[prev in list] [next in list] [prev in thread] [next in thread]
List: postgis-users
Subject: Re: [postgis-users] adding columns to the geometry_columns table
From: Phil James <borntopedal () yahoo ! co ! uk>
Date: 2011-07-25 14:33:34
Message-ID: 1311604414.54559.YahooMailNeo () web25803 ! mail ! ukl ! yahoo ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I think this i because the constraints from the existing table (geom type and srid) \
are not copied over with the data. You need to recreate these (copy them from the \
CREATE TABLE sql from the "old" table). probe_geometry_columns() will then do what \
it is supposed to do.
Phil
> ________________________________
> From: Jan Hartmann <j.l.h.hartmann@uva.nl>
> To: postgis-users@postgis.refractions.net
> Sent: Monday, 25 July 2011, 9:51
> Subject: [postgis-users] adding columns to the geometry_columns table
>
>
> Hi,
>
> When I create a table "like" another table with geometry columns,
the the public.geometry_columns table is not updated. The
"probe_geometry_columns()" and "populate_geometry_columns"
functions don't work on the new table, because they cannot
determine the srid of the geometry column in the new, empty table.
Is there another way to update the geometry_columns table?
Alternatively, would it make sense to add a "srid"-parameter to
"probe_geometry_columns()" and "populate_geometry_columns()"?
>
> Jan
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
>
[Attachment #5 (text/html)]
<html><body><div style="color:#000; background-color:#fff; font-family:arial, \
helvetica, sans-serif;font-size:12pt"><div>I think this i because the constraints \
from the existing table (geom type and srid) are not copied over with the data. \
You need to recreate these (copy them from the CREATE TABLE sql from the "old" \
table). probe_geometry_columns() will then do what it is supposed to \
do.</div><div><br></div><div>Phil</div><div><br><blockquote style="border-left: 2px \
solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-size: \
12pt; font-family: arial, helvetica, sans-serif; "><div style="font-size: 12pt; \
font-family: 'times new roman', 'new york', times, serif; "><font size="2" \
face="Arial"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Jan \
Hartmann <j.l.h.hartmann@uva.nl><br><b><span style="font-weight: \
bold;">To:</span></b> postgis-users@postgis.refractions.net<br><b><span \
style="font-weight: bold;">Sent:</span></b> Monday, 25 July 2011, 9:51<br><b><span \
style="font-weight: bold;">Subject:</span></b> [postgis-users] adding columns to the \
geometry_columns table<br></font><br><div id="yiv1307427099">
<font face="Times New Roman, Times, serif">Hi,<br>
<br>
When I create a table "like" another table with geometry columns,
the the public.geometry_columns table is not updated. The
"probe_geometry_columns()" and "populate_geometry_columns"
functions don't work on the new table, because they cannot
determine the srid of the geometry column in the new, empty table.
Is there another way to update the geometry_columns table?
Alternatively, would it make sense to add a "srid"-parameter to
"probe_geometry_columns()" and "populate_geometry_columns()"?<br>
<br>
Jan <br>
</font>
</div><br>_______________________________________________<br>postgis-users mailing \
list<br><a ymailto="mailto:postgis-users@postgis.refractions.net" \
href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br><a \
href="http://postgis.refractions.net/mailman/listinfo/postgis-users" \
target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br><br><br></div></div></blockquote></div></div></body></html>
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic