Hello Bruce,
> Triggers are designed to check and modify input data, and since DELETE
> has no input data, it makes no sense.
Sorry, I am still ambiguous. You say that DELETE has no input data,
but doc says that it has:
https://www.postgresql.org/docs/current/trigger-definition.html
For a ro
Hello Eugen,
> https://dbfiddle.uk/?rdbms=postgres_12&fiddle=95ed9fab6870d7c4b6266ea4d93def13
sorry, forget to update link to the latest example:
https://dbfiddle.uk/?rdbms=postgres_12&fiddle=8e114ccc9f15a30ca3115cdc6c70d247
--
Best regards,
Eugen Konkov
Hi again.
> Thinking some more on this, I now don't think a TODO makes sense, so I
> have removed it.
Please look into this example:
https://dbfiddle.uk/?rdbms=postgres_12&fiddle=95ed9fab6870d7c4b6266ea4d93def13
This is real life code from our production.
You can see that this is important to
On Mon, Nov 11, 2019 at 07:00:22PM +0300, Liudmila Mantrova wrote:
>
> > 8 нояб. 2019 г., в 0:26, Bruce Momjian написал(а):
> >
> > First, notice "only", which was missing from the later sentence:
> >
> >For INSERT and UPDATE
> >operations [only], the trigger may modify the
> >NEW r
> 8 нояб. 2019 г., в 0:26, Bruce Momjian написал(а):
>
> First, notice "only", which was missing from the later sentence:
>
>For INSERT and UPDATE
>operations [only], the trigger may modify the
>NEW row before returning it.
>
> which I have now added with my applied patch to all s
Hello Eugen,
Saturday, November 9, 2019, 2:05:02 PM, you wrote:
> Hello Bruce,
> Friday, November 8, 2019, 12:28:18 AM, you wrote:
>> On Thu, Nov 7, 2019 at 04:26:55PM -0500, Bruce Momjian wrote:
>>> On Thu, Nov 7, 2019 at 11:24:29AM +0200, Eugen Konkov wrote:
>>> > >> As far as allowing DELE
Hello Bruce,
Friday, November 8, 2019, 12:28:18 AM, you wrote:
> On Thu, Nov 7, 2019 at 04:26:55PM -0500, Bruce Momjian wrote:
>> On Thu, Nov 7, 2019 at 11:24:29AM +0200, Eugen Konkov wrote:
>> > >> As far as allowing DELETE to modify the trigger row for RETURNING, I am
>> > >> not sure how muc
On Thu, Nov 7, 2019 at 04:26:55PM -0500, Bruce Momjian wrote:
> On Thu, Nov 7, 2019 at 11:24:29AM +0200, Eugen Konkov wrote:
> > >> As far as allowing DELETE to modify the trigger row for RETURNING, I am
> > >> not sure how much work it would take to allow that, but it seems like it
> > >> is a v
On Thu, Nov 7, 2019 at 11:24:29AM +0200, Eugen Konkov wrote:
> Hello Eugen,
>
> Thursday, November 7, 2019, 11:20:32 AM, you wrote:
>
> >> I looked in the CREATE TRIGGER manual page and found this:
>
> >> https://www.postgresql.org/docs/12/sql-createtrigger.html
> >> If the trig
Hello Eugen,
Thursday, November 7, 2019, 11:20:32 AM, you wrote:
>> I looked in the CREATE TRIGGER manual page and found this:
>> https://www.postgresql.org/docs/12/sql-createtrigger.html
>> If the trigger fires before or instead of the event, the trigger
>> can skip the
> I looked in the CREATE TRIGGER manual page and found this:
> https://www.postgresql.org/docs/12/sql-createtrigger.html
> If the trigger fires before or instead of the event, the trigger
> can skip the operation for the current row, or change the row
> being insert
On Tue, Oct 29, 2019 at 05:54:36PM +0200, Eugen Konkov wrote:
> Hi.
>
> This is not clear from doc, so I have asked on IRC too.
>
> from the DOC: https://www.postgresql.org/docs/current/trigger-definition.html
> In the case of INSTEAD OF triggers, the possibly-modified row returned by
> each tr
Hi.
This is not clear from doc, so I have asked on IRC too.
from the DOC: https://www.postgresql.org/docs/current/trigger-definition.html
In the case of INSTEAD OF triggers, the possibly-modified row returned by each
trigger becomes the input to the next trigger
I modify OLD row, thus I expect
13 matches
Mail list logo
