Hello,

I upgraded my HypersonicSQL 1.7.1 to 1.7.2_Alpha_T because
this version allows the usage of BIGINT identity columns.

However...I can run inserts and selects with my little app but
doing one query I get following exception.

I have no idea what is going wrong...some issue with the 'dialect'?
Can someone interpret Error: -16 or SQLState: 37000, respectively?

Thanks for any kind of help or suggestion!
mac

22:02:30,733 WARN net.sf.hibernate.util.JDBCExceptionReporter:38 - SQL Error: -16, SQLState: 37000
22:02:30,733 ERROR net.sf.hibernate.util.JDBCExceptionReporter:46 - Wrong data type: TOP m in statement [select top ? messager0_.messageId as messageId, messager0_.tstamp as tstamp, messager0_.destinationId as destinat3_, messager0_.languageId as languageId, messager0_.projectStatusId as projectS5_, messager0_.reviewerId as reviewerId, messager0_.reviewerStatusId as reviewer7_, messager0_.sourceURI as sourceURI, messager0_.text as text from t_Message messager0_ where (destinationId in(? , ? , ? , ? , ?))and(languageId in(? , ? , ? , ?))and(reviewerStatusId=0 ) order by tstamp asc]
22:02:30,733 ERROR net.sf.hibernate.util.JDBCExceptionReporter:38 - Could not execute query
java.sql.SQLException: Wrong data type: TOP m in statement [select top ? messager0_.messageId as messageId, messager0_.tstamp as tstamp, messager0_.destinationId as destinat3_, messager0_.languageId as languageId, messager0_.projectStatusId as projectS5_, messager0_.reviewerId as reviewerId, messager0_.reviewerStatusId as reviewer7_, messager0_.sourceURI as sourceURI, messager0_.text as text from t_Message messager0_ where (destinationId in(? , ? , ? , ? , ?))and(languageId in(? , ? , ? , ?))and(reviewerStatusId=0 ) order by tstamp asc]

Hi, myself again...

Taking a closer look, I found the bug, I think.

As stated in the log, the TOP value is not set! Although I have
specified in the code setMaxResults, it seems, that Hibernate
does not put the value into the SQL statement!
(By the way, If i omit the setMaxResults, it works ;-) )


Can somebody confirm me that this is really a Hibernate bug
or am I missing here something?

All is working just fine for me with 2.1rc1 and the version of HSQL that is in our CVS.

Weird....I now migrated back to 2.1beta4 and there its running!
(at least for me ;-) )

If I look to the CVS marks, this was also the version from where
on some changes were made related to SELECT TOP.

However, I have not looked into the source. Maybe tomorrow...

Try the version of HSQL from our CVS. IIRC, there are bugs in the latest HSQL release.