Hibernate 2.1.2

Hi,

How can I write this ORACLE query in HQ ?:


select count(d.ED_ID), SUBSTR(d.ED_VALUE_STRING,1,3) kvc
from epd_details d,
epd p, columns c, keylist_values kv
where
(d.ED_EPD_ID = p.EPD_ID) and
(d.ED_COL_ID = c.COL_ID) and
(d.ED_KLD_ID = kv.KLD_ID) and
(kv.KLD_KL_ID = 15 )
group by SUBSTR(d.ED_VALUE_STRING,1,3);

Any help appreciated. Thx.

Not possible yet, use direct JDBC

is it possible in a formula?

Hm, might be worth a try ...

Can someone tell me if it's possible Hibernate 3?
Thanks.
Mara

I try next with hibernate3 beta4 and caveatemptor


it isn't work - error is line 3:16: unexpected token: (


regards

i play with this query

and last hibernate 3

when I change line 275 in grammar/hql.g
( "by"! path ( COMMA! path )* )? // NOTE: The '!' after "by" tells ANTLR to skip AST generation for the token.

with

( "by"! expression ( COMMA! expression )* )? // NOTE: The '!' after "by" tells ANTLR to skip AST generation for the token.

it work

Joshua, is it fine ?

regards

Not a solution, but a work around....create a query in oracle that has the substr in it....then use hibernate to manipulate the query.

Lee

Hi,
I'm using Oracle 8 +hibernate 3+Tomcat 4.1
and this query work!

select substr(c.Date,6,2), avg(c.Value)from Table c
where substr(c.Date,1,4)='2003'
group by substr(c.Date,6,2)

Why do you say to us to use jdbc?

But I've notice a stange thing: using MySQL (and mysql dialect) this query doesn't work!
I recive an error message like this:"Alias undefined on query ..."
(Query syntax in mysql is correct, using jdbc it works!)
Can someone tell me the reason of this difference using Oracle and using MySQL?

Thanks.
Mara

h3 work with old parser, but new parser (from Josua) don't work

regards

Each database dialect has a number of standard and non-standard select functions. Oracle dialect has a very large number of them, I assume from the error (I have not looked) that MySQL does not have that function defined in the dlalect. See Oracle dialect source and add it to the MySQL dialect - if it works submit a patch.

Why the new parser version doesn't support this feature?
Is it a bug or there is a reason for this?
If this feature wont be in future Hibernate releases, maybe it's better if I don't use it in my code, or I can choose to use this feature without to change the Hibernate version that I'm using?
What advised to me?
Thanks.
Mara

I think that is bug.I send patch/workoaround before in this thread, but I don't know if it break another thing

regards