Skip site navigation (1) Skip section navigation (2)

Re: Limit vs setMaxRows issue

From: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Limit vs setMaxRows issue
Date: 2006-06-21 16:10:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
On Wed, June 21, 2006 12:00 pm, Kris Jurka wrote:

> I'm not sure how you would like the driver to tell the server that it
> doesn't want more than setMaxRows rows.  The defined API for this is using
>  LIMIT in your sql query.  The driver cannot do this for you (at least
> without parsing your query) because the query may already have a LIMIT or
> it may be something like an INSERT into a VIEW that has a DO INSTEAD
> SELECT rule on it.  If you're suggesting that we extended the
> frontend/backend protocol to include this extra information than that's
> definitely a feature request, not a bug report.

The backend protocol already supports maximum row limit if you use the
extended protocol.

I guess it's a legacy thing in the driver, but there really is no reason
to use the simple query protocol at all on recent postgresqls.


In response to


pgsql-jdbc by date

Next:From: Tom LaneDate: 2006-06-21 16:46:34
Subject: Re: Limit vs setMaxRows issue
Previous:From: Kris JurkaDate: 2006-06-21 16:00:06
Subject: Re: Limit vs setMaxRows issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group