| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Postgresql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inspection of row types in pl/pgsql and pl/sql |
| Date: | 2009-11-14 17:39:51 |
| Message-ID: | 15292.1258220391@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:
> Yes, and I have used it, but it really would be nicer to have some
> introspection facilities built in, especially for use in triggers.
Maybe, but the proposal at hand is spectacularly ugly --- in particular
it seems designed around the assumption that a given trigger will only
care about handling a predetermined set of datatypes, which hardly
fits with PG's normal goals for datatype extensibility. If the argument
is that you don't like hstore or other PLs because they'll smash
everything to text, then I think you have to do better than this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roger Leigh | 2009-11-14 17:40:24 | Re: Unicode UTF-8 table formatting for psql text output |
| Previous Message | Marko Tiikkaja | 2009-11-14 17:26:13 | Writeable CTE patch |