Re: EOOrQualifier
Re: EOOrQualifier
- Subject: Re: EOOrQualifier
- From: Pierre Bernard <email@hidden>
- Date: Sat, 22 Sep 2007 11:49:42 +0200
My guess is you have not defined relationship properties correctly.
This is the most common cause of odd query results.
E.g. an optional to-many relationship should be defined as left join.
If you fail to do so an inner join will eliminate rows where the
right side of the join is null
Pierre Bernard
Houdah Software s.à r.l.
On Sep 22, 2007, at 5:18 AM, email@hidden wrote:
Having a little trouble with this one, its only what I can assume
is a bug.
I have two EOQualifiers, say A and B.
If I search the database with A I get objects a and b.
If I search the database with B I get the object c.
If I search with an EOOrQualifier generated from A and B I get only
object c. Naturally I'm expecting a, b, and c.
Is there anything that could cause an EOOrQualifier to behave like
this or is it a bug? Object's a, b, and c are all from the same
table. The qualifiers A and B do have a contains selector for a
many to many. This is with mysql v. 5.0.37.
Thanks,
Eric_______________________________________________
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
- - -
Houdah Software s. à r. l.
http://www.houdah.com
HoudahGeo: One-stop photo geocoding
HoudahSpot: Powerful Spotlight frontend
_______________________________________________
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