[postgis] PATCH: more robust shp2pgsql -d option

[Paul Ramsey]

Just to confirm before applying this: -d drops the existing table before
making a new one. So from a global db perspective, we want to erase all
evidence of this table from the db before starting again. Is everything
which DropGeoemtryColumn() does to erase the existance of the prior
table still done with this replacement patch?

Always leery what fixed "route around" an existing problem,
Paul

Steffen Macke wrote:
> 
> I'm having problems with the DropGeometryColumn function.
> It's not working for me. The attached mini patch changes
> shp2pgsql to use "delete from geometry_colums" instead of
> DropGeometryColumn(). This fixes the shp2pgsql -d option
> for me.
> 
> Steffen
> 
> To unsubscribe from this group, send an email to:
> postgis-unsubscribe at yahoogroups.com
> 
> 
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
> 
>   ------------------------------------------------------------------------
>                               Name: shp2pgsql-drop.patch.gz
>    shp2pgsql-drop.patch.gz    Type: application/x-gzip
>                           Encoding: base64

-- 
      __
     /
     | Paul Ramsey
     | Refractions Research
     | Email: pramsey at refractions.net
     | Phone: (250) 885-0632
     \_

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Tiny Wireless Camera under $80!
Order Now! FREE VCR Commander!
Click Here - Only 1 Day Left!
http://us.click.yahoo.com/nuyOHD/7.PDAA/yigFAA/PhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
postgis-unsubscribe at yahoogroups.com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/