Status: Open (View Workflow)
Affects Version/s: 10.4.1, 10.4.12, 10.5, 10.5.3
Environment:OS: Windows 10, CentOS 6, CentOS 7, Ubuntu 18.04 , Windows 2012
ODBC Connector 3.0 & 3.1.7
We were upgrading to 10.4.12 recently and found an year 2038 issue in the integration tests.
This is a regression from 10.4.0 which is known good.
First, let me state that I already bisected the commit that introduced the changed behaviour which is:
Probably the best to look at this would be @"Alexander Barkov"
I changed a MSDN example to do the following
Steps to reproduce:
This is working (log_direct.trace is the corresponding dbuglog):
This is will set NULL for timestamps affected by the year 2038 issue ( log_prepared.trace is the corresponding dbug log)
(pseudocode, the complete code will be in the reproducer):
If you want to use the reproducer program, it can be compiled with
cl /EHsc /DEBUG:FULL /DUNICODE /D_UNICODE user32.lib odbc32.lib /link /SUBSYSTEM:CONSOLE replicate.cpp
and run with
replicate.exe "DSN=DebugMDB; Uid=root; Pwd="
I wanted to write a test but could not reproduce this with prepared SQL statments like so: