Skip to Content.
Sympa Menu

freetds - Re: conversion status

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: conversion status
  • Date: Fri, 30 Aug 2002 11:39:05 -0400


> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: August 30, 2002 1:48 AM
> Il ven, 2002-08-30 alle 06:37, James K.Lowden ha scritto:
>
> > Anyone think any of this should be in cvs?
>
> If this can be converted in an automatic test should be better.
> Why not process an input file and compare results with an
> output file?

Good idea. The code and the query need some refinement. As you did :) I
found convert_acid.c helpful in exercising convert.c.

> They are unimplemented... broken seem a fault to me...

Acknowledged, missing code isn't broken code. You understand of course I'm
not blaming anyone.

> How should we convert to binary/image?
> Should we just do a memcpy or we should swap some bytes before ??

I don't know. I don't use blobs of any kind, and I've never thought about
converting them to anything.

> Perhaps we can convert numeric -> char -> anytype. Poor
> performance but better than nothing.

That's acceptable. Sure, a X -> char -> Y conversion will be slower and
harder to understand than X->Y, but (one of my mottos is) "slow is better
than broken". The database interface is radically slower than the local
CPU. I look forward to the day when someone's major complaint about FreeTDS
is that convert.c is too slow. :) That would be a Good Problem (tm).

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