I'd assume that something like that is exactly what's happening since
the problem only happens after a reboot, although I was thinking that
sqlite was caching it to a temp file or something. I'm running
Windows XP Pro but I haven't done anything to change the default
behavior of the os.
On Apr 05, 2006, at 06:19, Jay Sprenkle wrote:
On 4/4/06, Milton Sagen <[EMAIL PROTECTED]> wrote:
After a machine restart the first time I try to change a field in a
record, on Windows, it takes an inordinately long time for the sqlite
code to return, the amount of time is dependent on the size of the
database but even for a 20 Meg one with about 4000 records, the time
is in the order of a minute. Once the change is made I can quite the
program and relaunch it, open the database, and make another change
exactly like the first to another record and the sqlite code returns
almost immediately. On the Mac OS X, I don't see this delay.
Is the operating system, or cache hardware,
reading the database into memory and caching it?
