FreeTDS Development Group

[Ken Collins <ken AT metaskills.net>]

For instance, the dbprtype() just returns "char" for these columns and 
dbcolutype() just returns 0/null. It would be great if I could get TinyTDS at 
the C-level to do some extra legwork for these unsupported columns that come 
back as text. But I can not seem to find a way to get a human readable string 
to compare for the columns datatype. Thoughts?

 - Ken

> So I know this has to have been asked before, but I just wanted a 
> refresher. Does anyone think they will be needing or working on supporting 
> these data types [date], [datetime2], [datetimeoffset], and [time] using 
> DBLIB? Right now they come back to me as SYBTEXT and I was considering 
> coping with them at that level in my own way for the time being, which 
> seems OK. I think I can parse out what I need from the string.
> 
> Quick question on that. In my codes case for SYBTEXT, I'd like to find the 
> columns datatype as a string. Is there a way in DBLIB to get that?
> 
> - Ken