• 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: EOOrQualifier
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOOrQualifier


  • Subject: Re: EOOrQualifier
  • From: Chuck Hill <email@hidden>
  • Date: Tue, 25 Sep 2007 10:11:13 -0700


On Sep 24, 2007, at 9:01 PM, email@hidden wrote:

Good to know and looks like it might fix my problem. Except that MySQL doesn't support WO's syntax for outer joins.

You should be able to correct this by sub-classing com.webobjects.jdbcadaptor.MySQLPlugIn and com.webobjects.jdbcadaptor.MySQLPlugIn.MySQLExpression.


Looks like it's another point for switching to postgreSQL, maybe later though. Switching over now would be a bit of a headache.

Have you not used EOPrototypes? :-)


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.

That sounds like it is worth doing.


Chuck




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.

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


This email sent to email@hidden

--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
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: EOOrQualifier
      • From: Eric Wagner <email@hidden>
References: 
 >Re: EOOrQualifier (From: email@hidden)

  • Prev by Date: DTW date formatting rule...
  • Next by Date: just a reminder
  • Previous by thread: Re: EOOrQualifier
  • Next by thread: Re: EOOrQualifier
  • Index(es):
    • Date
    • Thread