26.11.2018 16:18, Leyne, Sean wrote:
What about external tools which might use this field for their own purposes???
These tools will be broken by proposed changes as isc_database_info() will start
returning different data type or different value.
Summarizing whole discussion, there are several options named:
1) Leave the field as is and put local time w/o TZ into it. Full backward
compatibility.
2) Leave the field as is and put UTC into it. Less compatible but consistent with changes
to CURRENT_TIMESTAMP.
3) Expand field to include TZ. No backward compatibility at all. Every external tool that
reads the creation TS value via API or whole database header directly will be broken.
4) Add TZ info into variable part of header (and choose option 1 or 2 for the value).
Compatibility depends on choice.
If there was democracy here, I would vote for 2.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
