dumblob

>Yes, most of the tables were migrated ... Well done. We're getting closer :wink:. >For the 1st error, does the script support "timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP"...

There was indeed a mistake in the processing of the MySQL specialty `ON UPDATE CURRENT_TIMESTAMP`. I've updated the script a bit and pushed a new revision. Feel free to test...

@juliniq please refer to my argumentation in https://github.com/dumblob/mysql2sqlite/issues/24#issuecomment-347993916 . Should you have any better idea, I'm keen to hear you out.

Hi @juliniq, thanks for the report! I've taken a look at the python plugin for the MySQL Workbench and it's definitely a better choice than this conversion script because of...

This error comes from sqlite, not from this conversion script.. It seems you hit the limitations of SQLite3 (refer to **Maximum Number Of Terms In A Compound SELECT Statement** section...

@tom it's about **select**s and I can't see any connection to **insert**s. @androidseb25 I'm not sure what you mean by splitting a query, but I'm not aware of any existing...

@tom thank you for your explanation and testing. It's impressive! I'm really curious whether you'll come across some issue with the SQLite3 DB converted from MySQL (be careful, SQLite3 doesn't...

@apsg did you create the mysql dump with `mysqldump --skip-extended-insert ...` as mentioned in *README.md*?

Hi @ManjotS, I'm sorry but currently I'm lacking time to investigate it by coming up with my own test cases. Could you please provide the by MySQL generated output, so...

@karborator do you have the corresponding MySQL generated output, so that I can take a look at it?