[postgis-tickets] [PostGIS] #4483: Can't upgrade from PostGIS 3.0.0alpha3 to 3.0.0alpha4 ST_AsGeoJSON

[PostGIS]

#4483: Can't upgrade from PostGIS 3.0.0alpha3 to 3.0.0alpha4 ST_AsGeoJSON
----------------------+---------------------------
  Reporter:  robe     |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  blocker  |  Milestone:  PostGIS 3.0.0
 Component:  postgis  |    Version:  trunk
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by pramsey):

 "tag", "release", we bundled out a release with this change already in
 place, so if A was old and B was new, and A>B is broken, we can't really
 fix it, right? B is broken and it's released. Also, changing back for C
 would imply B>C would also be broken. But at least then C>D, D>E, etc
 would all work.

 We can change back, the only thing that "pretty_bool" is good for is
 matching up to the json emitting functions in PostgreSQL which use
 "pretty_bool" as the name for their pretty printing variable. I noticed
 while adding the casts and decided to try to match them up and then we
 ended up here (because why PostgreSQL cares so much about variable names
 that you cannot change them in signatures? seems overly tight to me)

 I still don't know what to do to fix this. I don't even know what test
 you're running. If you're upgrading from the broken release to trunk that
 won't work, right?

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4483#comment:6>
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.