Re: dbdatecrack producing erroneous results
Frediano Ziglio <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <CAHt6W4dwShgaa6K+MLzkgAAnFFLZZ=FRtdor4ZFCJKOZg0qxHQ@mail.gmail.com> |
Il 22 aprile 2012 01:58, Ken Collins <[email protected]> ha scritto: > >> When reading datetime fields of 8 byte precision from SQL server and >> parsing them using dbdatecrack the date is passed incorrectly for values >> that are outside of what normally one would use (i.e years in the >> distant future like 2300 A.D) > > Do you mean datetime2? I did not think the datetime type had a user defined precision. If you did mean datetime2, I am not sure FreeTDS supports that. FWIW, I have datetime tested to the hilt in my Ruby C extension of FreeTDS and it works like a champ with dbdatecrack() in all scenarios. > > But moot if your talking about datetime2. Again if that is the case, you may want to frame your questions and research around that. > > > - Ken > No, ms dblib does not support protocols which allow datetime2 on wire. Frediano _______________________________________________ FreeTDS mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/freetds