| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix optimization of foreign-key on update actions |
| Date: | 2019-02-05 16:02:08 |
| Message-ID: | 878syu5j4i.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Peter" == Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
Peter> The SQL standard seems clear
ha
hahaha
HAHAHAHAHAHA
(since when has the SQL standard ever been clear?)
SQL2016, 15.17 Execution of referential actions
10) If a non-null value of a referenced column RC in the referenced
table is updated to a value that is distinct from the current value
of RC, then,
[snip all the stuff about how ON UPDATE actions work]
does that "is distinct from" mean that IS DISTINCT FROM would be true,
or does it mean "is in some way distinguishable from"? Nothing I can see
in the spec suggests the latter.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-02-05 16:20:52 | Re: Fix optimization of foreign-key on update actions |
| Previous Message | Peter Eisentraut | 2019-02-05 15:36:31 | Fix optimization of foreign-key on update actions |