| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Joel Jacobson <joel(at)trustly(dot)com> |
| Subject: | Re: merging some features from plpgsql2 project |
| Date: | 2017-01-08 02:31:33 |
| Message-ID: | 9484f6f5-cfb3-db45-cc0f-bbc336587f81@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/7/17 5:39 AM, Pavel Stehule wrote:
>
> I checked current implementation of FOUND variable. If we introduce new
> auto variable ROW_COUNT - exactly like FOUND, then it doesn't introduce
> any compatibility break.
Except it would break every piece of code that had a row_count variable,
though I guess you could see which scoping level the variable had been
defined in.
I think the right solution in this case is to replace GET DIAGNOSTICs
with something easier to use, but I'm not sure what that would be.
I think this is another example of where not using some kind of
character to distinguish variables screws us. :/
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2017-01-08 02:39:24 | Re: merging some features from plpgsql2 project |
| Previous Message | Jim Nasby | 2017-01-08 02:27:15 | Re: merging some features from plpgsql2 project |