Re: event trigger support for PL/Python - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: event trigger support for PL/Python
Date
Msg-id CAFj8pRDgdnG2oQ8E431epguQkNS8g0kEtN2H1KyC9hZi9gzMfg@mail.gmail.com
Whole thread Raw
In response to Re: event trigger support for PL/Python  ("Euler Taveira" <euler@eulerto.com>)
List pgsql-hackers


pá 8. 8. 2025 v 1:31 odesílatel Euler Taveira <euler@eulerto.com> napsal:
On Thu, Aug 7, 2025, at 1:53 AM, Pavel Stehule wrote:
> Minimally - you should to use PLPY_DML_TRIGGER instead PLPY_TRIGGER
>

I didn't use DML terminology for the same reason Peter said in another thread
[1]; let's *not* introduce a new terminology (DML trigger).

> Maybe the name "trigtype" can be better than "is_trigger". The
> similarity with PLpgSQL has some benefits, but in this case I think so
> the plpgsql design (of this case) is minimally confusing (and really
> the related part in plpgsql_compile_callback can be cleaned). How much
> - this is a question. There are two different things that are mixed
> together (and this is what I dislike):
>

I'm fine with trigger kind or trigger type but I wouldn't like to use DML
trigger.


[1] https://www.postgresql.org/message-id/1379995202.8103.4.camel@vanquo.pezone.net

ok

Regards

Pavel 



--
Euler Taveira
EDB   https://www.enterprisedb.com/

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposal to adjust typmod argument on base UDT input functions
Next
From: Octavio Alvarez
Date:
Subject: Re: Proposal to adjust typmod argument on base UDT input functions