[postgis-devel] [PostGIS] #1802: Ensure interruptability of long-running calls

[PostGIS]

#1802: Ensure interruptability of long-running calls
---------------------+------------------------------------------------------
 Reporter:  strk     |       Owner:  strk         
     Type:  task     |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.0.1
Component:  postgis  |     Version:  2.0.x        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by strk):

 If I read the message from 2005 correctly your change removed an SQL entry
 point (transform_geom). SQL is our API so it was really a problem of
 backward compatibility.
 There's no backward compatibility problem in this case. The SQL interface
 doesn't change.
 There is _no_ API change.

 The only point I see as valid is the testing one.
 What about putting the code in but conditionally enable it with a compile
 time define ?
 Would give people the opportunity to test within the framework of the 2.0
 branch w/out them being forced to do so (it will be off by deafult).

 PS: I agree about shorter release cycles

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