Convert SQL to DIF
Turn SQL files into DIF files. The tables the script creates are loaded first, with a dump from MySQL, MariaDB or PostgreSQL rewritten into SQLite's dialect.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop SQL files on the dialor turn it to pick what to do
Each table in your SQL script, as a DIF file.The tables the script creates are loaded, then written out one per table.
What you get
One DIF file for each table, named after the table. Each file holds the table's values in UTF-8, with a header row on top.
A dump from MySQL, MariaDB or PostgreSQL is rewritten into SQLite's dialect before the tables are loaded.
What changes or is left out
Dates that are not real dates, such as MySQL's 0000-00-00, are left empty. PostgreSQL true and false become 1 and 0.
Views, functions and triggers are left out, and a warning says so. Only the tables and their values end up in the DIF files.
SQL and DIF.What each format is.
The formats
SQL Script
SQL statements as text. A database dump that any SQL tool can read or replay.
- Extensions
- .sql
- MIME type
- application
/sql - Kind
- Text and data
Data Interchange Format
Data Interchange Format spreadsheets.
- Extensions
- .dif
- MIME type
- application
/x -dif - Kind
- Documents
In your code.The same SQL to DIF conversion through the API, for your app or your agent.
$ cv convert report.sql report/ --to dif$ cv convert report.sql report/ --to difQuestions.What people ask about SQL to DIF.
One DIF file for each table the script creates, named after the table.
Yes. A dump from MySQL, MariaDB or PostgreSQL is rewritten into SQLite's dialect before the tables are loaded.
They are not real dates, so the cells are left empty.
No. Views, functions and triggers are left out, and a warning tells you. See every DIF conversion for other ways to produce DIF files.