The reason I don't want to use a GEOMETRY type is because the rest of my application stack is built to work with Shapefile-style homogeneous geometry fields. The alteration of the constraint, with Ralf suggested, works fine for my purposes. It's not particularly interoperable, but that is fine for me right now. I guess it is actually equivalent to creating the field with a GEOMETRY type, and then simply altering the geometry_columns table so that it is 'POLYGON', or whatever the case may be.
Ben On Thu, Jul 2, 2009 at 4:21 PM, Ben Madin<[email protected]> wrote: > Could you not just use a Geometry type? > > cheers > > Ben > > > On 02/07/2009, at 5:47 PM, Ben Harper wrote: > >> I am looking for a way of creating a geometry field that has a >> constrained type identical to the Shapefile spec. >> Basically, Polygons and MultiPolygons are equals. Linestrings and >> Multilinestrings are equals. >> Is there a way to accomplish this with PostGIS? >> If I make the field Polygon, then I can't insert Multipolygons, and vice >> versa. >> >> Thanks, >> Ben >> _______________________________________________ >> postgis-users mailing list >> [email protected] >> http://postgis.refractions.net/mailman/listinfo/postgis-users > > -- > > Ben Madin > REMOTE INFORMATION > > t : +61 8 9192 5455 > f : +61 8 9192 5535 > m : 0448 887 220 > Broome WA 6725 > > [email protected] > > > > Out here, it pays to > know... > > > _______________________________________________ > postgis-users mailing list > [email protected] > http://postgis.refractions.net/mailman/listinfo/postgis-users > _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
