[postgis-devel] 1.0.5

[alex bodnaru]

hi strk,

i would rename the executable to shp2pgsql_correct, and supply a script
called shp2pgsql, to call the executable and return failure.
and advise upgrading scripts.

but sincerely, i believe no one relyied on the wrong code, so that
documenting might be enough.

alex

strk at refractions.net wrote:
> Release 1.0.5 is scheduled for tomorrow.
> CHANGES:
>         - New "Reporting Bugs" chapter in manual
>         - Segfault fix in shp2pgsql (utf8 encoding)
>         - Fixed computation of null values fraction in analyzer
>         - Fixed return code of shp2pgsql
>         - Fixed handling of trailing dots in dbf numerical attributes
>         - Schema aware postgis_proc_upgrade.pl, support for pgsql 7.2+
>         - Fixed back-compatibility issue in loader (load of null shapefiles)
>         - Fixed a small bug in the getPoint4d_p() low-level function
>         - Fixed memory alignment problems
>         - Speedup of serializer functions
>         - Bug fix in force_4d, force_3dm and force_3dz functions
> 
> The only concern I have is about shp2pgsql changing return code.
> I'm sure the new behaviour is the correct one (EXIT_SUCCESS on
> success rather then EXIT_FAILURE), still any existing script using
> the return code is going to require a change, and I can't see
> an easy way for a script to tell wheter it would be talking to
> an old or new version.
> 
> Any tip on how could we handle this ?
> An environmental variable maybe ?
> 
> --strk; 
> 
>  /"\    ASCII Ribbon Campaign
>  \ /    Respect for open standards
>   X     No HTML/RTF in email
>  / \    No M$ Word docs in email
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>