FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

SQL Server 7.0 GA and SP1 had broken date handling from big endian
machines....A patch was applied to work around it. Unfortunately it is
fixed in SP2, but there is no way to tell the difference between them.
So if you look in convert.c you'll see a section of code that looks like:

if (major_ver==7) {
        tds->broken_dates=1;
}

just comment that out and recompile and you should be set.  However it
should be noted that you will now have broken date handling on SQL 7
servers < SP2.

Cheers,

Brian

On Thu, 1 Feb 2001, ZULU wrote:

> hi
> 
> On our developmentmachine we are using linux - there all SQL statements
> work fine. Our client machine is an
> SunOS  5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-4 this is the only
> known difference.
> The porblems occures in all date related SQL funtions, I dont know if
> Insert statements work fine but the select statements equal on rows or on
> integrated functions like getdate or Current_timestamp produce no valid
> days.
> 
> Datetime fields returns always Feb 07 2036 06:30A.
> Getdate and Current_timestamp return an date between 1900 and 2036 -
> growing all time to the maximum and starts again
> 
> Hm
> Hope somebody finds an answer.
> 
> mfg Gerald Urbas
>