| Bug #51422 | SQLForeignKeys returns rows for FK that points to unique constraint field | ||
|---|---|---|---|
| Submitted: | 23 Feb 2010 14:16 | Modified: | 30 Jun 2010 10:19 |
| Reporter: | Lawrenty Novitsky | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Lawrenty Novitsky | CPU Architecture: | Any |
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
[25 Feb 2010 10:28]
Lawrenty Novitsky
[25 Feb 2010 10:31]
Lawrenty Novitsky
Same as "correct", but exploiting fact, that for foreign keys only(?) referenced_* fields in the KEY_COLUMN_USAGE are not NULL
Attachment: bug51422incl49660_correct_opt.patch (application/octet-stream, text), 5.79 KiB.
[25 Feb 2010 10:36]
Lawrenty Novitsky
Same as "optimized correct", but uses for identifying of primary key uses the fact that constraint name for PK is 'PRIMARY'
Attachment: bug51422incl49660_optimized.patch (application/octet-stream, text), 5.57 KiB.
