Unfortunately, we have been reduced to "manually" maintaining this table through the mechanism of the "AddGeometryColumn" "DropGeometryColumn" functions. As you noted, we had some old scruft in there dating back to the pre-DROP COLUMN days. That's gone in the current version.
In an idea world though, we would construct the thing as a view, so that when you did a CREATE TABLE that included a geometry type, you would automatically get a row in geometry_columns. That requires a view on system tables though, and that just does not work. :/
Any thoughts on a nice implementation?
Paul
On Tuesday, January 20, 2004, at 09:07 AM, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:So, if we replace that with: ALTER TABLE table_name ALTER column_name DROP NOT NULL; ? should be good to go? still not as clean as doing the straight DROP COLUMN, but its a fast fix ...
Yeah, that's what I'd do until the PostGIS guys can rethink things at a higher level.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Paul Ramsey Refractions Research Email: [EMAIL PROTECTED] Phone: (250) 885-0632
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])