| Bug #19923 | MyODBC Foreign key retrieval broken in multiple ways | ||
|---|---|---|---|
| Submitted: | 19 May 2006 1:33 | Modified: | 10 Jan 2008 10:34 |
| Reporter: | Richard Wesley | ||
| Status: | Closed | ||
| Category: | Connector/ODBC | Severity: | S1 (Critical) |
| Version: | 3.51.12.0 | OS: | Microsoft Windows (Windows/Linux) |
| Assigned to: | Jim Winstead | Target Version: | 5.1.2 |
| Tags: | SQLForeignKeys | ||
| Triage: | D3 (Medium) | ||
If the data you need to attach is more than 500KB, you should create
a compressed archive of the data and a README file that describes the data
with a filename that includes the bug number (example:
bug-data-19923.zip), and use FTP to upload the archive
to ftp://ftp.mysql.com/pub/mysql/upload/.
Once you have uploaded the file, add a comment to this bug to notify us about
it. Note: This directory is unlistable, which means that once you
have uploaded your file, you will not be able to see it.
All entries become the exclusive editorial property of Sun Microsystems, Inc.
Implementation of SQLForeignKeys that uses INFORMATION_SCHEMA.
Attachment: bug19923.patch (text/plain), 17.69 KiB.
updated patch, still needs work
Attachment: bug19923.patch (text/plain), 17.69 KiB.
Use INFORMATION_SCHEMA for SQLForeignKeys -- needs more tests
Attachment: bug19923.diff (text/plain), 18.26 KiB.
Fixed up queries for UPDATE_RULE and DELETE_RULE with 5.1, added test
Attachment: bug19923.diff (text/plain), 20.62 KiB.
