Convert GZ to SQLITE
Turn GZ archives into SQLITE. The gzip layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop GZ files on the dialor turn it to pick what to do
A database file, unwrapped from gzip.The gzip layer is removed. The SQLite database inside is written as it was.
What you get
One SQLite file. The conversion removes the gzip layer and writes the bytes inside exactly as they were, so the tables, indexes and views in the database are not rebuilt or altered.
What you need to know
Ask for the format you know is inside the GZ file. If you ask for anything else, the conversion is refused.
A GZ file that does not hold a SQLite database is not a source for this conversion. The conversion stops with
unsupported_elementswhen the file holds something the target cannot carry, or when some inputs cannot become the format the join takes.When it stops
The conversion stops with
input_corruptedwhen the file could not be parsed.To go the other way and compress a database, use SQLITE to GZ.
GZ and SQLITE.What each format is.
The formats
Gzip
A single file compressed with gzip, such as a log or a CSV.
- Extensions
- .gz
- MIME type
- application
/gzip - Kind
- Archives
SQLite Database
A whole relational database in one file. Tables, indexes and views.
- Extensions
- .sqlite .sqlite3 .db
- MIME type
- application
/vnd .sqlite3 - Kind
- Text and data
In your code.The same GZ to SQLITE conversion through the API, for your app or your agent.
$ cv convert archive.gz archive.sqlite$ cv convert archive.gz archive.sqliteQuestions.What people ask about GZ to SQLITE.
No. The gzip layer is removed and the bytes inside are written as they were.
The conversion is refused if you ask for a format other than the one inside. It can also stop with unsupported_elements when the file holds something the target cannot carry.
The file could not be parsed. The conversion stops with input_corrupted in that case.
Use SQLITE to GZ, which goes the other way.