| 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, David Blasby <dblasby(at)refractions(dot)net> |
| Subject: | Re: Trigger on 'create table' ? |
| Date: | 2002-10-30 17:42:25 |
| Message-ID: | 29720.1035999745@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:
> Now, if we changed the geometry type so that when one defined a geometry
> column, one had to include info about what SRID and what dimension it
> was, (ala varchar(243)) maybe the whole schmeer could reside in pg_class
> and geometry_columns would be a trivial view?
atttypmod would be a natural place for that stuff, if you can fit it
into 31 bits. The bigger problem is how are you going to get
type-specific syntax through the Postgres parser? Currently, all the
types that use typmod have to have special-purpose syntax to set it.
I'm not eager to see extension datatypes trying to do the same thing...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-30 17:53:32 | Re: 7.3b3 on MacOSX 10.2.1 |
| Previous Message | Pedro Miguel Frazao Fernandes Ferreira | 2002-10-30 17:01:19 | Re: float output precision questions |