[postgis-devel] SVN trunk parser modifications stage 2

[Obe, Regina]

David,
> One problem with all of the function-overloading ideas, is that if you 
> backup your geometries using pg_dump (COPY or INSERT mode), you won't 
> necessarily be able to reimport them.  (Without using INSERT mode and 
> writing an ugly script to wrap geometry fields in the loose parsing 
> function.)

I don't quite understand this argument above.  Presumably copy and insert
would be using the 

CAST(...) syntax implicitly or just doing  memory copy so how would overloading 
these functions cause problems?  The current ones would just not do any checking which is desired since even if your data is no good, I presume you still
want to bring it in and deal with it inside the db.

Thanks,
Regina


-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20081027/a115752a/attachment.html>