On 7 Aug 2019, at 9:16pm, Thomas Kurz wrote:
> Well, that's why I asked for an *import* support. It's widely spread practice
> to offer at least import capabilities from other software.
This is what the .import function in SQLite's shell tool is for. It reads a
well-documented text format.
Wednesday, August 07, 2019, 9:16:17 PM, Thomas Kurz
wrote:
>> I highly doubt the SQLite team will undertake this task. They
>> Surely have the skill to do so, but their priority is the one
>> software product you desire to use, undoubtedly due to its
>> high utility. I doubt that utility would
> I highly doubt the SQLite team will undertake this task. They
> Surely have the skill to do so, but their priority is the one
> software product you desire to use, undoubtedly due to its
> high utility. I doubt that utility would exist if they were
> to wander off tacking the conversion
The BIGGEST problem I had with importing data from MySQL to SQLite is the
table definitions.
If you do two dumps, one specifically for table definitions, the other for
the actual data to be imported, you could get a script to handle the table
definition file to make it conform to what SQLite can
You can use the SQL files from OpenGeoDB as an example:
http://www.fa-technik.adfc.de/code/opengeodb/opengeodb-begin.sql
The result (see below) from the https://github.com/dumblob/mysql2sqlite
converter is completely useless as none of the create statements is complete. I
have observed severe
On 7 Aug 2019, at 5:13pm, Thomas Kurz wrote:
> So my suggestion would be to add an import feature to the CLI that allows to
> directly import MySQL/MariaDB dumps into an SQLite database keeping as many
> information as possible. As SQLite already has a complete SQL parser I expect
> much
6 matches
Mail list logo
