Hello all.

I've had queries working in my hibernate projects before when I used it about 6 months ago. For some reason now I'm always getting the same exception regardless which (of the 2) classes I try to query on now. I'm hoping somebody will have some insight to point me in the right direction.

I can successfully load() an object, even update() an object, but I cannot run a query. I have hibernate2.jar installed in my jboss default app's lib folder (and its dependencies as far as i can tell).

Here is the code that executes the query...



Here is the exception that is thrown...

Message : 16:14:10,015 INFO [STDOUT] unexpected token: as [select u from Users as u where u.userName = 'somename']

If you need the rest of the stack trace let me know (it's long so I don't want to clutter this message).

Here is a snip from my mapping file...



I hope you can see what I'm doing wrong. I'm going batty! I may end up getting the source code to hibernate to solve this, but this seems like overkill to me.

Thanks,

Mal.

Query q = session.createQuery("select u from qnext.bo.database.to.UserTO as u where u.userName = 'somename'");


Note: In most cases, its better to use parameter arguments.

Shoot! I haven't tried it but I'm almost sure you're right. I forgot to fully qualify the object name. Perhaps I should remove the package information from the mapping file. It makes the queries a little ugly.

Thanks.

Mal.

Yep, that was it. It was obviously my mistake, and an obvious one, but I feel the error message could have helped point me in the right direction a little more. Something along the lines of "could not create object XX", etc.

Mal.

instead of using ='somename' use =\'somename\' in Query

Its not a matter of fully qualified name or not. You were attempting to write a query against the table name, not the class name.

You always have to option of using Java itself to help avoid these issues.
eg


So the compiler can catch the error if it does not exist.