Question data cannot be written using non-ASCII characters #1

New Issue

Closed

opened 2022-11-25 07:24:35 +00:00 by nu · 1 comment

nu commented

2022-11-25 07:24:35 +00:00

Owner

Data pulled from the default SQLite database becomes mojibaked if it uses non-ASCII characters. Appears to be a problem with either DBI, the way the default database works, or perhaps how SQLite works.

nu added the

bug

label 2022-11-25 07:24:35 +00:00

nu commented

2023-03-15 06:55:58 +00:00

Author

Owner

Fixed in commit 8c415e9850. The issue seemed to be that, for very specifically the sqlite_unicode option in the options hashref, DBI (or the SQLite driver?) was expecting that the options array be after the username and password entries for the database... which it didn't have, because SQLite doesn't need those and I wrote it with that in mind lmao

Just having empty user/pass args was enough to fix it

Fixed in commit 8c415e9850. The issue seemed to be that, for very specifically the `sqlite_unicode` option in the options hashref, DBI (or the SQLite driver?) was expecting that the options array be after the username and password entries for the database... which it didn't have, because SQLite doesn't need those and I wrote it with that in mind lmao Just having empty user/pass args was enough to fix it

nu closed this issue

2023-03-15 06:55:58 +00:00