[Mono-bugs] [Bug 77711][Maj] Changed - Mono.Data.SqliteClient throws exception retrieving non-ASCII data

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Mar 8 09:04:45 EST 2006

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by tauberer at for.net.


--- shadow/77711	2006-03-05 19:53:37.000000000 -0500
+++ shadow/77711.tmp.30529	2006-03-08 09:04:45.000000000 -0500
@@ -76,6 +76,22 @@
 can use both.
 Either way, this bug is still valid for the sqlite2 case--there is
 still a bug in retrieving the non-ascii values since they are
 obviously stored correctly in the DB as the native sqlite tool can
 retrieve them but mono can't.
+------- Additional Comments From tauberer at for.net  2006-03-08 09:04 -------
+As a side note, it defaults to version 2 when both are present for
+whatever reason.
+In any case, I'm wondering if this is a bug outside of
+Mono.Data.Sqlite.  This returns null:
+  Marshal.PtrToStringAnsi(Marshal.StringToCoTaskMemAnsi("ü"));
+I'll look into whether that's a bug.
+Mono.Data.SqliteClient with Sqlite2 uses ANSI encoding by default,
+which may not be good for F-Spot.  F-Spot should either give
+"encoding=UTF-8" in the connection string (that's new), or else use
+Sqlite3 ("version=3" in the connection string), which now uses Unicode.

More information about the mono-bugs mailing list