28.02.2018 16:42, Leyne, Sean wrote:
Based on this, and considering legacy FB applications I propose the following:
1- The only acceptable string format for the new Date/Time with Timezone
datatypes should be the ISO/SQL standard
2- Only legacy DATE and TIMESTAMP datatype would maintain support for the
legacy date formats.
Does Firebird parser have a problem with rule '<timezoned value> := <leagcy
timestamp><space><timezone>'?
I can't remember example of timezone that would make parsing conflict between time part
of timestamp and time zone string.
--
WBR, SD.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
