Hi Clive,
[EMAIL PROTECTED] wrote:
I am benchmarking sqlite3 as a potential database for Windows and embedded applications. I am running the following code in a Rapid development environment that calls the equivalent sqlite3 functions in a Window's DLL that I built from the release . I am seeing that memory usage goes up and up with every loop, until Windows runs out of virtual memory. Am I doing something wrong?
while(true) SQL exec: 'BEGIN TRANSACTION'; for <Integer:i> from 1 to 1000 step 1 SQL query: 'INSERT INTO Contacts values(''aaa'',''bbb'',''4'')'; SQL exec: 'COMMIT TRANSACTION';
It looks like you've wrapped it in some sort of Visual Basic. Is that true?
If you are using the sqlite3_prepare/sqlite3_step/sqlite3_finalize API, yhe behavior you experience may be because you don't call sqlite3_finalize. Do you use that API?
HTH
Ulrik P.
