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:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Lawrenty Novitsky	CPU Architecture:	Any

File:	Maximum allowed size is 50MB.
Description:
Privacy:

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

Patch that uses in query "correct" ways of identifying foreign and primary keys

Attachment: bug51422incl49660_correct.patch (application/octet-stream, text), 5.45 KiB.

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.

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.

Page generated in 0.037 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.