Re: BUG #15623: Inconsistent use of default for updatable view
Dean Rasheed <dean.a.rasheed@gmail.com>
From: Dean Rasheed <dean.a.rasheed@gmail.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
Roger Curley <rocurley@gmail.com>, pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>
Date: 2019-02-10T11:18:46Z
Lists: pgsql-bugs, pgsql-hackers
Attachments
- view-insert-null-default-fix-v4.patch (application/octet-stream) patch v4
On Sun, 10 Feb 2019 at 00:48, Dean Rasheed <dean.a.rasheed@gmail.com> wrote: > However, this is still not the end of the story, because it doesn't > fix the fact that, if the view has a DO ALSO rule on it, single-row > inserts behave differently from multi-row inserts. In that case, each > insert becomes 2 inserts, and defaults need to be treated differently > in each of the 2 queries. That's going to need a little more thought. > Here's an updated patch to handle that case. In case it's not obvious, I'm not intending to try to get this into next week's updates -- more time is needed to be sure of this fix, and more pairs of eyes would definitely be helpful, once those updates have been shipped. Regards, Dean
Commits
-
Further fixing for multi-row VALUES lists for updatable views.
- 431471e1f2a2 9.4.22 landed
- 556fdd49c9e0 9.5.17 landed
- 133923aeb1b6 9.6.13 landed
- 0a08446308c8 10.8 landed
- 6ccb97337326 11.3 landed
- ed4653db8ca7 12.0 landed
-
Fix DEFAULT-handling in multi-row VALUES lists for updatable views.
- 41531e42d34f 12.0 landed
- fbec6fa38ade 11.3 landed
- 2b1971c0318b 10.8 landed
- d31e421d7df1 9.6.13 landed
- 90f91bfbd76f 9.5.17 landed
- 5a73edf050ed 9.4.22 landed