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

[Markus Schaber]

Hi, Mark,

Mark Cave-Ayland <mark.cave-ayland at siriusit.co.uk> wrote:

> Paul Ramsey wrote:
> > We should think pretty hard before doing this. As Tom noted, this is
> > not much different than just moving AddGeometryColumns into the CREATE
> > TABLE statement, in terms of information required. We also have the
> > problem of what to DO with geometry that is defined WITHOUT these
> > options. If I don't miss by guess, geometry created with a CREATE
> > TABLE AS SELECT... will be in this category, for example.
> 
> I think this part will be okay. At least, if you do a CREATE TABLE AS 
> SELECT on a table with a field of varchar(255) then your new table 
> should also contain a field of varchar(255).

But when you do operations like string concatentation, or intersections
etc, the result type may require different typemods.



Regards,
Markus

-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org