Bug #3798 rules for foreign keys are always reported as "no action"
Submitted: 17 May 2004 13:09 Modified: 14 Jul 2004 9:28
Reporter: Adrian Sandor Email Updates:
Status: Duplicate Impact on me:
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.07 OS:Microsoft Windows (WindowsXP)
Assigned to: Assigned Account CPU Architecture:Any

[17 May 2004 13:09] Adrian Sandor
This is related to bug 3795. This time I use a system dsn to connect to a database with InnoDB tables and foreign keys.
Using OpenSchema with adSchemaForeignKeys, I am able to get all the foreign keys from that database, but the UPDATE_RULE and DELETE_RULE fields are always "NO ACTION" although all my foreign keys use "CASCADE" for both rules.

How to repeat:
It should be clear enough from the description
[14 Jul 2004 8:53] Miguel Solorzano
Please don't open 2 bugs reports for related issue. Please add
comments in bug #3795.

[14 Jul 2004 8:57] Adrian Sandor
It is related, but it's a different bug
[14 Jul 2004 9:28] Miguel Solorzano

Yes I agree with you, but reporting related behaviors in the same bug report
the MyODBC developer will fix them at once because most probably is the
same code source.