[postgis-devel] [PostGIS] #252: Text autocasting behavior of geography is breaking geometry functionality

[PostGIS]

#252: Text autocasting behavior of geography is breaking geometry functionality
----------------------+-----------------------------------------------------
  Reporter:  robe     |       Owner:  pramsey      
      Type:  defect   |      Status:  new          
  Priority:  medium   |   Milestone:  postgis 1.5.0
 Component:  postgis  |     Version:  trunk        
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Comment (by kneufeld):

 Confusing signals?  I thought we were all on the same page.  Paul
 mentioned that he has many breaking changes that he'll introduce in 2.0.
 So to handle this issue and avoid a breaking change in 1.5, we'll add the
 overloaded functions that accept textual arguments (which still complies
 with the new release policy).  Then, when 2.0 rolls out, we can remove the
 unnecessary functions, enforcing explicit typecasting, following the lead
 of PostgreSQL.

 I was merely pointing out that we would need to overload every function
 that shares a common prototype as geometry, not just st_asbinary.

 So geography introduced at least one breaking change that looks like can
 be dealt with easy enough.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/252#comment:9>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS