Re: plpgsql-trigger.html: Format TG_ variables as table (patch)

From: Christoph Berg <myon(at)debian(dot)org>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: plpgsql-trigger.html: Format TG_ variables as table (patch)
Date: 2022-08-31 12:33:24
Message-ID: Yw9VFHD1APjGRCec@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: To Daniel Gustafsson
> "string containing" is again pretty boilerplatish, how about just
> "contains"?

Actually, just omitting the whole prefix works best.

TG_WHEN (text)

BEFORE, AFTER, or INSTEAD OF, depending on the trigger's definition.

I also shortened some "name of table" to just "table". Since the data
type is "name", it's clear what "table" means.

Christoph

Attachment Content-Type Size
0001-plpgsql-trigger.html-Use-more-concise-wording-for-TG.patch text/x-diff 6.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2022-08-31 12:38:01 Re: SQL/JSON features for v15
Previous Message Robert Haas 2022-08-31 12:30:07 Re: replacing role-level NOINHERIT with a grant-level option