Re: Specify valid values for a Core Data attribute

2011-08-19 Thread Sean McBride
On Fri, 19 Aug 2011 15:40:55 +0200, Brian Norh said: >One of the problems with this approach is that it doesn't work if the >application is localized it into a different language. Then the word >which indicates the state is stored differently depending on the >current language. I need to save the

Re: Specify valid values for a Core Data attribute

2011-08-19 Thread Martin Hewitson
Hi Brian, I've normally solved this using an integer for the value and enumerate that to stand for different states of the bug. I'm not sure if there's a clever way to use an enum in conjunction with core data, so it may become a headache to 'remember' what each value stands for, but if you onl

Specify valid values for a Core Data attribute

2011-08-19 Thread Brian Norh
Hello. When I'm using Core Data I'm sometimes in a situation where I have an attribute than can only have a specific set of possible values. As an example let's say that you make a bug tracker and you have an entity called Bug. Then it's possible that you want an attribute for the state that the b