e; I'd
like to have that between two machines...
Thanks for your time,
Arthur C.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-
I've been busy adding some structure to the NSUserDefaults in my app. So I
would have a dictionary like 'generalPrefs' with some key/value pairs,
separate from 'otherPrefs' etc.
Now I wonder why the following doesn't work:
[[NSUserDefaultsController sharedUserDefaultsController] valueForKeyPath:
return [self managedObjectContextForConfiguration:
recipesConfigurationKey];
} ?
2. Is it correct to set up the dictionary in - init?
3. Could there be a timing problem?
Thanks in advance,
Arthur C.
___
Cocoa-dev mailing list (Cocoa-dev@lists.
I have two managedObjectContexts with one persistentStoreCoordinator
having two persistent stores?
Thanks,
Arthur C.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
C
me when there is one object having a relation to two or more other
>objects.So, the problem is now more accurately defined. I hope someone has an
>idea how to tackle this one, as it prevents us in a nasty way from having
>multiple separately savable stores.Thanks,Arthur C.
__
n once, and it doesn't help to
> do the assignObject: toPersistentStore: outside the awakeFromInsert.Note that
> on systems with OS 10.5 (Leopard) it works fine, while on 10.4 (Tiger) it
> always gives the error... We'
ce it has been saved'. This means the
Core Data stack cannot be saved anymore, which is of course a serious problem.
Do you know what causes this error? Do I need to use a different setup for the
managedObjectContext - persistentStoreCoordinator - persistentStores system?
Thanks for your
you know what causes this error? Do I need to use a different setup for the
managedObjectContext - persistentStoreCoordinator - persistentStores system?
Thanks for your time,
Arthur C.
_
Express yourself instantly with MSN Messe
>From: [EMAIL PROTECTED]>To: cocoa-dev@lists.apple.com>Subject: Validating a
>non-optional transient Core Data property - it can be erased?!>Date: Wed, 12
>Nov 2008 22:31:02 +0100>
>In my Core Data database I have a property called 'target' (double), which is
>transient and required (i.e.
In my Core Data database I have a property called 'target' (double), which is
transient and required (i.e. 'non-optional' in the model). It is dependent on
another variable 'color'; so for each color there is a 'target'. As I want to
show only the target for the selected color, I use this trans
is not preserved, which
causes the rest of the application to behave unexpectedly.
How can I preserve this selection, and make the user select a new item
explicitly also when using the search box?
Thanks for your time,
Arthur C
access to theDepartment from Employee - awakeFromInsert. But I'm not
allowed to do a fetchRequest from here, right?
What is a clean way to do this? At this moment I have the department
pre-fetched somewhere (like in AppDelegate), but that's probably not the right
approach.
Thanks f
I have an NSDictionary that has to be written to disk, distributed and read in
again.
I would like to add an MD5 sum to the dictionary to make sure it has not been
modified/corrupted on the way. That can be done by making NSData using
NSArchiver and then passing it to MD5() from .
But, the o
In my application I have a status log which is kept in Core Data. This gives a
nice interface and persistence for the log.
However, I would like to be able to save the log to disk independent from other
parts of my Core Data model. This is needed to prevent the log from getting
lost in the even
14 matches
Mail list logo