Skip to Content.
Sympa Menu

freetds - RE: money wire format

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: money wire format
  • Date: Thu, 8 Aug 2002 09:38:20 -0400


> From: Thompson, Bill D (London) [mailto:ThompBil AT exchange.uk.ml.com]
> Sent: August 8, 2002 2:18 AM
>
> On little endian the two bytes would be:
>
> 0 0 0 0 1 0 0 0
>
> which, if you were to cast the data to an 8 byte integer
> would NOT make
> sense (well it would , but the number would be wrong). The
> number 1 , on a
> little endian machine in an 8 byte integer would presumably be:
>
> 1 0 0 0 0 0 0 0
>
> HTH, How did you get on ?

Bill,

As my father used to say, we're cooking with gas.

I basically stole the pre-August 2 code and adpated it to tds_convert_money.
Once I understood the problem and realized we had had working code at one
time, it was just a matter of fitting the old logic into your new signature.
I spent more time researching the problem than fixing it.

The clue was that both you and Brian said TDS_MONEY is two 32-bit integers
(not one 64-bit one).

I left your code in place (#ifdef'ed out) in case you want to endianize your
version instead, or in case mine is good for one situation and yours for
another. Let me know if you want to fix it; otherwise and some point I'll
remove it.

What do you see as still TODO for 0.60?

Regards,

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page