Re: [HACKERS] merging some features from plpgsql2 project
От | Jim Nasby |
---|---|
Тема | Re: [HACKERS] merging some features from plpgsql2 project |
Дата | |
Msg-id | 9484f6f5-cfb3-db45-cc0f-bbc336587f81@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] merging some features from plpgsql2 project (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: [HACKERS] merging some features from plpgsql2 project
Re: [HACKERS] merging some features from plpgsql2 project |
Список | 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)
В списке pgsql-hackers по дате отправления: