D. Richard Hipp wrote:
Please run your program in a debugger and tell
me what the subroutine "isNT()" returns in os_win.c.
If it is returning false, that would explain your
occasional inability to get a read lock on a
read-only database.
Perhaps a windows programmer can suggest a better
isNT() returns 1(true)
I've only seen this database lock problem while access the db file on
the (slow) NAS - local file systems seem to work fine. Even accessing
it through one of our Windows shares seems to work fine. I'll keep
you posted if I find any more information related to this
Please run your program in a debugger and tell
me what the subroutine "isNT()" returns in os_win.c.
If it is returning false, that would explain your
occasional inability to get a read lock on a
read-only database.
Perhaps a windows programmer can suggest a better
implementation of the isNT()
ent.
Regards
Massimo
John Duprey <[EMAIL PROTECTED]> on 21/06/2005 22.59.12
Please respond to sqlite-users@sqlite.org
To:sqlite-users@sqlite.org
cc:
Subject:[sqlite] Database is locked on SELECT only calls?
Hi All,
I'm using sqlite 3.2.0 - the native C/C++ interface. I'm seeing
Hi All,
I'm using sqlite 3.2.0 - the native C/C++ interface. I'm seeing
something that I haven't seen before. I have 4 programs accessing the
same db file. The db file is on a slow Windows network share (NAS
device). The 4 programs are the only processes accessing the DB file
and all of them
5 matches
Mail list logo