Import from SQL-Dump files is broken since v3.11 #2323
Comments
|
Is there any chance you could email me the dump (or zip of it). If needed, you could sanitize the data... I'd just need the lump where the error occurs. What 'possibly' is happening, is that there is no 'standard' for creating a SQL dump file. Depending on what dumped it, it might have different quotes or formatting. Additionally, the biggest gotcha is inserting records into a table that hasn't been created yet, or due to foreign keys, a record can't be inserted, as the corresponding record hasn't been inserted yet. Its a little bit messy... You can email it to db4s [at] chrisjlocke [dot] co [dot] uk (a poor attempt to obfuscate an email address that probably isn't worth it anymore...)
Improvements (or not ... depending on your viewpoint) were made to importing back in 3.11, and tweaks have been made. |
justinclift
added
the
bug
|
@chrisjlocke : I just sent you an email |
|
This appears to be because the .sql file being imported is encoded as UTF-8 (BOM).
If converted to UTF-8 (Notepad++ does this in a simple menu-click) then it imports fine. 👍
Maybe DB4S could detect this file format when importing and do a pre-import cough? Slightly over my head for these sort of conversions and what DB4S can detect. I don't know if DB4S is reading the whole file as one long string and therefore choking, or just isn't expecting BOM encoded files... |
This fixes the import of SQL files with a leading BOM. See issue #2323.
|
Should be fixed in the next nightly build. Can you give that a try, @HarryDe? 😄 |
|
Ok, I’ll try tomorrow then and let you know
|
|
Can you make me a 64-msi? The latest 64 nightly build is of 6. July. |
|
Oh you're right. @justinclift Can you check if there was any build failure? |
|
Oops. I nuked the built win .msi's and logs about an hour ago from the build server Win VM, to free up disk space. 😦 As a workaround, I've just kicked off the Win64 build process again manually. If that it completes ok then there should be updated Win64 binaries on the nightlies server in about 30-40 mins. 😄 |
|
The Win64 build process just finished without error. 😄 @HarryDe New .msi's are here: |
|
Works now with UTF-8-BOM |
|
Perfect, you did even include the unique constraint message.
Thanks!
Harry
|
|
Awesome 😄 Thanks again for reporting this! |
This fixes the import of SQL files with a leading BOM. See issue #2323.
Details for the issue
What did you do?
I tried to import data from a SQL-Dump.
What did you expect to see?
Approx. 20,000 records imported into a table
What did you see instead?
A syntax error near "DELETE FROM
table". Removing the DELETE statement resulted in a syntax error near "INSERT INTO ..."The error was already present in v3.11, upgrading to 3.12 did not fix it.
However, after downgrading to 3.10 the import worked, as it did years before. Hence the bug was most likely introduced in 3.11
Useful extra information
The text was updated successfully, but these errors were encountered: