You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by sudhakar <su...@co.brazos.tx.us> on 2007/10/11 04:21:35 UTC

limit

Everything I've read so far says that Derby does not implement LIMIT
which lets you write queries that return only so many rows in the resultset.

Is this still the case or has this changed? Or are there initiatives to
implement this? This seems to be a serious limitation when working with
large databases and you want to take advantage of Derby in a standalone
application.

-sud

Re: limit

Posted by Thomas Nielsen <Th...@Sun.COM>.
Hi Sudhakar,

Please note, as explained in DERBY-2998 and DERBY-581, that we are *not* 
implementing LIMIT (a dialect word), but rather following the SQL 
standard using the ROW_NUMBER() rank function.

There is still a way to go, and as Brian says if you're interested in 
helping we'd appreciate that a lot!

BR,
Thomas

Bryan Pendleton wrote:
>> Everything I've read so far says that Derby does not implement LIMIT
>> which lets you write queries that return only so many rows in the 
>> resultset.
>>
>> Is this still the case or has this changed? Or are there initiatives to
>> implement this? 
> 
> DERBY-581 and DERBY-2998 are relevant, I believe.
> 
> If you are interested in helping us work on this, there are lots of
> ways to help contribute to the effort, and we'd love to have more people 
> involved!
> 
> thanks,
> 
> bryan
> 

-- 
Thomas Nielsen

Re: limit

Posted by Bryan Pendleton <bp...@amberpoint.com>.
> Everything I've read so far says that Derby does not implement LIMIT
> which lets you write queries that return only so many rows in the resultset.
> 
> Is this still the case or has this changed? Or are there initiatives to
> implement this? 

DERBY-581 and DERBY-2998 are relevant, I believe.

If you are interested in helping us work on this, there are lots of
ways to help contribute to the effort, and we'd love to have more people involved!

thanks,

bryan