DBD::Sybase is now two years old. Perhaps it was never tested on 64 bit Systems?

(Update: According to the CHANGES file, DBD::Sybase runs on several 64 bit systems.)

From the symptoms, it looks like the DBD::Sybase code, when compiled for 64 bit, assumes a wrong size and leaves a part of a buffer untouched (zeroed).

I think you should post your question on the DBI-Users mailing list. Include a link to your thread here.

Alexander

Here are the versions we are using: DBD::Sybase is 1.115 (10/2/2011), DBI is version 1.622, ctlib: Sybase Client-Library/15.5/P-EBF18235 ESD #7/DRV.15.5.1/Linux x86_64/Linux 2.6.9-55.ELsmp x86_64/BUILD1550-009/64bit/OPT/Fri Aug 27 01:52:15 2010

If so, what do you mean by "weird" results?

Michael

Yes, the make test did work properly. 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.

Is this with the exact same version of OpenClient, with just the 32/64 bit difference?

Because the 64bit data you get is more correct - and is also what I get with a 32bit 15.7 client:

use strict;

use DBI;

my $dbh = DBI->connect('dbi:Sybase:server=foo', 'user, '***');
my $sth = $dbh->prepare("select convert(date, getdate()), convert(time
+, getdate())");
$sth->execute;

while(my $r = $sth->fetch) {
  print "@$r\n";
}
[download]

which outputs:

$ perl /tmp/date.pl
Feb  7 2013  3:06PM
[download]

And to me that's as it should be - you're asking for just the date, so no time portion is displayed, or just the time, and no date portion is displayed.

This is with DBD::Sybase 1.14, btw.

Michael