datetime: raise error for ambiguous, nyi timezones
Use different return values for indication that recognized timezone suffix is ambiguous or not yet handled (before tzdata integration to come in next patchset). i.e. we could always parse '2020-02-02T01:03 MSK' as MSK is static +03:00, but it's ambiguous if there is something like '2020-02-02T01:03 AT' as there are multiple ATs (e.g. 'Alaska Time' and 'Atlantic Time'). NO_CHANGELOG=internal NO_DOC=internal
Showing
- src/lib/core/datetime.c 8 additions, 7 deletionssrc/lib/core/datetime.c
- src/lib/core/datetime.h 2 additions, 1 deletionsrc/lib/core/datetime.h
- src/lib/tzcode/strptime.c 1 addition, 2 deletionssrc/lib/tzcode/strptime.c
- src/lib/tzcode/timezone.c 21 additions, 5 deletionssrc/lib/tzcode/timezone.c
- src/lib/tzcode/timezone.h 24 additions, 2 deletionssrc/lib/tzcode/timezone.h
- src/lua/datetime.lua 18 additions, 4 deletionssrc/lua/datetime.lua
- src/lua/tnt_datetime.c 1 addition, 1 deletionsrc/lua/tnt_datetime.c
- test/app-tap/datetime.test.lua 39 additions, 1 deletiontest/app-tap/datetime.test.lua
Loading
Please register or sign in to comment