You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having trouble with the ctlib blk_* feature, can't get datetime2 to work. SQL Server 2019, TDS 7.4. Same problem with src/ctlib/unittests/blk_in -- if I change not_null_datetime to be a datetime2 type, it fails with server message:
Message 4895 severity 16 state 2 line 1:
"Unicode data is odd byte size for column 4. Should be even byte size."
The datetime2 type works fine with my other applications using straight ctlib interface, so perhaps it's something obscure in the blk_* routines. I've tried a number of tweaks with no success. If I change my code to use datetime type (not a viable option for my application), it works fine. Would appreciate someone taking a look.
The text was updated successfully, but these errors were encountered:
I'm having trouble with the ctlib blk_* feature, can't get datetime2 to work. SQL Server 2019, TDS 7.4. Same problem with src/ctlib/unittests/blk_in -- if I change not_null_datetime to be a datetime2 type, it fails with server message:
Message 4895 severity 16 state 2 line 1:
"Unicode data is odd byte size for column 4. Should be even byte size."
The datetime2 type works fine with my other applications using straight ctlib interface, so perhaps it's something obscure in the blk_* routines. I've tried a number of tweaks with no success. If I change my code to use datetime type (not a viable option for my application), it works fine. Would appreciate someone taking a look.
The text was updated successfully, but these errors were encountered: