On Apr 21, 2009, at 7:12 PM, Marco Bambini wrote: > Hello Dr. Hipp, > > I was finally able to track down the issue ... the problem is due to > the fact that after each write operation the client executes a query > like: > "SELECT 123 AS changes;" (the number 123 changes all the time) > this select statement was performed in an in-memory database ... > then I tried to perform it in a disk based db ... but the behavior > doesn't change, the memory used by sqlite continue to increase and > it is never released (until the db is closed). > > So, my new question is... how I can return a fixed value from an > sqlite3 database without having this memory issue? >
Are you sure you are calling sqlite3_finalize() on the statement once you are done with it? You can use sqlite3_next_stmt() interface to get a listing of all unfinalized statements for a database connection. Count them, and if the number keeps growing, that is your problem. D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
