Re: Table rewrite supporting functions for event triggers
Greg Sabino Mullane <htamfids@gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
pgsql-docs <pgsql-docs@lists.postgresql.org>
Date: 2024-09-11T14:14:27Z
Lists: pgsql-docs
On Wed, Sep 11, 2024 at 2:00 AM Michael Paquier <michael@paquier.xyz> wrote: > Putting the documentation change aside for a bit, could it be better > to redesign this function and return a text value rather than an > integer? We could directly return the names, minus "AT_REWRITE_", for > instance. > I dunno - so would we smush them together and return something like: "ALTER_PERSISTENCE and COLUMN_REWRITE" That would be a step backwards for anyone possibly using that integer programatically to (for example) give a pretty user-facing message about why the event was triggered. Cheers, Greg
Commits
-
doc: Add better description for rewrite functions in event triggers
- 93a596c73517 13.17 landed
- bca802600c7f 14.14 landed
- 14440d3b07af 15.9 landed
- a1b859c6893a 16.5 landed
- 709ce29b1656 17.1 landed
- 4b7bba49e712 18.0 landed