Re: [HACKERS] merging some features from plpgsql2 project - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] merging some features from plpgsql2 project
Date
Msg-id CAFj8pRAUgCtH3aHAvsWK1Q1gm6o0KSmo_7N7nhB6_a1fOjy=cQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] merging some features from plpgsql2 project  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers


2017-01-08 3:31 GMT+01:00 Jim Nasby <Jim.Nasby@bluetreble.com>:
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 invite any ideas?

Regards

Pavel
 

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)

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] merging some features from plpgsql2 project
Next
From: Ryan Murphy
Date:
Subject: Re: [HACKERS] Adding type info etc for inheritance errmsg: "childtable is missing column ..."