Bulk insert problem with SQL Server datetime2 type

[jboia]

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.

[freddy77]

Apparently the function supposed to convert data to server format is not doing the right thing in this case.
Seeing if it's easy to fix.

[jboia]

I noticed you made some recent changes over several commits, but also removed some of those changes. When I have a chance, I will try some tests and see if datetime2 works better. Thanks.

[freddy77]

The patch from Aaaron was better so I replaced mine.
With the right protocol version datetime2 columns are imported correctly.
Unfortunately not with older protocol (the ones not supporting datetime2).