Odd Behavior with Null Dates: Feature or Bug?

[Jamie Jackson]

A couple of strange things happen with null date columns in transfer
(latest BER, rev 645). See attached example (columnB).

1. They are returned as January 1, in the year 100.
2. They are returned as coldfusion.runtime.OleDateTime, whereas other
dates seem to be returned as Strings

Is this the way it's supposed to work? If so, why?

MSSQL 2005:
columnA
value in db: 1999-02-02 00:00:00.0
transfer-returned value: 1999-02-02 00:00:00.0
class: class java.lang.String
columnB (nullable)
value in db: NULL
transfer-returned value: {ts '0100-01-01 00:00:00'}
class: class coldfusion.runtime.OleDateTime
columnC (nullable)
value in db: 2012-12-12 00:00:00.0
transfer-returned value: 2012-12-12 00:00:00.0
class: class java.lang.String

Thanks,
Jamie

[Jamie Jackson]

Small, probably trivial, correction: DB's MSSQL 2000 and not 2005.

[Jamie Jackson]

I still think the behavior is weird, but I'm finding my answers in
http://groups.google.com/group/transfer-dev/browse_thread/thread/7b55d3bcf66985ec/6ae6d3681b9d0164?lnk=gst&q=null+date#6ae6d3681b9d0164