For whom it may concern. I have done some quick testing - and it seems Mono.Data.SQLite is fully compatibale with MS.Net framework 1.1 - great job you guys at Mono :) On monday I'll convert my project to use Mono's wrapper - and see if I can reproduce the error here. /Michael
________________________________ From: Michael B. Hansen [mailto:[EMAIL PROTECTED] Sent: Fri 2006-05-26 19:08 To: sqlite-users@sqlite.org Subject: RE: [sqlite] Possible bug in sqlite3_prepare Hi Robert, My project doesn't work well with .NET 2.0 - so that's not an option (believe me, I have thought about it) :( However, does anybody know if the Mono SQLite wrapper work with MS .NET Framework 1.1? /Michael ________________________________ From: Robert Simpson [mailto:[EMAIL PROTECTED] Sent: Fri 2006-05-26 17:42 To: sqlite-users@sqlite.org Subject: RE: [sqlite] Possible bug in sqlite3_prepare > ----- Original Message ----- > From: "Michael B. Hansen" <[EMAIL PROTECTED]> > To: <sqlite-users@sqlite.org> > Sent: Friday, May 26, 2006 8:23 AM > Subject: [sqlite] Possible bug in sqlite3_prepare > > > Hi, > > For the last month I've been troubled by an apparent bug in > SQLite 3.3.5 > which has been very hard to track down. After extensive debugging and > bug-tracking it seems there must be a bug/feature somewhere > in SQLite - > propably in sqlite3_prepare because this is where the symptom > of the bug > appears every time. It escalated when I updated the SQLite > from 3.3.4 to > 3.3.5 - although I'm not sure how often the problem occured in 3.3.4. > > I'm using SQLite 3.3.5 in a threaded .NET environment - although all > communication with SQLite happens synchronized manner (eg. only one > thread at a time). It's possible it could be a compatibility issue relating to the Finisar library which was last released and tested against an older SQLite version. Do you happen to have access to Visual Studio 2005 and will your program compile on .NET 2.0? If so, give the ADO.NET 2.0 provider a try and see if it still fails. Compiling with a different provider might help isolate whether it's a wrapper issue or a SQLite issue. http://sqlite.phxsoftware.com <http://sqlite.phxsoftware.com/> <http://sqlite.phxsoftware.com/> Robert
