No, I'm not using bizobjs in that program. I'm just getting a cursor and running queries on this (only once now to avoid the memory issue. Thanks for that info - my application will no longer eat up 500mb+ after a few runs :) ).
I was a little too quick to state that my problem was gone. I still get the error from time to time. Once I get some more time I'll try to locate where the error is happening, but it's been a bit hard since the problem only happens sometimes, and on different queries for no obvious reason (at least to me). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Leafe Sent: 4. oktober 2006 13:08 To: Dabo Users list Subject: Re: [dabo-users] Memory leak in dCursor? On Oct 3, 2006, at 3:22 PM, Simen Haugen wrote: > This actually had a very nice side effect. I've had problems all along > with SQLite tables and the error "Could not open database" when > running > queries for no apparent reason. By only having one cursor on each > database this problem is also gone (at least it seems that way). Are you running these queries from your bizobjs? That's really how cursors are designed to be used. Normally you set your SQL fields, filters, etc., and call bizobj.requery(). Cursors are then managed for you by the bizobj; you should rarely have to interact with one directly. -- Ed Leafe -- http://leafe.com -- http://dabodev.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
