[postgis-tickets] [PostGIS] #2209: [raster]: String of 388800145 bytes is too long for encoding conversion

[PostGIS]

#2209: [raster]:  String of 388800145 bytes is too long for encoding conversion
--------------------+-------------------------------------------------------
 Reporter:  robe    |       Owner:  dustymugs    
     Type:  defect  |      Status:  new          
 Priority:  medium  |   Milestone:  PostGIS 2.1.0
Component:  raster  |     Version:  trunk        
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by robe):

 Oh I see what you are saying I was assuming we could just say we are
 outputting UTF8 as part of the generated raster2pgsql.  Except we have no
 place to denote encoding in raster2pgsql anyway and not sure what that
 would mean for binary data why it even needs to pass thru an encoder.

 I suppose people might have filenames that require encoding care or if we
 start reading meta data from fiels we could encounter weird characters
 taht require encoding care.  Huh I don't even want to think about this.

 I'll just document in the FAQ. In theory you don't have to do anything
 until you get the error.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2209#comment:3>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.