[Mono-bugs] [Bug 76494][Min] Changed - Mono.Data.SqliteClient Memory corruption when reusing connection after DELETE with named parameters

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Nov 11 17:07:32 EST 2005

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 nazgul at omega.pl.


--- shadow/76494	2005-10-26 09:12:58.000000000 -0400
+++ shadow/76494.tmp.16658	2005-11-11 17:07:32.000000000 -0500
@@ -226,6 +226,19 @@
 For Sqlite3 current:
 ln -s /usr/lib/sqlite-3.2.7.so /usr/lib/libsqlite3.so.0
 For current Sqlite2:
 ln -s /usr/lib/sqlite-2.8.16.so /usr/lib/libsqlite.so.0
 - Now you can switch version in the Connection String.
+------- Additional Comments From nazgul at omega.pl  2005-11-11 17:07 -------
+tekkhedd, your patch works great for me - the nasty crashes from
+sqlite just disappeared from my application :-)
+It has an unpleasant regression though, setting encoding to 16-bit
+unicode breaks the previous semantics of library... For example in my
+Win32 App I insert some text with special characters into db (and the
+encoding it most probably the default cp1250) and after reading them
+back they are screwed up :(
+Probably I can workaround it explicitly converting those strings into
+UTF16, but I'm don't know yet how to set it up in
+System.Data.DataTable+DataAdapter classes.

More information about the mono-bugs mailing list