-
-
Notifications
You must be signed in to change notification settings - Fork 895
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encoding problem with cli export/import #2645
Comments
Hum, I did not observe such a problem during my tests. Would you be able to find the more precise data, which makes it fail? We could add some Unicode sanitizing before insertion |
Would you be able to produce a small version of your SQLite file, exhibiting the issue? |
Invalid entries where limited to a feed that is no longer updated: http://www.hardware.fr/backend/news.xml. I have been able to import my database, removing all entries from that feed. Here is the stripped down db (just one article of this feed): https://owncloud.cedricgirard.com/s/dtmHp66jqW5bfSS/download |
It is this comment, apparently in ISO-8859-x in the middle of some UTF-8, which seems to cause the problem, only with PostgreSQL: <!-- Page actualit� individuelle --> |
Sorry for not having been able to test this sooner. It does fix this bug. Thank you. |
Hi,
After exporting my user database to sqlite from MySQL with the cli, I am trying to import it back into PostgreSQL, still with the cli.
It fails with the following error in PostgreSQL log:
Is it related to utf8mb4 in MySQL? Is there any way to clean my data to allow import or just skip the invalid value?
The text was updated successfully, but these errors were encountered: