Changes between Initial Version and Version 1 of Ticket #4660


Ignore:
Timestamp:
Jul 20, 2020, 9:14:25 AM (4 years ago)
Author:
Algunenano
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4660

    • Property Status assigned → new
    • Property Summary Raise the max number of digits for double printing to 17 → Sensible number output semantics

  • Ticket #4660 – Description

    initial v1  
    1 In #4543 I enforced a limit on the number of digits output by lwprint_double. This limit was already in place but not always effective, which could lead to issues in other functions not calculating the necessary buffer correctly, so they would overestimate to be safe.
     1~~In #4543 I enforced a limit on the number of digits output by lwprint_double. This limit was already in place but not always effective, which could lead to issues in other functions not calculating the necessary buffer correctly, so they would overestimate to be safe.~~
    22
    3 I set it to 15 digits, but it has come to my attention that some double numbers need up to 17 digits to be able to do the correct round trip, so I'm thinking on raising it from 15 to 17.
     3~~I set it to 15 digits, but it has come to my attention that some double numbers need up to 17 digits to be able to do the correct round trip, so I'm thinking on raising it from 15 to 17.~~
    44
    5 It should be available for both ST_AsText and ST_AsGeoJSON, but the user setting (or default) is still in place (so if they request 8 digits they should get 8 and no more).
     5~~It should be available for both ST_AsText and ST_AsGeoJSON, but the user setting (or default) is still in place (so if they request 8 digits they should get 8 and no more).~~
     6
     7Comes from 2 different mail threads:
     8* https://lists.osgeo.org/pipermail/postgis-devel/2020-April/028510.html
     9* https://lists.osgeo.org/pipermail/postgis-devel/2020-April/028528.html