Bug #3795 foreign keys are not returned if using a file dsn
Submitted: 17 May 2004 10:38 Modified: 29 May 2013 13:29
Reporter: Adrian Sandor Email Updates:
Status: Closed Impact on me:
Category:Connector / ODBC Severity:S2 (Serious)
Version:3.51.07 OS:Microsoft Windows (Windows XP)
Assigned to: CPU Architecture:Any

[17 May 2004 10:38] Adrian Sandor
I use ADO and the OpenSchema function of the Connection object, with the adSchemaForeignKeys (=27) query type, on a database that has InnoDB tables with foreign keys. If I use a file dsn then the returned recordset is empty. If I use a system dsn, I get the keys correctly.
This bug is probably related to bug 3780 (also reported by me).

How to repeat:
Use a file dsn to connect to a database with InnoDB tables with foreign keys and connect to it using ADO,
then use the following code (javascript asp here):

var rst=cnn.OpenSchema(27);

It will display False with a file dsn and True with a system dsn.
[20 Sep 2007 12:44] Miguel Solorzano
Could you please try the latest released version 3.51.20. Thanks in
[20 Oct 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[21 Oct 2007 7:41] Adrian Sandor
Oh, you want some feedback? Well, here's some feedback then:
Once upon a time, a very very long time ago, I reported a lot of bugs in the MySQL ODBC driver, which was so catastrophically full of critical bugs that it was 99.999% unusable and should have never been released. And for more than 3 years, nobody really did anything about it (how's *THAT* for no feedback?), with the exception of somebody called Tonci, who really tried, but was unsuccessful eventually.
I don't think you could possibly imagine I've been waiting all this time for these bugs to be fixed. Obviously, I moved on. So the only feedback I can give now is that I don't really give a damn anymore.
All the bugs I reported already have enough information to reproduce them or verify fixes. So whoever is interested can use that information to give feedback.
[29 May 2013 13:29] Bogdan Degtyariov
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at