Fix foreign key constraint errors during import (#23)

Do not truncate export at null byte (#29)

Ensure we use a stable composer version (#25)

Co-authored-by: Kateryna Kodonenko <kateryna@automattic.com>

Load polyfills correctly for the new sqlite version (v2.2.22) (#24)

Co-authored-by: Kateryna Kodonenko <kateryna@automattic.com>

Set default SQL modes and other options for database import (#17)

Re throw the error when the encoding is correct but the import query …

…failed #16

Re throw the error when the encoding is correct but the import query failed

Fix import query parsing #14

* Adds multiple fixes and improvements that make the query recognition in the input dump almost complete.
* The only known edge cases that aren't supported yet are the usage of NO_BACKSLASH_ESCAPES SQL mode, and the MySQL DELIMITER ... statement. We likely won't implement those in the current logic—it's better to make the new query tokenizer fully support streaming to handle all edge cases correctly.

Merge pull request #12 from Automattic/update/escape-hash-values-when…

…-exporting

Fix sqlite export by escaping strings with numbers and e character

Merge pull request #11 from Automattic/fix-missing-db-name-constant

Add a fallback for missing `DB_NAME` constant

Merge pull request #10 from Automattic/new-sqlite-driver

Add support for the new SQLite driver