freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "James K. Lowden" <jklowden AT schemamania.org>
- To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] Sybase Incompatibilities?
- Date: Wed, 16 Jul 2003 18:28:58 -0400
On Wed, 16 Jul 2003 10:40:13 -0400, "Ben Vaughn"
<bvaughn AT BlackbirdTech.com> wrote:
> Yeah, this version of ASA requires the database name and servername to
> match, or it will NOT allow a connection. With tinkering I found that
> the database name sent to the server is the name you specify in the
> interfaces/freetds.conf files,
That's right, I remember now. It's also a footnote in the freetds.conf
section of the UG. That much is documented.
http://www.freetds.org/userguide/x631.htm#FTN.AEN643
> while the server name is part of the "app
> name" specification of the sybase_connect() function of PHP. I don't
> think such an option exists for SQSH/TSQL, but perhaps it would be
> beneficial to include it?
Maybe. I just spent a little while looking for where we pick up the
servername and send it to the server (as app_name or the database name).
I didn't find it. I would be nice to rid FreeTDS of this particular quirk
if we can.
--jkl
-
[freetds] Sybase Incompatibilities?,
Ben Vaughn, 07/15/2003
- Re: [freetds] Sybase Incompatibilities?, James K. Lowden, 07/15/2003
- <Possible follow-up(s)>
-
RE: [freetds] Sybase Incompatibilities?,
Ben Vaughn, 07/16/2003
- [freetds] how to : connection pool with ASE12.5 and freetds 0.61, nvodka, 07/16/2003
-
Re: [freetds] Sybase Incompatibilities?,
James K. Lowden, 07/16/2003
- Re: [freetds] Sybase Incompatibilities?, L J Bayuk, 07/16/2003
-
RE: [freetds] Sybase Incompatibilities?,
Ben Vaughn, 07/16/2003
- Re: [freetds] Sybase Incompatibilities?, James K. Lowden, 07/16/2003
- RE: [freetds] Sybase Incompatibilities?, Ben Vaughn, 07/17/2003
- RE: [freetds] Sybase Incompatibilities?, Lowden, James K, 07/17/2003
- RE: [freetds] Sybase Incompatibilities?, Ben Vaughn, 07/17/2003
Archive powered by MHonArc 2.6.24.