[postgis-tickets] [PostGIS] #5161: Exposed GEOSLineMergeDirected

[PostGIS]

#5161: Exposed GEOSLineMergeDirected
--------------------------+---------------------------
  Reporter:  mdavis       |      Owner:  pramsey
      Type:  enhancement  |     Status:  new
  Priority:  medium       |  Milestone:  PostGIS 3.3.0
 Component:  postgis      |    Version:  3.2.x
Resolution:               |   Keywords:
--------------------------+---------------------------
Comment (by mdavis):

 Regina says:

 It won’t cause any problems if you overload it rather than add a default
 arg.



 The default arg is cleaner, since we won’t have an additional function to
 contend with.

 The main danger with adding a default arg is anybody who is using
 ST_LineMerge in views will have some upgrade issues.  Since adding a
 default arg requires dropping the old version.



 Though Sandro made some adjustments to partly resolve that.
 https://trac.osgeo.org/postgis/ticket/5033

 It renames the old function (assuming you put in the right availability
 comments) and then if there are views dependent on the old (because views
 references the oid of the function, and not the function name),  then the
 upgrade will be in an incomplete upgrade state (will just have those
 dangling old names)

 https://trac.osgeo.org/postgis/changeset/3d947448b9c939b321bc22b85c719845722ecc3d/git
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5161#comment:1>
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.