[postgis-devel] Re: [PostGIS] #151: rt_ prefixes brake WKT Raster seemless integration

[PostGIS]

#151: rt_ prefixes brake WKT Raster seemless integration
------------------------+---------------------------------------------------
  Reporter:  pracine    |       Owner:  pracine        
      Type:  defect     |      Status:  closed         
  Priority:  medium     |   Milestone:  wktraster 0.1.6
 Component:  wktraster  |     Version:                 
Resolution:  fixed      |    Keywords:                 
------------------------+---------------------------------------------------
Comment (by robe):

 Guys I just realized a possibly small problem with using ST_ prefix.
 While writing book and complaining about why relying on autocasts is bad
 and you should explictly use ST_GeomFromText or CAST or what have you.  It
 occurred to me that the downside of using ST_ for Raster, is that you can
 never declare a Text auto cast for it.

 Auto casts I think are bad anyway.  The point though --

 In Postgis -- you can do this ST_Intersects('POINT(....)',
 'LINESTRING(...)');

 and PostgreSQL will happily cast both to geometry because there is an auto
 cast in place.

 However if you introduced an auto cast that takes WKT Raster text
 representation  --> RASTER -- it will break everything.

 So I guess the point is if you plan to create CASTS that convert text to
 RASTER -- make sure they are not declared automatic -- otherwise it would
 cause an ambiguous function name error thingy.

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