Re: [HACKERS] SQL procedures - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: [HACKERS] SQL procedures
Date
Msg-id CADkLM=dQY=p13Mk-3gNpRLGBm3mQaLHqEFjzMJh_rTjchoo-Pw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] SQL procedures  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] SQL procedures
List pgsql-hackers

T-SQL procedures returns data or OUT variables.

I remember, it was very frustrating

Maybe first result can be reserved for OUT variables, others for multi result set


It's been many years, but if I recall correctly, T-SQL returns a series of result sets, with no description of the result sets to be returned, each of which must be consumed fully before the client can move onto the next result set. Then and only then can the output parameters be read. Which was very frustrating because the OUT parameters seemed like a good place to put values for things like "result set 1 has 205 rows" and "X was false so we omitted one result set entirely" so you couldn't, y'know easily omit entire result sets. 

pgsql-hackers by date:

Previous
From: Ashwin Agrawal
Date:
Subject: Re: [HACKERS] Commits don't block for synchronous replication
Next
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] SQL procedures