[rabbiaqaswar]

This property is already set in the persistence.xml file along with the batch size property which i mentioned earlier.

[jaikiran]

I am running out of ideas. The only other suggestion i can give you is to use the correct (perhaps the latest) JDBC driver of Oracle.

[rabbiaqaswar]

:) Thanks

Should i report it as a bug at Hibernate? Maybe it is something wrong at their end?

[jaikiran]

I would suggest posting in the Hibernate forums instead of filing a bug.

[rabbiaqaswar]

I did, three days back but got no reply from there:

http://forum.hibernate.org/viewtopic.php?t=987845&highlight=

[rabbiaqaswar]

One thing which I have noticed is that the query returns ids only for the first ten records. After that, it always returns the Object[] e.g. setFirstResult(20) & setMaxResults(10), also gives Object[]'s.

[rabbiaqaswar]

Infact it gives ids only when the setFirstResult is set at 0 i.e. setFirstResult(0). When the value of setFirstResult is anything other than 0, the query returns Object[]'s.

[jaikiran]

The indexing starts with 1 and not 0. So when setFirstResult(0) is used, it probably gets ignored.

[rabbiaqaswar]

So does that mean that the query is supposed to return Object[] containg the result & the index, even if i am only retreiving a single value in the query?

[jaikiran]

"jaikiran" wrote:
The indexing starts with 1 and not 0. So when setFirstResult(0) is used, it probably gets ignored.

I'm sorry. i re-read the javadocs and it appears the indexing does start from 0.

"rabbiaqaswar" wrote:

So does that mean that the query is supposed to return Object[] containg the result & the index, even if i am only retreiving a single value in the query?

*As far as i know*, that's not how its expected to behave. The query output should be the same number of columns that you have mentioned in the select clause.

[rabbiaqaswar]

I just checked the javadoc of javax.persitence.Query, method setFirstResult and it says:

Query setFirstResult(int startPosition)

Set the position of the first result to retrieve.

Parameters:
startPosition - the start position of the first result, numbered from 0
Returns:
the same query instance
Throws:
IllegalArgumentException - if argument is negative

So the index must be starting from 0. Even in my query the first result i get when i setFirstResult to 0 is the user id in first row in the table and get the second id when the setFirstResult is set to 1.

[jaikiran]

How about changing your query to return the entire User object instead of just the ids? Maybe like this:

SELECT USR FROM USER USR, USERWATCH UW WHERE USR.ADDEDBYID =1 AND USR.COUNTRY = CAS
E WHEN (UW.COUNTRY is null) THEN USR.COUNTRY ELSE UW.COUNTRY END AND USR.ALIVE = 'A'

See if that works.

[rabbiaqaswar]

Okay, will try this now then.

Thanks