Re: dbcoltype char vs. datetimeoffset
Chris Kings-Lynne <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <bca69e4303d34c6383bc8f20516c8b74@HKXPR02MB007.apcprd02.prod.outlook.com> |
I'm sure I'm connecting with 8.0 - would this work if I were? Chris -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of James K. Lowden Sent: Monday, 23 September 2013 12:11 PM To: [email protected] Subject: Re: [freetds] dbcoltype char vs. datetimeoffset On Mon, 23 Sep 2013 02:58:44 +0000 Chris Kings-Lynne <[email protected]> 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. --jkl _______________________________________________ FreeTDS mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/freetds -- 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: https://login.mailguard.com.au/report/1I1Z6dKNJV/4izNNeqIVYlx9v2DGlT29B/0