Re: Allow WHEN in INSTEAD OF triggers

2020-01-06 Thread Dean Rasheed
On Sat, 28 Dec 2019 at 16:45, David Fetter wrote: > > On Sat, Dec 28, 2019 at 12:12:30AM -0300, Alvaro Herrera wrote: > > On 2019-Dec-28, David Fetter wrote: > > > > > While noodling around with an upcoming patch to remove user-modifiable > > > RULEs, I noticed that WHEN conditions were disallowed

Re: Allow WHEN in INSTEAD OF triggers

2019-12-28 Thread David Fetter
te! Consider donating to Postgres: http://www.postgresql.org/about/donate >From d6af8b66347b31e14d961e83023dbcb658bea64b Mon Sep 17 00:00:00 2001 From: David Fetter Date: Fri, 27 Dec 2019 18:57:31 -0800 Subject: [PATCH v2] Allow WHEN in INSTEAD OF triggers To: hackers MIME-Version: 1.0 Content-Type: mul

Re: Allow WHEN in INSTEAD OF triggers

2019-12-28 Thread David Fetter
On Fri, Dec 27, 2019 at 10:29:15PM -0500, Tom Lane wrote: > David Fetter writes: > > While noodling around with an upcoming patch to remove user-modifiable > > RULEs, I noticed that WHEN conditions were disallowed from INSTEAD OF > > triggers for no discernible reason. This patch removes that > >

Re: Allow WHEN in INSTEAD OF triggers

2019-12-27 Thread Tom Lane
David Fetter writes: > While noodling around with an upcoming patch to remove user-modifiable > RULEs, I noticed that WHEN conditions were disallowed from INSTEAD OF > triggers for no discernible reason. This patch removes that > restriction. This seems like a remarkably bad idea. The point of a

Re: Allow WHEN in INSTEAD OF triggers

2019-12-27 Thread Alvaro Herrera
On 2019-Dec-28, David Fetter wrote: > While noodling around with an upcoming patch to remove user-modifiable > RULEs, I noticed that WHEN conditions were disallowed from INSTEAD OF > triggers for no discernible reason. This patch removes that > restriction. If you want to remove the restriction,

Allow WHEN in INSTEAD OF triggers

2019-12-27 Thread David Fetter
m: David Fetter Date: Fri, 27 Dec 2019 18:57:31 -0800 Subject: [PATCH v1] Allow WHEN in INSTEAD OF triggers To: hackers MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="2.24.1" This is a multi-part message in MIME format. --2.24.1 Content-Type: text/pl