summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/ext
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2018-10-20 22:20:06 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2018-10-20 22:20:06 -0400
commitac358a04a7b077602ac668c19c3c40389d9e77e4 (patch)
tree54f42477c2cf35d1e538eae4bc39e5bb230fd462 /lib/sqlalchemy/ext
parent1963fdceae7e362f317df3621854c6276fa3fc2c (diff)
downloadsqlalchemy-ac358a04a7b077602ac668c19c3c40389d9e77e4.tar.gz
Use the same "current_timestamp" function for both sides of round trip
this test was using sysdate() and current_timestamp() together in conjunction with a truncation to DAY, however for four hours on saturday night (see commit time :) ) these two values will have a different value if one side is EDT and the other is UTC. tox does not transmit environment variables including TZ by default, so even if the server is set up for EDT, running tox will not set TZ and at least Oracle client seems to use this value, producing UTC for session time but the database on CI was configured for EDT, producing EDT for sysdate. Change-Id: I56602d2402a475a0c4fdf61c1c5fc2618c82f915
Diffstat (limited to 'lib/sqlalchemy/ext')
0 files changed, 0 insertions, 0 deletions