Skip to Content.
Sympa Menu

freetds - Re: [freetds] dbcoltype char vs. datetimeoffset

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Frediano Ziglio <freddy77 AT gmail.com>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] dbcoltype char vs. datetimeoffset
  • Date: Mon, 23 Sep 2013 09:52:01 +0100

2013/9/23 Chris Kings-Lynne <Chris.Kings-Lynne AT navitas.com>:
> Ah. I see that version 8.0 and 7.2 are mapped to 7.2 in PHP dblib. I
> imagine that's due to the MS vs. Sybase version naming confusion?
>

No, it's MS against MS version confusion, they changed numbering. To
not having server use varchar you have to use version 7.3 (supported
only by git versions).

> So basically I have to fix FreeTDS to recognise the new type...any hints on
> where to start?
>

Well... dblib itself does not support these types (and probably never
will) so we have to extend it on FreeTDS.

> Chris
>

Frediano

> -----Original Message-----
> From: freetds-bounces AT lists.ibiblio.org
> [mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Chris Kings-Lynne
> Sent: Monday, 23 September 2013 2:52 PM
> To: FreeTDS Development Group
> Subject: Re: [freetds] dbcoltype char vs. datetimeoffset
>
> I'm sure I'm connecting with 8.0 - would this work if I were?
>
> Chris
>
> -----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.
>
> --jkl
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> 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
>
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds




Archive powered by MHonArc 2.6.24.

Top of Page