Re: Multi-User using Core Data?
Re: Multi-User using Core Data?
- Subject: Re: Multi-User using Core Data?
- From: Frank Illenberger <email@hidden>
- Date: Tue, 5 Jul 2005 20:58:54 +0200
Note that mixing file systems when accessing a single SQLite database
file is a really, really bad idea. The alternative was to basically
go with .lock files on all filesystems.
Bill,
today I tried to use the locking abilities of sqlite to implement a
scenario in which two instances of a CoreData-NSPersistentDocument-
App share the same file. I observed the following:
Case1: (both AFP)
The shared file resides on a file server and I have two client
instances of my application running on another two separate machines.
Both client app-instances access the shared file via AFP.
---> This case works fine. I am able to to open the file on both
clients at the same time and I am able to perform reads and writes.
Case2: (mixed direct + AFP)
The file resides on the machine of ClientA. ClientA accesses the file
directly. ClientA activates personal file sharing for his account and
ClientB accesses the file via AFP.
--->This does not work. After few actions, I get "database is locked"
exceptions even if only one client tries to write to the file.
I understand that Case2 is a special one. But for small workgroups in
small companies it is a very common case.
Is there any way to achieve a correct locking behavior with sqlite
in this setup? Perhaps by using locking files etc.? How can I
activate the use of locking files with CoreData?
Thanks for you help!
Cheers
Frank
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden