Igor Korot wrote: > When the user asks to edit the data it starts the transaction, then > set the "SAVEPOINT"
Why do you need a savepoint in addition to the transaction? > Now the problem: only during the scenario #3 I have a lot of memory > leaks. They are reported in the Visual Studio debug > window. Looking at the data I did a global search and it turns out > that those leakage are coming from the sqlite. How are those leaks shown? With a call stack? In that case, please don't keep it a secret. It would be helpful to show the code for scenario #3. (It might be possible that your code doesn't correctly free some SQLite object.) Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
