Hi, I made another post related to this since the topic changed.
Problem was solved using sqlite3_prepare_v2() instead of sqlite3_prepare(). All is fine now ! :) Oyvind On Wed, Nov 26, 2008 at 5:41 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > > On Nov 26, 2008, at 11:02 AM, Oyvind Idland wrote: > > > Seems my problem are related to sqlite not handling multiple prepared > > statements properly. > > > Before every release of SQLite, we run scripts that do literally > millions of prepared statements. They all work correctly before we > make the release. And SQLite prepared statements are used in > thousands of consumer products like iTunes and Skype and Adobe Acrobat > reader, all without given any trouble. So I'm guessing the problem is > more likely to be found in your code than in the prepared statement > handling of SQLite. Perhaps if you give a concrete example of what is > going wrong in your application, someone might be able to suggest a fix. > > D. Richard Hipp > [EMAIL PROTECTED] > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
