On 2/3/15 5:26 AM, 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.
You might be able to add something like WHERE FALSE to the RETURNING
clause, but I agree with Andres; this seems like premature optimization.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
