Convert LZ4 to SQL
Turn LZ4 archives into SQL. The LZ4 layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop LZ4 files on the dialor turn it to pick what to do
The SQL text from inside an LZ4 file.The LZ4 layer comes off. The bytes inside are written as they were.
What you get
One SQL file. The LZ4 compression is removed, and the content inside is written out unchanged. If the LZ4 file holds a database dump, you get that dump as a script that any SQL tool can read or replay.
Nothing is rewritten or converted along the way. The statements in the SQL file are the statements that were inside the LZ4 file.
Ask for what is inside
Choose SQL only when you know the file inside the LZ4 is SQL. Anything else is refused, because the bytes are written as they are and are not turned into another format.
If the file holds something the target cannot carry, the conversion stops with
unsupported_elements. If the LZ4 file cannot be parsed, it stops withinput_corrupted.Going the other way
To pack a SQL script back into LZ4, use SQL to LZ4. For other LZ4 conversions, see every LZ4 conversion.
LZ4 and SQL.What each format is.
The formats
LZ4
A single file compressed with LZ4, built for speed over ratio.
- Extensions
- .lz4
- MIME type
- application
/x -lz4 - Kind
- Archives
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
In your code.The same LZ4 to SQL conversion through the API, for your app or your agent.
$ cv convert archive.lz4 archive.sql$ cv convert archive.lz4 archive.sqlQuestions.What people ask about LZ4 to SQL.
No. The LZ4 layer is removed and the bytes inside are written as they were.
The conversion is refused. Ask for the format you know is inside the file.
The file could not be parsed as LZ4. The conversion stops with input_corrupted in that case.
No. The conversion gives one file as output.