Excellent Stefan. Thank you very much/<div><br></div><div>What do you think Norbert?<div><br></div><div>Cheers</div><div><br></div><div>Mariano<br><br><div class="gmail_quote">On Fri, Nov 27, 2009 at 11:43 AM, Stefan Kapusniak <span dir="ltr"><<a href="mailto:mlist@yclept.clara.co.uk">mlist@yclept.clara.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On Tue, 24 Nov 2009 21:11:36 GMT, Stefan Kapusniak wrote:<br>
<br>
> I worked out what was going on with the MSSQL backend segfaulting<br>
> on my Vista machine<br>
<br>
> It turns out if you put in an incorrect (non-existing) host,<br>
> instead of getting an error either when you connect or when you<br>
> open the connection, everything seems to work, but it it then all blows<br>
> up dramatically as soon as you try execute some SQL.<br>
><br>
> The same happens if you supply a username that doesn't exist, or<br>
> even get your password wrong (ouch!).<br>
<br>
Okay I've done some more poking around, and the attached patch to<br>
the OpenDBX MSSQL backend (1.4.4 tarball) fixes this for me. It's just<br>
a one liner that adds setting tc->errtype to -1 in mssql_odbx_bind to<br>
what it does when it can't connect.<br>
<br>
Now whether this is a sane or sensible fix for this, and the<br>
real problem is SqueakDBX, or something higher up in OpenDBX<br>
not being able to handle thing without this set and it's that that<br>
needs fixing instead, I really couldn't tell you :)<br>
<font color="#888888"><br>
-- Stefan<br>
</font><br>_______________________________________________<br>
SqueakDBX mailing list<br>
<a href="mailto:SqueakDBX@lists.squeakfoundation.org">SqueakDBX@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx</a><br>
<br></blockquote></div><br></div></div>