Convert BZ2 to SQLITE
Turn BZ2 archives into SQLITE. The bzip2 layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop BZ2 files on the dialor turn it to pick what to do
A SQLite database, unpacked from BZ2.The bzip2 layer comes off and the database inside stays as it was.
What you get
One SQLite file. The bzip2 layer is removed and the bytes inside are written as they were, so the tables, indexes and views in the database are the ones that were in the archive.
Nothing is rebuilt or rewritten. The conversion unpacks the file and does not change what it holds.
Ask for what is inside
Choose SQLITE only when you know the BZ2 file holds a SQLite database. Anything else is refused.
The conversion stops with
unsupported_elementswhen the file holds something the target cannot carry, or when the input cannot become the format the join takes. It stops withinput_corruptedwhen the file could not be parsed.Going the other way
To pack a database back into a BZ2 file, use SQLITE to BZ2. The conversion has no options to set.
BZ2 and SQLITE.What each format is.
The formats
Bzip2
A single file compressed with bzip2.
- Extensions
- .bz2
- MIME type
- application
/x -bzip2 - 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 BZ2 to SQLITE conversion through the API, for your app or your agent.
$ cv convert archive.bz2 archive.sqlite$ cv convert archive.bz2 archive.sqliteQuestions.What people ask about BZ2 to SQLITE.
No. The bytes inside the archive are written as they were. Only the bzip2 layer is removed.
The conversion is refused. Ask for the format you know is inside the archive.
The file could not be parsed. The conversion stops with input_corrupted in that case.
One file. It is the database that was inside the BZ2 archive.