Skip to Content.
Sympa Menu

freetds - RE: [freetds] unixODBC failing to connect.

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] unixODBC failing to connect.
  • Date: Wed, 16 Apr 2003 11:55:25 -0400

> From: Brian Bruns [mailto:camber AT ais.org]
> Sent: April 16, 2003 6:02 AM
>
> I think that this just goes to prove that we desperately need
> a program to
> test the freetds.conf for validity. This is my next freetds related
> task.

I wrote an "ini file" parsing library with C and C++ interfaces. I call it
"nvp" for "name value pair." The only reason I haven't posted it on SF yet
is I haven't written the docs. Been busy, you know.

You point it at a file, it parses it and loads it into memory, returning a
handle. You pass it a handle and a section name, it returns a section
handle. You pass it a section handle and a name, it returns a value. Case
sensitive, so far.

My idea is to use nvp in FreeTDS, thereby giving the freetds.conf values a
freestanding representation that could be established before connecting.

As things are, TDSCONNECTINFO is populated as part of the connection
process, making it impossible to examine the server's characteristics before
attempting the connection. You can't print a message saying, "I'm about to
connect to the server you call S, known as machine M at address A on port P
using TDS version V, trying a domain login, dumping to log file L ... here
goes".

Happy to send you a tarball if you like.

--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.





Archive powered by MHonArc 2.6.24.

Top of Page