> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > The important thing to understand here, is that you're not stepping > through a set of results that you have in memory and that > were extracted > from the database. You are (at least for simple queries) > stepping through > data that is still in the database. Because you're still > actively reading > the database the writer thread can't get access until your query is > finished. If, instead, you want to load the whole results set > into memory > before stepping through them consider the sqlite_get_table_* > functions. > Alternatively you can collect the results into memory any way > you like > before stepping through the structures you've created yourself.
I ran into this yesterday too. This is a pretty severe limitation compared with other databases I've used, like Postgres, MySQL, and Oracle. Are there any plans/desires to fix this, or is it considered something that just comes with the "lightweight" territory? -Ken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
