I think I found the problem.
I used a version of pysqlite compiled against sqlite3.2.8.
When used with the shared library from any sqlite 3.3.x version, every
sql operation eats all memory.
Thank you all for the help
On 7/14/06, Eduardo <[EMAIL PROTECTED]> wrote:
At 17:43 13/07/2006, you wrote
At 17:43 13/07/2006, you wrote:
Even the smallest sql statement (like PRAGMA temp_store = 1) triggers
this behaviour when using sqlite 3.3.x. I forgot to mention that I
connect to a :memory: database and then attach 2 database to the
connection.
Perhaps the 2 database attached are converted to
Robert Wallner wrote:
Even the smallest sql statement (like PRAGMA temp_store = 1) triggers
this behaviour when using sqlite 3.3.x. I forgot to mention that I
connect to a :memory: database and then attach 2 database to the
connection.
I've been using the apsw and pysqlite wrappers for some tim
Even the smallest sql statement (like PRAGMA temp_store = 1) triggers
this behaviour when using sqlite 3.3.x. I forgot to mention that I
connect to a :memory: database and then attach 2 database to the
connection.
I am pretty sure it's something that changed in sqlite 3.3, I just
don't know where
4 matches
Mail list logo