Hi Stefan > > It turns out if you put in an incorrect (non-existing) host, > > instead of getting an error either when you connect or when you > > open the connection, everything seems to work, but it it then all blows > > up dramatically as soon as you try execute some SQL. > > > > The same happens if you supply a username that doesn't exist, or > > even get your password wrong (ouch!). > > Okay I've done some more poking around, and the attached patch to > the OpenDBX MSSQL backend (1.4.4 tarball) fixes this for me. It's just > a one liner that adds setting tc->errtype to -1 in mssql_odbx_bind to > what it does when it can't connect. > > Now whether this is a sane or sensible fix for this, and the > real problem is SqueakDBX, or something higher up in OpenDBX > not being able to handle thing without this set and it's that that > needs fixing instead, I really couldn't tell you :)
Thank you very much for your debugging! I think your fix is correct and puts the error handling of the mssql backend in line with the other ones. Your patch was added to the SVN and will be part of the next OpenDBX release. Norbert -- OpenPGP public key http://www.linuxnetworks.de/norbert.pubkey.asc
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________ libopendbx-devel mailing list libopendbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libopendbx-devel http://www.linuxnetworks.de/doc/index.php/OpenDBX
