I think I found a bug with the paging option for Oracle. When I use setFirstResult(int) it seems to be ignored and be set to zero.

The SQL statement below is correct! But I set the following values:

firstResult: 1000
maxResult: 2001
list size before sql: null

The size of the result list was:
list size after sql: 2001

As I paged down the result become bigger and bigger (+ pageSize for each select). Can I somehow display the bind variables which are set for the statement?

As I couldn't find it in the changelog for 3.0.2 I didn't update so far.

TIA,
caterham


Hibernate version:
3.0.1
Name and version of the database you are using:
Oracle 9.2.0.6
The generated SQL (show_sql=true):
select * from ( select row_.*, rownum rownum_ from ( select [...] from SIGNALPARAMS this_ where this_.SIG_AUFS_ID=? ) row_ where rownum <= ?) where rownum_ > ?

enabled debug level logging on org.hibernate.type

FAQ!

Just the one with the bind variables? Or even the problem with the setFirstResult(int) stuff? I couldn't find anything in the FAQ! Sorry.


That didn't work. I don't get any bind variables printed out on the console. The log level for the handler is set correctly.

But the main reason for this post remains the same.
I can set firstResult but it seems to be ignored.

TIA,
caterham

max results is the page size, not the maximum row number.

Thanks. After thinking about the method name it was clear for me too. ;-)