Depends on: #2809
Date: 2011-02-24 11:57:40 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:126.96.36.199) Gecko/20110103 Fedora/3.6.13-1.fc14 Firefox/3.6.13
Date: 2011-04-28 10:10:42 +0200
interestingly current_time() is wrong too, although it differs between mclient and JDBC (the latter sets the timezone)
Even though JDBC does
The latter seems to be a bug in JDBC?
Date: 2011-05-11 15:40:27 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e04ced483138
Date: 2011-09-22 11:51:11 +0200
Created attachment 76
The attached fixes the problem. It makes that times and timestamps are reported in the client's local timezone always. The difference between having and not having WITH TIME ZONE is that the client's timezone is reported if WITH TIME ZONE is used.
However, this patch is not enough. The input should also be handled. I would expect that
Date: 2012-08-24 14:54:30 +0200
Jul2012-SP1 has been released.
Date: 2012-11-27 16:04:20 +0100
sql.mx is part of SQL, redirect bug
Date: 2012-11-28 13:45:25 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b39f2769929d
Date: 2013-08-25 14:53:16 +0200
implemented new localtime/stamp functions and made sure mclient computes time zone, without the daylight saving time correction (ie plain diff in hours).
Date: 2013-08-25 16:23:38 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0620e9df2003
Date: 2013-09-06 00:26:59 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c8ead4fbb1f6
Date: 2020-05-06 10:24:43 +0200
For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=fb1d7bb740ac
The text was updated successfully, but these errors were encountered: