On 02/05/2018 13:16, Lester Caine wrote: > On 29/04/18 21:47, Adriano dos Santos Fernandes wrote: >> But standard CURRENT_TIME and CURRENT_TIMESTAMP works different than >> Firebird, as they returns the "WITH TIME ZONE" types. >> >> Tweaking CURRENT_TIME/CURRENT_TIMESTAMP for compatibility is >> problematic. > > So how do I maintain a functional system where the server has been > configured PROPERLY and is using UTC current time? Timezone is not > something that should be rammed down our throats if we are already > managing it properly with a clean timestamp and managing the display > of that data based on a client login or other local time indication. I > don't want CURRENT_TIME to be loaded with a timezone. >
As said, if you want to update server, I propose backward compatibility via LOCALTIME in old versions. If you want a stable (say, I system that should not update), don't update the server too. I think we should agree that for Firebird a expression CURRENT_TIME_AS_IN_THE_SQL_STANDARD will not be good. :) It's funny as you being one of the most interested in have timezone in Firebird not liking to do any easy work on your systems to adjust. Adriano ------------------------------------------------------------------------------ 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
