FreeTDS Development Group

[John Seers <John.Seers AT uk.lionbioscience.com>]

James


> 
> You're welcome and please don't apologize.  The ML is here for everyone to
> use and improve FreeTDS; a mailing list without questions wouldn't
> accomplish that.

OK, I will stop apologising. It is just that I am under pressure and I
am aware that I am trying to go too fast. 

Thanks for the information and explanations on/of the handlers. I will
look up the references you have given.

I have now installed 0.53 on the more up to date Linux server and proved
that I get the same failure in ct_connect. I have also installed tcsh
(binary version) and I get a failure in ct_connect though it does not
look exactly the same. It is a bit premature to give any details as I do
not know what tcsh is yet and I will look further.


> 
> For any but trivial programs, a handler is necessary.  (That doesn't mean
> our default behavior should be a segfault, though. :/ )  Even if the
> (working) default handler's behavior is acceptable for most things, sooner
> or later you'll want to intercept some message (by number) for special
> handling.

Ok that is clear. I was thinking that perhaps I was missing some
essential functionality I should have supplied.


> 
> If you don't choose FreeTDS, how will I make my quota this month?  And what
> about my commission?
> 

Hmmmm, almost persuaded me. :)


> As we lay out in the User Guide, there really is no good alternative, IMHO.
> Of the proprietary alternatives, all lack BCP.  Some actually use FreeTDS
> under the hood.  None is faster.

Yes, I have noticed that some of the offerings look suspiciously like
FreeTDS.
(Thinks - must look up what BCP is).


> 
> John, it looks from here that the problems you've had so far have mostly
> been part of the process of learning a new library in a new environment.  

Absolutely right. I am climbing quite a steep learning curve here and I
am pushing quite hard.

> In
> such a situation, it's nice to have a reliable benchmark to help isolate
> problems.  

That was why I wrote the small C program - to learn and prove to myself
how it worked. I then hoped that it would transfer into our
development/C++ environment fairly smoothly. Sigh.


>You might want to install Sybase for Linux (free to download),
> which of course comes with Sybase's ct-lib and documentation.  It took me an
> evening to set up.  That would give you a reliable ct-lib to test against,
> so when your code fails you'd know if it's your program or FreeTDS that's
> acting up.  There are differences in the servers, but by the time they
> matter, you'll be an experienced ct-lib programmer.

Sounds a good idea. I will investigate.

Thanks.


John
begin:vcard 
n:Seers;John
tel;cell:07900 498885
tel;fax:01223 224701
tel;home:01603 660746
tel;work:01223 224729
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:John.Seers AT uk.lionbioscience.com
fn:John Seers
end:vcard