| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Paul Ramsey <pramsey(at)refractions(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Bruce David <brucedavid(at)bigfoot(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Trigger on 'create table' ? |
| Date: | 2002-10-29 22:33:07 |
| Message-ID: | 24250.1035930787@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Paul Ramsey <pramsey(at)refractions(dot)net> writes:
> We have a similar requirement for PostGIS.
> In order to meet the OpenGIS specification, we have to maintain a
> GEOMETRY_COLUMNS table which includes an entry for every column in the
> db which holds a spatial column. It would be ideal if we could have
> triggers run on CREATE TABLE, DROP TABLE, and ALTER TABLE to watch for
> the comings and goings of spatial columns and update GEOMETRY_COLUMNS
> appropriately.
Couldn't you define GEOMETRY_COLUMNS as a view? Seems a lot more
efficient than firing random triggers on every table operation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Bierman | 2002-10-29 22:38:40 | CVS TOT fails to build on MacOSX 10.2.1 |
| Previous Message | Tom Lane | 2002-10-29 22:21:27 | Re: float output precision questions |