anonymous wrote : Path expression navigability is composed using ?inner join?
semantics. That is, if the value of a non-terminal cmr-field in the path expression is
null, the path is considered to have no value, and does not participate in the
determination of the result.
|
If that's the standard, then that is just assinine. Why should I have to choose
between 16 EJB-QL queries or "fake" nulls?!? Imagine 8 optional parameters. That
would require 256 EJB-QL queries, rendering "fake" nulls virtually inevitable!
If I were generating the SQL myself, I would do this to generate the component of the
WHERE clause for one comparison (in psuedo code):
| if ({the parameter is null})
| whereComponent = field + " IS NULL ";
| else
| whereComponent = field + " = " + parameter;
|
If this violates the standard, then the standard is overdue for a change. I heard
that UNIONS were coming out in a future release. That's a cheesy solution to me.
There's no reason why it can't be a simple and fast query. UNIONS are slow.
I'm not blaming JBoss at all for this. I blaim the JCP. I love J2EE. It has a lot
of good well thought out standards. But this is not one of them.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836286#3836286
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3836286
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
