• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: Kieran Kelleher <email@hidden>
  • Date: Wed, 03 Oct 2012 08:40:00 -0400

Hi Paul,

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.

-Kieran

On Oct 3, 2012, at 4:34 AM, Paul Hoadley <email@hidden> wrote:

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
  • Follow-Ups:
    • Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
      • From: Paul Hoadley <email@hidden>
References: 
 >Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder] (From: Paul Hoadley <email@hidden>)
 >Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder] (From: Johann Werner <email@hidden>)
 >Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder] (From: Paul Hoadley <email@hidden>)

  • Prev by Date: Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
  • Next by Date: RE: Localizable.strings
  • Previous by thread: Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
  • Next by thread: Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
  • Index(es):
    • Date
    • Thread