Alternative suggestion:
A readonly derived column is another option to expose the PK. The advantage is
that the the new exposed column can be used in standard EOQualifier that works
in memory and for schema-based qualifiers.
Assuming your primary key col is named "pk" and you want an attribute n
Thank you primaryKey() is working for my needs. I didn't want to do a
separate query... I have a couple of relations and I eventually wanted a string
that was something like:
--
so I end up with a display of:
MRK-M-1001
I just tested this and it is perfect...
Ted
--- On Sat, 4/17/10, G
On 17. Apr, 2010, at 19:49 , Theodore Petrosky wrote:
> I want to expose the primary key to be part of my entity. (At least this is
> what I think I want.)
Maybe you want this, but is it what you need? I'd say, you have several options:
In awakeFromInsertion you could query (probably just raw s
I want to expose the primary key to be part of my entity. (At least this is
what I think I want.)
I have a Job entity. Each job has a number. I am using a setval in my
migrations to make the primary key start at a given number and I want to use
this number as the job number. So far so good. I w
Sounds like fun, but I¹m not going to be there this month.
Paula
On 4/17/10 7:32 AM, "Andrew R. Kinnie" wrote:
> Greetings all,
>
> This month's WO-NOVA Webobjects developers' group meeting is TUESDAY NIGHT
> (4/20/2010) at 6:30 PM.
>
> The meeting will include discussions about using Mylyn t
Greetings all,
This month's WO-NOVA Webobjects developers' group meeting is TUESDAY NIGHT
(4/20/2010) at 6:30 PM.
The meeting will include discussions about using Mylyn to integrate Jira with
Eclipse, Direct2Web with ERModernLook and Travis wants to brag about how much
better his new Macbook P
