I have seen something that seems strange and wonder if anyone has any
thoughts?

I have been using SQLite for a long time now and never seen anything
similar.  Had been using 3.7.6.1 and have now upgraded to 3.7.13 but
behavior has not changed.

In a Debug build this code works as expected but in Release build I am
having only 2 of the 7 rows be inserted.  I have found a workaround in that
if I Sleep() for 100ms after each INSERT the Release build then works as
expected.

Unfortunately a lot of code involved so it will take a while to pare down
to small test case and since I have a workaround I will hope for a general
answer first.

Inside a BEGIN IMMEDIATE, I do a SELECT from table Objectives and get back
7 rows which are held in a list.  Iterate that list and for each do a
SAVEPOINT then INSERT a row into table Calibration then do RELEASE.  When
finished iterating the list do COMMIT.

Windows 7 64bit.  Visual Studio 2010.  Real HDD not SSD.  The file is on
local machine but is opened using a network path.  i.e.
\\MACHINENAME\Data\Calibration.db
Thank you in advance for your time on this matter.

Jeff Archer
Nanotronics Imaging
jsarc...@nanotronicsimaging.com
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to