| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Postgresql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inspection of row types in pl/pgsql and pl/sql |
| Date: | 2009-11-14 19:27:37 |
| Message-ID: | 17110.1258226857@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> Perhaps it would help if we looked at some specific use-cases that
>> people need, rather than debating abstractly. What do you need your
>> generic trigger to *do*?
> The two things I have wanted most badly in the past are
> a) to be able to address a field in NEW and OLD by a string name
> (usually passed in via a trigger argument) and
But what are you then going to do with that field? Are you just
assuming that it will be of a pre-agreed datatype? Or that you
can perform some specific operation on it? What are you expecting
will happen if it isn't or can't?
> b) to be able to discover the names if the fields in NEW and OLD
It doesn't seem hard or ugly to provide an API for that, but again
I'm wondering what happens next.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-11-14 19:28:56 | patch - per-tablespace random_page_cost/seq_page_cost |
| Previous Message | Jeff Davis | 2009-11-14 19:27:29 | Re: operator exclusion constraints |