This is a bug in MacOS X.
I am quite sure Apple has recently fixed it in the latest 10.4.6 update:
http://www.apple.com/support/downloads/macosx1046forppc.html
From the fix release note: "file access and byte range locking with
AFP file sharing".
This theoretically means that with the latest OSX update, it should
works on shared volumes, but I haven't verified it... (and maybe this
now requires some changes inside sqlite).
---
Marco Bambini
http://www.sqlabs.net
http://www.sqlabs.net/blog/
On Apr 11, 2006, at 6:48 PM, GregO wrote:
I'm trying to get some clarification on:
http://www.realsoftware.com/feedback/viewreport.php?reportid=pranjyzk
The answer from Will is that this is a limitation in SQLite, but if
that's the case, why does it work on Windows? I would expect that
with a real path, and a legal folderItem, the database engine
wouldn't care. Is this not the case?
GregO
BTW - The workaround I have been using is to create my own version
of a .ldb file and then COPY the backend down to the local machine,
use it, and then put it back when I am done and delete the .ldb
file. What a pain in the butt......
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
