|
|
sybperl-l Archive
Up Prev Next
From: michael dot peppler at bnpparibas dot com
Subject: Re: unsigned datatype causing ct_fetch(): overflow?
Date: Oct 16 2006 6:31AM
I was able to reproduce the problem. I'll have to dig a little bit, but it
the problem should be localized to the describe() function in dbdimp.c in
case you want to give it a shot.
Michael
Internet
h4w301@gmail.com@peppler.org - 15.10.2006 14:40
Sent by: owner-sybperl-l@peppler.org
To: sybperl-l
cc:
Subject: unsigned datatype causing ct_fetch(): overflow?
Hi,
I'm using ASE Express 15 and DBD-Sybase 1.07.
Is it true that DBD-Sybase 1.07 can not accept unsigned datatype from ASE
15?
I create a simple table:
create table asdf (
num unsigned smallint
)
insert into asdf values (32768)
When I fetch the table, it gave me error message:
Message String: ct_fetch(): user api layer: internal common library
error: The bind of result set item 1 resulted in an overflow.
Its OK when I insert 32767 (max of signed smallint).
Regards,
Humphrey
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
|
