13.01.2017 16:46, Tim Ward t...@telensa.com [firebird-support] wrote:
> One thing I've now noticed is that running the trigger by updating a
> record via isql gives the correct, Brazilian, answer.
If you are running isql and connected to database in embedded mode, your
current
environment is
On 13/01/2017 14:04, Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] wrote:
> 13.01.2017 13:09, Tim Ward t...@telensa.com [firebird-support] wrote:
>> I just don't believe this. Can anyone make any other suggestion as to
>> what is going on?
> Is timezone on your Linux set globally or
13.01.2017 13:09, Tim Ward t...@telensa.com [firebird-support] wrote:
> I just don't believe this. Can anyone make any other suggestion as to
> what is going on?
Is timezone on your Linux set globally or for each current user environment
independently?
--
WBR, SD.
-
However what I'm actually seeing is as follows.
(1) Set a Linux machine to "Brazil/East". Check this using the "date"
command line command.
(2) Confirm that
select CURRENT_TIMESTAMP from rdb$database
does report the Brazilian local time as expected.
(3) Next, I've got a table with a TIMESTAMP
On 12/01/2017 14:09, Tim Ward wrote:
> Sorry if this is a really basic question, but some time spent
> searching has failed to find for me the definitive detailed
> documentation on exactly how Firebird handles time zones (I'm
> particularly interested, to start with, in using CURRENT_TIMESTAMP
