Allright! That worked beautifully. My question is.. if LIMIT is not supported, then why did it work just fine for the other 2 types of queries I'm using it in... and it even returns the correct amount of results i want! Kinda dangerous to let that in, if its going to give unpredictable results. Would be nice to have it at least warn or print out some error statement if LIMIT is found in the query.
Then again, I really should have read the documentation more carefully, but I was just typing it out like standard sql, and gave it a try and it seemed to work...
Thanks again.
-tim
On Friday, January 17, 2003, at 07:50 PM, Gavin King wrote:
Note that the Hibernate query language does not support the "limit" syntax. Use setMaxResults() instead.
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your clients even if they use browsers that are limited to 40 bit encryption. Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
