| From: | Paul Ramsey <pramsey(at)refractions(dot)net> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Cave-Ayland <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> | 
| Cc: | dblasby(at)refractions(dot)net, pgsql-hackers(at)postgresql(dot)org | 
| Subject: | PostGIS Integration | 
| Date: | 2004-02-03 20:19:56 | 
| Message-ID: | 55A45278-5686-11D8-B42D-000393D33C2E@refractions.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Actually, in my wet dream, we stored everything in system tables. 
Dimensionality and SRID became parameters of the geometry, the 
selectivity stats lived in the system stats table (as Mark's patch 
should hopefully do) and the geometry_columns view just pulled 
everything together into one user-convenient location.
CREATE TABLE foo ( mygeom POLYGON(4326) );
CREATE TABLE bar ( mygeom MULTILINESTRING(20711, 2 ) );
I think we had this discussion before though, and the "parameterized" 
types, like varchar(256), were not available for extended types, like 
our geometries.
P.
On Tuesday, February 3, 2004, at 12:06 PM, Tom Lane wrote:
> Paul Ramsey <pramsey(at)refractions(dot)net> writes:
>> Oh, now I remember. The deal was not views, it was triggers.
>
> Oh, okay.  You're right, we don't do triggers on system tables.  But
> couldn't you combine a view on the system tables with storage of
> additional data outside?
>
> 			regards, tom lane
>
      Paul Ramsey
      Refractions Research
      Email: pramsey(at)refractions(dot)net
      Phone: (250) 885-0632
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-02-03 21:25:59 | Re: Idea about better configuration options for sort | 
| Previous Message | Austin Gonyou | 2004-02-03 20:17:38 | PITR Dead horse? |