I think there is a problem with file locking on Mac OS X as it is implemented in SQLite. The problem shows itself if you begin a transaction in one process and then try to read from the same database with another process. The read succeeds without error. I believe this is not correct. In fact, if I build the command-line sqlite utility on OS X and try to read the same database I *do* get an error.

I believe the problem is described by this technote:

<http://developer.apple.com/technotes/tn/tn2037.html>

Basically, the Mac implementation of file locking in os.c uses PBLockRangeSync to lock files. But apparently on OS X that can return with no error even if that same range has previously been locked.

This leads me to wonder what would be involved in trying to get the UNIX implementation to compile and run under CodeWarrior for the OS X version of SQLite.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to