[freetds] unixODBC failing to connect.

Brian Bruns camber at ais.org
Wed Apr 16 19:06:11 EDT 2003

Only problem is i'll need to look at every name/value pair since i want to 
detect extraneous or mispelled key strings.  i'd be very nterested in 
seeing the code as it should be adaptable to the task.


On Wed, 16 Apr 2003, Lowden, James K wrote:

> > 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.
> _______________________________________________
> FreeTDS mailing list
> FreeTDS at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds

More information about the FreeTDS mailing list