Query.setProperties( Object ) question.

Shino · **Posted:** Fri Sep 19, 2003 2:33 pm

I can't find a lot in the documentation about this guy.

Does
Query.setProperties( Object )
work with native sql queries?

Here's what I have.
QUERY

Code:

select {d.*} 
from department {d} 
where {d}.deptno = :deptno

passing in an object (Department) which has a

Code:

private String deptno;

on it.

Getting the following Exception:

Code:

net.sf.hibernate.QueryException: in expected: {d} [select   {d.*} 
from   department {d} 
where   {d}.deptno = :deptno]

{d} is defined in my query object.

When I do

Code:

Query.setString( "deptno", department.getDeptno() );

The query executes correctly.

Any ideas?
Thanx,

max · **Posted:** Fri Sep 19, 2003 2:57 pm

Sounds like a bug.

Could you make a small test.hbm.xml and java file illustrating the problem and submit it to the JIRA ? That will speed it up ;)

thanx!

Shino · **Posted:** Mon Sep 22, 2003 12:26 pm

Looked deeper into this.

Seems as if it is handling the Native sql call as HQL.

The query dies after parsing "department."

it's expecting a class path, ( saw indexOf( '.' ) so I assume that is what was going on. Then it sets expectingIn to true. The next thing it sees is {d} and it chokes on it. Making a little program to reproduce it, will put it in jira when it's done.

The way we are trying to do things, this is pretty crutial. Is this a trivial change I can make in my hibernate code until it is fixed?

Thanx,
Chris

max · **Posted:** Mon Sep 22, 2003 12:36 pm

Shino wrote:

Looked deeper into this.

Seems as if it is handling the Native sql call as HQL.

The query dies after parsing "department."

it's expecting a class path, ( saw indexOf( '.' ) so I assume that is what was going on. Then it sets expectingIn to true. The next thing it sees is {d} and it chokes on it. Making a little program to reproduce it, will put it in jira when it's done.

The way we are trying to do things, this is pretty crutial. Is this a trivial change I can make in my hibernate code until it is fixed?

Thanx,
Chris

Don't use createSQLQuery ;)

Well - the best thing you can do is to submit a test program and put it in the JIRA .... it get's WAAAY more attention when it's easy to reproduce ;)

Shino · **Posted:** Mon Sep 22, 2003 2:01 pm

Opened an issue in Jira on this ( #353 ) and attached a tester.

Please let me know if there is something else I can do.

Shino · **Posted:** Mon Oct 13, 2003 9:00 am

Hey guys,

Just wondering if this fix was released with 2.1 b4.

I'm still getting the same error in my code as well as the test program I uploaded to Jira.

"in expected: {tableAlias}

Thanx,

Shino · **Posted:** Mon Oct 13, 2003 10:16 am

Nevermind... My bad.

Eclipse was pulling from an old jar. After flushing it and importing fresh it worked fine.

Thanks guys!