Hi,
On 2015-02-03 12:26:33 +0100, Shay Rojansky wrote:
> Sorry if this has been asked before, couldn't find any mention...
>
> I'm working on the Npgsql, the .NET driver for PostgreSQL, and am trying to
> find a way to execute a query but without fetching any rows. The Execute
> message has a maximum result-row count, but zero is documented to mean
> "fetch all rows".
>
> The use case would be sending a query which might modify or might not (e.g.
> UPDATE), but we know that the user is uninterested in any result row.
>
> My current workaround is to specify maxrows=1, was wondering if I missed a
> better alternative.
Is this really a relevant optimization? If the user doesn't want
results, RETURNING shouldn't be specified... Sure, sometimes the same
query will be reused over cases where you want the results and those
where you don't, but I doubt this is worthy of optimization.
Greetings,
Andres Freund
-- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services