Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
- Subject: Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
- From: Paul Hoadley <email@hidden>
- Date: Thu, 04 Oct 2012 06:36:54 +0930
On 03/10/2012, at 10:10 PM, Kieran Kelleher wrote: FWIW, I made a small change to ERXGenericRecord (integration branch) recently that allows valueForKey( primaryKeyAttributeName ) to read the PK value .... using "id" or whatever you use for PK field names to be used. This was to allow a fetch qualifier qualified on the primary key attribute to be used in both fetchspecs and in-memory qualification.
That might be a solution for what you are trying to achieve while avoiding the derived attribute altogether.
Thanks Kieran, I'll take a look.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden