freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Brian Bruns <camber AT ais.org>
- To: "'freetds AT lists.ibiblio.org'" <freetds AT lists.ibiblio.org>
- Subject: RE: [freetds] Preparing 0.61
- Date: Wed, 29 Jan 2003 16:00:30 -0500 (EST)
Yeah, I saw the problem. I believe it happens with a true-blue Sybase 4.2
dblib-based isql too, but have been unable to dredge one up to test it ;-)
Anyway, it's a flat out server bug, possibly fixed in the latest EBF's but
again I haven't had the time to look recently. 12.5 GA and the first EBF
(sorry don't have the number handy) had the problem.
Brian
BTW, someone forwarded me a note the other day, and I don't know if you
guys have seen this, but Sybase apparently is using FreeTDS for its plugin
to REALBasic on the Mac, which I personally find fascinating.
On Wed, 29 Jan 2003, Lowden, James K wrote:
> > From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafoneomnitel.it]
> > Sent: January 29, 2003 11:22 AM
> > >
> > > I updated several files in preparation for 0.61rc1. The
> > > version number
> > > and .so numbers have been bumped, the text files updated to reflect
> > > changes since the last release. I consider this ready,
> >
> > Only one thing.. what's the problem with Sybase 12.5,
> > described in README ??
>
> AFAIK, the problem Brian (?) discovered with Sybase 12.5 and TDS 4.2 hasn't
> been addressed. Our TDS 4.2 implementation crashes a Sybase 12.5 server.
> The warning was taken from the README-0.60 that was included in that
> release. I figured we need only one README, so I included the warning in
> it.
>
> One of these days, I'm going to rewrite tds_send_login(). It should be
> handed a structure of TDS_X_LOGIN (where X is the version) to write out to
> the server. As written, it's very hard to tell what's being sent, because
> the data are pulled from a variety of sources and written on the fly,
> complete with #if's for endianism and branches for the TDS version.
>
> Perhaps if we made what we're doing more plain, Sybase could tell us what to
> differently.
>
> We should add this to Known Issues in the UG.
>
> --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 we do not accept account orders and/or
> instructions by e-mail, and therefore will not be responsible for carrying
> out such orders and/or instructions.
>
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
-
[freetds] Preparing 0.61,
James K. Lowden, 01/29/2003
- <Possible follow-up(s)>
- RE: [freetds] Preparing 0.61, Thompson, Bill D (London), 01/29/2003
- RE: [freetds] Preparing 0.61, Lowden, James K, 01/29/2003
- RE: [freetds] Preparing 0.61, Thompson, Bill D (London), 01/29/2003
- RE: [freetds] Preparing 0.61, ZIGLIO Frediano, 01/29/2003
-
RE: [freetds] Preparing 0.61,
Lowden, James K, 01/29/2003
-
RE: [freetds] Preparing 0.61,
Brian Bruns, 01/29/2003
- RE: [freetds] Preparing 0.61, Michael Peppler, 01/29/2003
- RE: [freetds] Preparing 0.61, Mark J. Lilback, 01/29/2003
-
RE: [freetds] Preparing 0.61,
Brian Bruns, 01/29/2003
Archive powered by MHonArc 2.6.24.