Thanks Regina, Robe and Paul as usual you answer fast and giving us a
lot of information.
I will be checking out the ticket to know the status of this bug.
To know it is working with geography type let me get rid of some fear
about if it was a PostgreSQL issue.
As Regina said we can use still c
Jose,
slight omission in my last
> -- to put back constraints on it --
> SELECT populate_geometry_columns('a'::regclass);
>
I forgot that use type mod is the default now -- so the above should be
SELECT populate_geometry_columns('a'::regclass, false);
To force it to constrain the geometry us
I figure out where to put that.
Hope that helps,
Regina
http://www.postgis.us
> -Original Message-
> From: postgis-users-boun...@postgis.refractions.net
> [mailto:postgis-users-boun...@postgis.refractions.net] On
> Behalf Of Jose Carlos Martinez
> Sent: Tuesday, Novemb
Hi all,
Im using PostgreSQL 9.1 and PG 2.0 under MS Windows.
Lets say I have a tabla A with a geometry column 'geom' of type
geometry(MultiPolygon, 23030).
then I wrote a trigger (BEFORE INSERT ON, FOR EACH ROW) that changes:
New.geom:= ST_GeometryN (New.geom, 1).
After inserting a row:
inser
