Title: [Hibernate] Test suite now has 12 errors, up from 11
yes my bad. forgot to commit
the last change i did - will do it later today when i get back to my
box.
-max
Fra: [EMAIL PROTECTED]
på vegne af Joshua DavisSendt: sø 19-12-2004 03:09Til:
Hibernate-DevelEmne: [Hibernate] Test s
This EJBQL2 query:
FROM Foo foo, IN(foo.bars) bar
Is exactly equivalent to this HQL/EJBQL3 query:
FROM Foo foo JOIN foo.bars bar
Joshua Davis wrote:
Okay, that worked so I'm committing it. The new rule seems a little
strange to me, but perhaps I don't understand what it's supposed to do.
Gavin King wrote:
This EJBQL2 query:
FROM Foo foo, IN(foo.bars) bar
Is exactly equivalent to this HQL/EJBQL3 query:
FROM Foo foo JOIN foo.bars bar
Yes, so I gathered from the grammar. It's no big deal, but the
following would be slightly 'nicer' IMHO:
FROM Foo foo IN (foo.bars) bar
The us
Oh, don't get me wrong, it's a crappy syntax. But that's what the EJB
2.1 spec says
Joshua Davis wrote:
Gavin King wrote:
This EJBQL2 query:
FROM Foo foo, IN(foo.bars) bar
Is exactly equivalent to this HQL/EJBQL3 query:
FROM Foo foo JOIN foo.bars bar
Yes, so I gathered from the grammar.
That looks much nicer. Thanks, Joshua.
The IN expression is translated into inner join. There is EJBQLTest
(next to HQLTest) which compares translation results of EJBQL and
equivalent HQL queries. So, you can always look at them to see what is
expected.
Thanks.
> -Original Message-
> From
..is now removed (i hope ;)
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
http://jboss.com
---
SF email is sponsored by - The IT Product Guide
Read honest & candid
Guys, in the new query parser, some SQL functions like upper() and
max() do not work in the select clause, since they expect to be
passed the type of the expression they are applied to.
Currently MethodNode.resolve() passes null:
SQLFunction function =
getSessionFactoryHelper().findSQLFunct
Try it now. :)
Gavin King wrote:
Guys, in the new query parser, some SQL functions like upper() and
max() do not work in the select clause, since they expect to be
passed the type of the expression they are applied to.
Currently MethodNode.resolve() passes null:
SQLFunction function =
getSe
Great, you made my day!
:)
Joshua Davis wrote:
Try it now. :)
Gavin King wrote:
Guys, in the new query parser, some SQL functions like upper() and
max() do not work in the select clause, since they expect to be
passed the type of the expression they are applied to.
Currently MethodNode.resolve() pa
