[postgis-devel] [PostGIS] #1505: Deal with database dumps containing geometries with SRID > MAX_SRID

[PostGIS]

#1505: Deal with database dumps containing geometries with SRID > MAX_SRID
----------------------+-----------------------------------------------------
  Reporter:  strk     |       Owner:  pramsey      
      Type:  defect   |      Status:  closed       
  Priority:  high     |   Milestone:  PostGIS 2.0.0
 Component:  postgis  |     Version:  trunk        
Resolution:  fixed    |    Keywords:               
----------------------+-----------------------------------------------------
Changes (by strk):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Alright, as of r9145 we have the cooperative clamping in postgis_restore
 and core.
 The attached dump restores with a single non-blocking error:
 {{{
 ERROR:  check constraint "spatial_ref_sys_srid_check" is violated by some
 row
 }}}

 That error is expected and doesn't prevent all entries from being
 restored.
 This was an already implemented "feature" of disabling the check and
 attempting to recreate it later for the sake of reestablishing it or
 raising an error to the user attention.

 Actually, now that we clamp the values we do know that NO SRID > MAX_SRID
 will end up in spatial_ref_sys so could avoid that warning, except that
 the original spatial_ref_sys wants SRID to be also <= MAX_USER_SRID, which
 is before the reserved zone...

 Anyway, this ticket is completed. I would postpone cleanup (getting the
 range values in a central place, possibly at ./configure time) to after
 deciding about the actual range values.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1505#comment:22>
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.