Re: Fetch zero result rows when executing a query? - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: Fetch zero result rows when executing a query?
Date
Msg-id 54D20589.1010505@joh.to
Whole thread Raw
In response to Re: Fetch zero result rows when executing a query?  ("Stephen R. van den Berg" <srb@cuci.nl>)
Responses Re: Fetch zero result rows when executing a query?  (Shay Rojansky <roji@roji.org>)
List pgsql-hackers
On 2/4/15 12:36 PM, Stephen R. van den Berg wrote:
> Marko Tiikkaja wrote:
>> This seems to be a common pattern, and I think it's a *huge* mistake
>> to specify maxrows=1 and/or ignore rows after the first one in the
>> driver layer.  If the user says "give me the only row returned by
>
> I guess it depends on the amount of backpressure you can excert on
> the sql "programmer".
> If you are writing a driver which just has to run applications
> written by third parties in the most efficient way, the outline
> I gave above is best.
> If the driver has a way to communicate with the one writing
> the SQL, then giving warnings is better.

Screw warnings, that should be an error.  "I tried to execute your 
query, but something went wrong."

Anyway, this is getting really off topic now, and that's my fault, so I 
should shut up.


.m



pgsql-hackers by date:

Previous
From: "Stephen R. van den Berg"
Date:
Subject: Re: Fetch zero result rows when executing a query?
Next
From: Michael Paquier
Date:
Subject: Re: Unnecessary pointer-NULL checks in pgp-pgsql.c