[postgis-devel] postgis_restore; and geometry_columns is now a view

[Bryce L Nordgren]

Ah, I see. Should the postgis_upgrade script go away then, since it won't
upgrade to 2.0?

Thanks,
Bryce

On Fri, Sep 9, 2011 at 12:55 AM, Paragon Corporation <lr at pcorp.us> wrote:

> **
> I wrote up these instructions for upgrading.  Works for the couple of
> databases I have upgraded to 2.0
>
>
> http://www.postgis.org/documentation/manual-svn/postgis_installation.html#hard_upgrade
>
> Regina
>
>  ------------------------------
> *From:* postgis-devel-bounces at postgis.refractions.net [mailto:
> postgis-devel-bounces at postgis.refractions.net] *On Behalf Of *Bryce L
> Nordgren
> *Sent:* Thursday, September 08, 2011 6:24 PM
> *To:* PostGIS Development Discussion
> *Subject:* [postgis-devel] postgis_restore; and geometry_columns is now a
> view
>
> Ok,
>
> so I notice that the new postgis.sql (on trunk) will create a
> geometry_columns view.
>
> But postgis_restore will try to
>
> DROP TABLE geometry_columns;
>
> Won't work because it's a view now. Also, the script is setup to replace
> the geometry_columns from postgis.sql with the geometry_columns from the
> dumpfile. Meaning the "dumpfile.ascii" tries to create a geometry_columns
> table (won't work because a view with the same name already exists.)
>
> I've uncommented lines 545-546, hoping to git rid of geometry_columns from
> the "dumpfile.ascii" file.
>
> Is this a real problem or am I just making things difficult where they
> shouldn't be? Does postgis_restore need to get smarter before the release?
>
> Bryce
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20110909/b44045d0/attachment.html>