Bug #1349 | InnoDB Foreign Keys | ||
---|---|---|---|
Submitted: | 19 Sep 2003 10:26 | Modified: | 19 Sep 2003 10:53 |
Reporter: | Lívio Cerqueira | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 4.x - max | OS: | Any (All) |
Assigned to: | CPU Architecture: | Any |
[19 Sep 2003 10:26]
Lívio Cerqueira
[19 Sep 2003 10:53]
Mark Matthews
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html
[19 Sep 2003 10:53]
Mark Matthews
This is a known issue that comes about because of a change in the way InnoDB displays foreign key info that changed _after_ the release of connector/J 3.0.8. The latest nightly builds of Connector/J have the fix for this (see http://mmmysql.sourceforge.net/snapshots/stable/)