| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Table rewrite supporting functions for event triggers |
| Date: | 2024-09-11 14:14:27 |
| Message-ID: | CAKAnmmJ-DXh4QDjS8Aiz8SBxDWrcj1Epq54byb8T_035nTX2JQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Sep 11, 2024 at 2:00 AM Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2024-09-11 20:12:19 | Elaborate on phrase "table metadata" in the Notes section of ALTER by specifying pg_attribute |
| Previous Message | David G. Johnston | 2024-09-11 11:32:06 | Re: Mathematical Functions and Operators |