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> |
Subject: | Re: plpgsql - additional extra checks |
Date: | 2017-01-13 01:46:39 |
Message-ID: | c46bf7fc-e0e5-f8f7-ad69-92b171204cfc@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/11/17 5:54 AM, Pavel Stehule wrote:
> + <term><varname>too_many_rows</varname></term>
> + <listitem>
> + <para>
> + When result is assigned to a variable by <literal>INTO</literal> clause,
> + checks if query returns more than one row. In this case the assignment
> + is not deterministic usually - and it can be signal some issues in design.
Shouldn't this also apply to
var := blah FROM some_table WHERE ...;
?
AIUI that's one of the beefs the plpgsql2 project has.
FWIW, I'd also be in favor of a NOMULTI option to INTO, but I don't see
any way to do something like that with var := blah FROM.
--
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 | Fujii Masao | 2017-01-13 01:56:36 | Re: Proposal for changes to recovery.conf API |
Previous Message | Peter Geoghegan | 2017-01-13 01:36:19 | Re: WIP: [[Parallel] Shared] Hash |