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: Wed, 03 Oct 2012 18:04:46 +0930
Hi Johann,
On 03/10/2012, at 5:26 PM, Johann Werner wrote: derived attributes are "computed" by the database and thus those values are only updated when an eo is fetched into memory. In your case you are creating a new eo that has NULL for these attributes and as long as WO uses that eo or its snapshot cache those values will be still NULL. You have to refetch the eo to update the derived attributes.
Thanks for the explanation. Looks like a derived attribute is not the solution for this use case, then.
I wrote:
(As an aside, last time I looked at this was a few months ago, and I swear it was behaving properly then—i.e., that the derived attribute was immediately visible.)
Clearly I imagined that.
|
_______________________________________________
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