[postgis-tickets] [PostGIS] #3453: PostGIS JDBC Driver extension inconsistencies

[PostGIS]

#3453: PostGIS JDBC Driver extension inconsistencies
---------------------+--------------------------
 Reporter:  manaeem  |      Owner:  bergun
     Type:  defect   |     Status:  new
 Priority:  medium   |  Milestone:  PostGIS Java
Component:  java     |    Version:  2.1.x
 Keywords:           |
---------------------+--------------------------
 While using postgis-2.1.8.tar.gz PostGIS JDBC extension with PG9.5
 following anomalies are observed i.e.

 1. Version.getFullVersion() method returning wrong version i.e.
 {{{
 PostGIS JDBC V2.0.0
 }}}

     It seems that related version information require to be updated i.e.
     java/jdbc/src/org/postgis/version.properties
 {{{
       REL_MAJOR_VERSION=2
       REL_MINOR_VERSION=0
       REL_MICRO_VERSION=0
 }}}

 2. Test case java/jdbc/src/examples/TestParser.java fail with two type of
 errors i.e.
     A). There are # of failure because of "can not mix dimensionality in a
 geometry", It seems a test case bug.
 {{{
 2016-02-05 11:19:54 PKT ERROR:  can not mix dimensionality in a geometry
 2016-02-05 11:19:54 PKT HINT:  "...IONM(POINT(10 10 20),POINT(20 20 20))"
 <-- parse error at position 52 within geometry
 2016-02-05 11:19:54 PKT STATEMENT:  SELECT
 geometry_in('GEOMETRYCOLLECTIONM(POINT(10 10 20),POINT(20 20 20))')
 }}}

         Test case output snippet i.e.
 {{{
 Testing on connection 0: postgres
 --- Server side error: org.postgresql.util.PSQLException: ERROR: can not
 mix dimensionality in a geometry
   Hint: "...ONM(POINT(10 10 20),POINT(20 20 20))" <-- parse error at
 position 53 within geometry
 SQLout  :  GEOMETRYCOLLECTIONM(POINTM(10 10 20),POINTM(20 20 20))
 Eq SQLout: yes
 Prepared:  GEOMETRYCOLLECTIONM(POINTM(10 10 20),POINTM(20 20 20))
 Eq Prep: yes
 --- Server side error: org.postgresql.util.PSQLException: ERROR: can not
 mix dimensionality in a geometry
   Hint: "...ONM(POINT(10 10 20),POINT(20 20 20))" <-- parse error at
 position 53 within geometry
 --- Server side error: org.postgresql.util.PSQLException: ERROR: can not
 mix dimensionality in a geometry
   Hint: "...ONM(POINT(10 10 20),POINT(20 20 20))" <-- parse error at
 position 53 within geometry
 hexNWKT:   GEOMETRYCOLLECTIONM(POINTM(10 10 20),POINTM(20 20 20))
 equal    : yes
 hexXWKT:   GEOMETRYCOLLECTIONM(POINTM(10 10 20),POINTM(20 20 20))
 equal    : yes
 NWKT:      GEOMETRYCOLLECTIONM(POINTM(10 10 20),POINTM(20 20 20))
 equal    : yes
 XWKT:      GEOMETRYCOLLECTIONM(POINTM(10 10 20),POINTM(20 20 20))
 equal    : yes

 }}}

         You can observe that test case is using POINT instead of POINTM
 for some cases that is troubling PostGIS.

     B). Second set of errors are failing with following errors i.e.
 {{{
 2016-02-05 11:19:55 PKT ERROR:  parse error - invalid geometry
 2016-02-05 11:19:55 PKT HINT:  "GEOMETRYCOLLECTION(EMPTY" <-- parse error
 at position 24 within geometry
 2016-02-05 11:19:55 PKT STATEMENT:  SELECT
 geometry_in('GEOMETRYCOLLECTION(EMPTY)')
 }}}
         It looks like a bug to me that result in query like "SELECT
 geometry_in('GEOMETRYCOLLECTION(EMPTY)')" instead of "SELECT
 geometry_in('GEOMETRYCOLLECTION EMPTY')" i.e. new representation.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3453>
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.