Uh, LIMIT and OFFSET are not supported?
This may not be standard SQL, but some DBs
that Hibernate supports do support that SQL
extension. I thought that the whole point
of having different Dialects for different
types of databases was to support things
that are different, non-standard about them.
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 resul
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 resul
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 t
: Timothy Kettering [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 17, 2003 5:39 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Hibernate] problems with date comparision
>
>
>
> Good suggestion. I checked the database and it's in datetime
> format.
> It's
Good suggestion. I checked the database and it's in datetime format.
It's storing the time too because the time shows up properly when I do
entries, and it also gets retrieved properly if I retrieve an single
entry to match a timestamp.
I even checked the hbm.xml file - timestamp as well. An
The first thought that comes to mind is that your database column is not
storing
time information, i.e. year/month/day only. You might want to take a look
at that.
-Original Message-
From: Timothy Kettering [mailto:[EMAIL PROTECTED]
Sent: Friday, January 17, 2003 4:35 PM
To: [EMAIL PROTEC
