[fdo-trac] #104: PostGIS provider cannot insert features with geometry

[FDO]

#104: PostGIS provider cannot insert features with geometry
------------------------------+---------------------------------------------
 Reporter:  cwilbur           |         Owner:  mloskot 
     Type:  defect            |        Status:  assigned
 Priority:  major             |     Milestone:  3.3.0   
Component:  PostGIS Provider  |       Version:  3.2.0   
 Severity:  3                 |    Resolution:          
 Keywords:                    |   External_id:          
------------------------------+---------------------------------------------
Changes (by mloskot):

  * status:  new => assigned

Comment:

 I'm going to review and test these patches but I'm a bit confused.
 Are all these 3 patches to be applied or only two patches starting with
 ExprProc* should be considered?

 There are some reasons why EWKB is used and transfered as HEX encoded
 stream.
 First, we intentionally do not use binary cursor so we do not exchange raw
 binary data. It would be even better to use Base64.

 EWKB is used because it supports extended dimensions of coordinates used
 in FDO, but WKB does not support it.

 Also, generally, it's recommended to work in text mode than in binary,
 because in the latter case we would need to deal with endianness issue.
 The PostgreSQL server accepts only big-endian binary, regardless of arch
 of machine the server is running on. This issue is not handled
 automatically by client library libpq.

 Current strategy was discussed with Paul and Jason and the implementation
 follows the compromise we found.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/104#comment:10>
FDO <http://fdo.osgeo.org/>
Feature Data Objects