24 messages in org.postgresql.pgsql-jdbcRe: Limit vs setMaxRows issue
FromSent OnAttachments
Sebastiaan van ErkJun 21, 2006 2:11 am 
Dave CramerJun 21, 2006 7:56 am 
Sebastiaan van ErkJun 21, 2006 8:48 am 
Kris JurkaJun 21, 2006 8:59 am 
A.M.Jun 21, 2006 9:09 am 
Tom LaneJun 21, 2006 9:46 am 
Oliver JowettJun 21, 2006 3:52 pm 
Sebastiaan van ErkJun 22, 2006 1:35 am 
Mark LewisJun 22, 2006 9:15 am 
David WallJun 22, 2006 9:36 am 
Sebastiaan van ErkJun 22, 2006 1:13 pm 
Marc HerbertJul 10, 2006 1:50 am 
Marc HerbertJul 10, 2006 1:59 am 
Marc HerbertJul 10, 2006 2:05 am 
Oliver JowettJul 10, 2006 11:32 pm 
Oliver JowettJul 10, 2006 11:37 pm 
Marc HerbertJul 11, 2006 2:48 am 
Marc HerbertJul 11, 2006 3:00 am 
Oliver JowettJul 11, 2006 3:45 am 
Marc HerbertJul 11, 2006 5:14 am 
Oliver JowettJul 11, 2006 10:01 pm 
Marc HerbertJul 12, 2006 3:22 am 
Markus SchaberJul 12, 2006 3:59 am 
Marc HerbertJul 20, 2006 11:52 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Limit vs setMaxRows issueActions...
From:A.M. (age@themactionfaction.com)
Date:Jun 21, 2006 9:09:59 am
List:org.postgresql.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.

-M