Re: Fetch zero result rows when executing a query?

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
Cc: Shay Rojansky <roji(at)roji(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fetch zero result rows when executing a query?
Date: 2015-02-04 11:42:01
Message-ID: 54D20589.1010505@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2015-02-04 12:00:08 Re: Unnecessary pointer-NULL checks in pgp-pgsql.c
Previous Message Stephen R. van den Berg 2015-02-04 11:36:56 Re: Fetch zero result rows when executing a query?