[postgis-devel] Re: [postgis-users] create tables smarter

[Mark Cave-Ayland]

Markus Schaber wrote:

>> I don't see this as being particularly difficult to implement...  If
>> there's agreement on this approach then I'd be happy to write the C code
>> necessary.  Is there a preference on the structure of the typmod values,
>> or is Frank's suggestion of:
>>
>> GEOMETRY(<dimension>,<srid>,<type>)
>>
>> acceptable? 
> 
> I think this is acceptable, feel free to go ahead and present
> patches. :-)


Hi Markus,

Welcome back from holiday! ;)

I must admit that I find GEOMETRY(<dimension>,<srid>,<type>) fairly 
unintuitive; I'd prefer GEOMETRY(<type>,<dimension>,<srid>) as an 
alternative. Also, when we determine the maximum size of the SRID field, 
we can easily add a CHECK constraint on the table to return an ERROR if 
someone tries to go above the limit.

Given the massive re-working of the codebase (see 
http://postgis.refractions.net/pipermail/postgis-devel/2008-May/003010.html 
and 
http://postgis.refractions.net/pipermail/postgis-users/2008-May/019886.html 
for a catch-up) I'm happy to work on this in SVN trunk when we decide on 
the final layout. The hardest bit will be trying to keep the maintenance 
of both the new code for 8.3+ and the existing code relatively sane.


ATB,

Mark.

-- 
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063