[freetds] dbcoltype char vs. datetimeoffset

Chris Kings-Lynne Chris.Kings-Lynne at navitas.com
Mon Sep 23 02:51:55 EDT 2013

I'm sure I'm connecting with 8.0 - would this work if I were?


-----Original Message-----
From: freetds-bounces at lists.ibiblio.org [mailto:freetds-bounces at lists.ibiblio.org] On Behalf Of James K. Lowden
Sent: Monday, 23 September 2013 12:11 PM
To: freetds at lists.ibiblio.org
Subject: Re: [freetds] dbcoltype char vs. datetimeoffset

On Mon, 23 Sep 2013 02:58:44 +0000
Chris Kings-Lynne <Chris.Kings-Lynne at navitas.com> wrote:

> The dbcoltype() function returns code 47 for both varchar and 
> datetimeoffset fields...is there any way to distinguish these - as 
> they really are _rather_ different...

Less different than you might think, I'm afraid.  

If you connect to a server that supports datetimeoffset with TDS 7.2, you're using a protocol for which no datetimeoffset datatype is defined.  On your behalf, the server provides the data as a string, which you see as VARCHAR.  That's what's known as backwards compatibility.  

There are good reasons to update db-lib to support the new datatypes, which after all are not so new anymore.  What is lacking someone with time and interest.  

FreeTDS mailing list
FreeTDS at lists.ibiblio.org
Message  protected by MailGuard: e-mail anti-virus, anti-spam and content filtering.http://www.mailguard.com.au/mg
Click here to report this message as spam:

More information about the FreeTDS mailing list