• 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: EOKeyValueQualifier not resolving vertical inheritance?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOKeyValueQualifier not resolving vertical inheritance?


  • Subject: Re: EOKeyValueQualifier not resolving vertical inheritance?
  • From: Kieran Kelleher <email@hidden>
  • Date: Tue, 14 Mar 2006 08:18:26 -0500

I had issues with EOQualifiers and inheritance hierarchies generating bad SQL a few weeks ago and the solution (Chuck Hill responded I think) was to stick with single table inheritance if you want reliable SQL generated from your EOQualifiers.

Regards, Kieran

On Mar 14, 2006, at 3:11 AM, Wolfram Stebel wrote:

Hi List,

i create a complex query from user input via EOKeyValueQualifier and other
EOQualifiers.


Absolutely fine is:
EOKeyValueQualifier ( myAttributeName, mySelector, myComparedEO );

Also OK is it for a keypath to a non flattened attribute (lets say:
"location.derivedClassAttribute", where location is a derived class):
EOKeyValueQualifier ( "location.derivedClassAttribute", mySelector,
myComparedValue );
(myComparedValue is a string in this case).

The above statement creates joins with aliases like:

...FetchedClass t0, Location T1, LocationBaseClass T2...

and fetches the correct EOs.

When the left hand side points to an attribute of an inherited class it
evaluates to the wrong derived entity:
Compared to the above example:
EOKeyValueQualifier ( "location.baseClassAttribute", mySelector,
myComparedValue );
does not evaluate to table "Location". Instead it creates aliases like:

... FetchedClass t0, Person T1, LocationBaseClass T2...

where "Person" is another derived class of the same base class.

This seems to be a bug, because the class information for
"location.baseClassAttribute" is available and correct for the relation
"location", but it does not create the correct SQL.

Did someone see this behavior too?
Any tips for a workaround?

TIA

Wolfram


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


This email sent to email@hidden


_______________________________________________ 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: EOKeyValueQualifier not resolving vertical inheritance?
      • From: Wolfram Stebel <email@hidden>
References: 
 >EOKeyValueQualifier not resolving vertical inheritance? (From: Wolfram Stebel <email@hidden>)

  • Prev by Date: Re: EOKeyValueQualifier not resolving vertical inheritance?
  • Next by Date: Compatability with MacBook Pro
  • Previous by thread: Re: EOKeyValueQualifier not resolving vertical inheritance?
  • Next by thread: Re: EOKeyValueQualifier not resolving vertical inheritance?
  • Index(es):
    • Date
    • Thread