Re: Limit vs setMaxRows issue

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.

-M