On 12/12/17 15:20, Alex Peshkoff via Firebird-devel wrote: >> Oracle also mentions inconsistency that may happen when the time zone >> database is updated. If user had previously entered a time in a moment >> that subsequently has updated by the time zone db, it may become >> inconsistent. So it should be updated manually. > > May be also add a new type of trigger that will be invoked under such > circumstances? In some cases such time may be corrected automatically > according to business logic of data, stored in database.
The new mechanism for distributing TZ data ... tzdist ... has the potential to trigger events when a particular rule has been changed, but there is a lack of any management of just what set of rules are being used when publishing a calendar. While the current tzdb data does have a version number, the whole database has to be updated when in reality only one or two rules may have changed. The VERSION of TZ data that was used to normalize the UTC timestamps is just as important as the location of the event. The two go hand in hand ... and it's the version data that is missing in the Oracle 'solution' ... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk ------------------------------------------------------------------------------ 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
