From: John H. <joh...@gm...> - 2009-12-23 15:20:32
|
There is an ExistsInRelationshipQualifier from Pierre Bernard that I have used. I'm not finding a link to it right now, but I have the code. Maybe this could be added to Wonder? John On Tue, Dec 22, 2009 at 11:52 PM, Kieran Kelleher <kie...@ma...>wrote: > +1 .... automatic LEFT JOIN would be really nice ..... > > the only way to work around this today without executing undesirable > hardcoded SQL is to generate two different fetches and merge the two > resulting arrays. > > Fetch #1 (firstName contains John AND supervisor is null) > > Fetch #2 (supervisor.firstName contains John) > > Sent from my MacBook Pro while sitting on my Sofa > > On Dec 22, 2009, at 5:49 PM, ms...@md... wrote: > > It's not really a bug in erxorqualifier ... It's more a lack of > expressiveness in the qualifier API. In your model, you can change the join > semantic to be left outer instead of inner and I believe it will solve this > particular problem, but it may introduce new problems as well. I personally > think we need more API on qualifiers to be able specify this on the query > and not in the model. > > Sent from my iPhone > > On Dec 22, 2009, at 5:29 PM, "Ray Kiddy"<ra...@ga...> wrote: > > > On Dec 22, 2009, at 12:09 PM, WebHelpDesk wrote: > > I apologize if this has already been addressed somewhere, but I didn't find > anything... > > I'm trying to figure out how I can make an OR qualifier work with an > indirect property. For example, if I try to create an ERXOrQualifier like > the following: > > (firstName contains 'John' OR supervisor.firstName contains 'John') > > and then give that to an ERXFetchSpecification and use it to look up > "Employee" entities, then the results will exclude all Employees where the > supervisor is null, even though the Employee's firstName property is 'John'. > This is because the sql that gets generated from that FetchSpecification > will include "AND t0.SUPERVISOR_ID = T1.ID" in the WHERE clause. But I > need it to find *everyone* named John, whether or not the supervisor > property is null. > > Does anyone know of a way to do that without running two separate queries? > > > People may feel it is better to work around this, but is seems to me that > this is a bug in ERXOrQualifier. > > For now, your only solution may be to use a delegate on the expression > builder to fix the SQL. > > - ray > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev_______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc > > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc > > |