Skip to Content.
Sympa Menu

freetds - Re: [freetds] freebcp file limit

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Robert Klemme <shortcutter AT googlemail.com>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] freebcp file limit
  • Date: Tue, 6 Dec 2005 21:43:00 +0100

2005/12/6, Frediano Ziglio <freddyz77 AT tin.it>:

> > How true. That reminds me that I always wanted to ask about freetds
> > version number policy. When can we expect to see 1.0 (or even
> > higher)? On one hand I have the feeling that 0.63 is pretty much
> > stable (at least the bulk loader which is the only one we extensively
> > tested so far) on the other hand 0.63 seems to indicate quite a gap to
> > 1.0 which irritates me a bit...

> Good question Robert... I start following this project some years ago
> (changelog say on 2002) and there was 0.53 version. I remember that we
> introduced a lot of changes so someone (Brian perhaps) decide to release
> a 0.60 version (skipping some versions). After that we just follow a
> simple increment role... 0.61, 0.62, 0.63 and 0.64.
>
> I think that the confusion raise from not using separate versions for
> stable and development. For instance we are developing the future 0.64
> version and we call cvs head version ad 0.64...
>
> So your question is: "Will a "1.0" version be available?"
> Mine is: "How care?" :-)

It depends. I am just trying to find out. :-)

> Current 0.63 version support a lot of feature and 0.64 support even
> more. From my point of view (that is mainly ODBC) there are only a big
> TODO: cursors... query, results, all types, dynamic sql, RPC are already
> there we support a lot of systems and a lot of applications.

Ok, then it's not 1.x because some major features are still missing.

> About bulk operations... I have to say that Bill made a good work but I
> feel (and I hope that is only a feeling) that this field is not very
> tested... If you could get the point where program segfaults (after
> updating to 0.63 of course!) it would be very helpful.

I'll happily submit any segfaults - if they occur. (Haven't seen any yet.)

Kind regards

robert




Archive powered by MHonArc 2.6.24.

Top of Page