Re: Binding a BIGINT in db-libraray

"Thompson, William" <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <55198BE54F002144AECD1A4556A1469523136A@smtp_mail.bankofamerica.com>
Freddy,

> Something like that ??

EXACTLY like that, actually.

> Perhaps to avoid some clash with proprietary libraries

That would have been a reason for caution, certainly.
It *would* be extending db-lib's capabilities beyond the existing documentation, but we've done that before where we think the extension is worthwhile. In this case it most definitely is.

Bill


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Frediano Ziglio
Sent: 19 May 2011 09:55
To: FreeTDS Development Group
Subject: Re: [freetds] Binding a BIGINT in db-libraray


2011/5/18 James K. Lowden <[email protected]>:
> On Tue, 17 May 2011 22:24:50 +0100
> "Thompson, William" <[email protected]> wrote:
>
>> I'm trying out 0.91 for the first time...
>
> Welcome back!
>
>> well to cut a long story short, my existing application code calls
>> dbbind() with a bind type of BIGINTBIND to allow  bigint data to be
>> bound to a long long variable.
>> Is this one my er...bespoke extensions to dblib ?
>
> Your patch would go well here, Bill.  Cf. _db_get_server_type().
> (Server type?  Who names these things?)
>

Something like that ??
I think I have too much patches unfinished... this is a small one!
Don't ask me why I skipped some numbers... I don't remember but there
must be a reason! Perhaps to avoid some clash with proprietary
libraries

freddy77

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.