[postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?

[Paragon Corporation]

Are we goig to be supporting 8.2.  I think that is the one main issue I have
with typemod.  I don't think that was supported until 8.3.

Then again I think the spec calls for the table to be called
ST_Geometry_Columns (not geometry_columns)
Thanks,
Regina 

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Chris
Hodgson
Sent: Friday, March 13, 2009 4:16 PM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?


> What is your concern about making these views?  Honestly, in the worst 
> case we'd have to do something like have a side-table that just 
> creates an ID for each new set of options given with the parameters 
> similar to the current tables and then have the view based on that.  
> At least for users it would still be transparent since you can tailor 
> the input/output for the typmod to be something like:
>
> mycolumn    geometry(4269,'POINT',2)
>
> or whatever.
>   
The side table seems like the only way to reliably fit all of our type
information into the 31 bits of typmod. It works as long as there are no
more than 2 billion differently-defined geometry columns, which I think is
an acceptable limitation. But where does this side-table end up living?
Isn't it just going to have the same problems as the geometry_columns table?

Chris
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel