Hi,
I've noticed that using setParameter of the Query object is much slower than using the "typed" methods like setString(), setLong() etc.
I would expect that from the setParameter() version without the Type parameter because Hibernate needs to find out what Type is actually needed, but even the setParameter() call with the correct Type is slower than the typed method version.

I am using Hibernate 3.2.2. Maybe it is already fixed in the current version?

Is this a know behaviour of this method? If so (and if I'm not wrong ;-)) it would be nice if you could stress the fact in the javadocs of this method.
If you try to implement a generic DAO base class you tend to use the setParameter() method and not the typed ones. This will cause a performance reduction at the basis of all DAO implementations!

My development environment:
Java 1.4.2
Hibernate 3.2.2.
DB: Oracle 10g
Oracle Driver Implementation Version: 10.2.0.3.0

Best regards,

Christian

Tried it at home with an Oracle Express and a different database. There was no difference in the query execution time. I guess it is an issue with the oracle version/database/driver/ combination at work.

I too had never seen a significant difference in the two method calls, which made your original post somewhat curious. Time to figure out what the heck is going on with those JDBC drivers at work!

I've found the explanation for this behaviour. It is simple and clear but it can be overlooked easily...
I simply made a mistake in my mapping file. A property of my Hibernate Pojo was mapped as an int but the column
type in the oracle database was a vachar2! I know that there are only integers in the database, therefore I've never noticed the wrong column type...
Oracle (and maybe other databases too?) is extremely bad when it comes to type conversion. Even when you execute a SQL statement directly (e.g. in Toad) you get a noticeable performance drop if you provide a numerical parameter for a varchar2 column.
Is there a way to produce an error message for this? I've written some test code that compares the Hibernate Metadata with the Metadata that is returned from a JDBC ResultSet to find other mapping mistakes in my Hibernate mapping files. This works for me, but a more general solution might be helpful.

Chris