Good to know and looks like it might fix my problem. Except that
MySQL doesn't support WO's syntax for outer joins. Looks like it's
another point for switching to postgreSQL, maybe later though.
Switching over now would be a bit of a headache.
I also still think it should be classified as a bug. It would have
worked if WO hadn't optimized the SQL incorrectly, I was able to take
the two independent SELECT statements and just put an OR between them
and got the expected results. Guess I'll build a small sample project
and head on over to the bug reporter.
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 PROTECTED] 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.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
