Convert XZ to SQLITE
Turn XZ archives into SQLITE. The xz layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop XZ files on the dialor turn it to pick what to do
A SQLite database, unpacked from XZ.The xz layer comes off. The database inside is written as it was.
What you get
One file. The xz compression is removed, and the bytes inside are written unchanged. If the XZ file holds a SQLite database, you get that database with its tables, indexes and views as they were.
What the conversion expects
The conversion does not turn other data into a database. You must ask for the format you know is inside the XZ file. Anything else is refused.
When the file holds something the target cannot carry, the conversion stops with
unsupported_elements. When the file cannot be parsed, it stops withinput_corrupted.Going the other way
To compress a database into an XZ file, use SQLITE to XZ. The page for every XZ conversion lists the other targets.
XZ and SQLITE.What each format is.
The formats
XZ
A single file compressed with xz, the LZMA format of most Linux distributions.
- Extensions
- .xz
- MIME type
- application
/x -xz - 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 XZ to SQLITE conversion through the API, for your app or your agent.
$ cv convert archive.xz archive.sqlite$ cv convert archive.xz archive.sqliteQuestions.What people ask about XZ to SQLITE.
No. The xz layer is removed and the bytes inside are written as they were.
No. Ask for the format you know is inside. If the file holds anything else, the request is refused.
The file holds something the target cannot carry, or some inputs cannot become the format the join takes.
The file could not be parsed. The conversion stops with input_corrupted in that case.