On Feb 11, 2013, at 11:19 PM, Terence J. young, DC wrote: > Hi, > > The default date format for the 64 bit version may be different than the 32 > bit.
I'll just re-iterate that this is not a 64 vs 32 bit issue, but rather a 12.x vs 15.x, or 15.0.x vs 15.7 issue. I tried the OPs issue on a 32bit version of OC 15.7, and had the same behavior. > to compensate for this, I always set the default date format in my login > subroutine. (outside of these options, I use the convert function in sybase) Which is not a bad idea. > On 2/7/13 9:53 AM, Gerardi, Mark wrote: >> Has anyone had the chance to use the 64 bit versions of DBD Sybase using >> dates/times? I'm pulling out a date from Sybase 15, with the latest version >> of ctlib, and getting weird results. >> >> By weird, I mean the date field (defined as date in the database), returns >> "Jan 4 2013 12:00am" as "Jan 4 2013". A field (defined as time in the >> database), returns "Jan 1 1900 5:00pm" as "5:00pm". In 32 bit, the dates >> return as "Jan 4 2013 12:00am" and "Jan 1 1900 5:00pm" respectively. >> This same function works fine on the 32 bit side. It does work properly if >> a "convert(char(20, date)" is used in the query, but we don't want to change >> the code if possible. Without the convert, it is just pulling the date from >> a date column is chopping off the time when it is midnight. Also, if the >> date is 1/1/1900, its only outputting the time, without the date at all. >> We've tried multiple versions of DBD, still no luck. Any suggestions? >> I’m using DBD version 1.622 btw… >> Thanks! >> Mark Gerardi | Senior Software Engineer >> > -- Michael Peppler Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html "A successful [software] tool is one that was used to do something undreamed of by its author." -- S. C. Johnson
