| Bug #19923 | MyODBC Foreign key retrieval broken in multiple ways | ||
|---|---|---|---|
| Submitted: | 18 May 2006 23:33 | Modified: | 10 Jan 2008 9:34 |
| Reporter: | Richard Wesley | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S1 (Critical) |
| Version: | 3.51.12.0 | OS: | Windows (Windows/Linux) |
| Assigned to: | Jim Winstead | CPU Architecture: | Any |
| Tags: | SQLForeignKeys | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[22 May 2006 10:54]
Tonci Grgin
[18 May 2007 23:53]
Jim Winstead
Implementation of SQLForeignKeys that uses INFORMATION_SCHEMA.
Attachment: bug19923.patch (text/plain), 17.69 KiB.
[30 Jul 2007 21:13]
Jim Winstead
updated patch, still needs work
Attachment: bug19923.patch (text/plain), 17.69 KiB.
[20 Dec 2007 20:45]
Jim Winstead
Use INFORMATION_SCHEMA for SQLForeignKeys -- needs more tests
Attachment: bug19923.diff (text/plain), 18.26 KiB.
[20 Dec 2007 22:53]
Jim Winstead
Fixed up queries for UPDATE_RULE and DELETE_RULE with 5.1, added test
Attachment: bug19923.diff (text/plain), 20.62 KiB.
