MySQL Bugs: #23867: Foriegn Keys fail to insert in QB for unicode tables

Bug #23867	Foriegn Keys fail to insert in QB for unicode tables
Submitted:	1 Nov 2006 23:59	Modified:	8 Jan 2007 9:07
Reporter:	Jared S (Silver Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S1 (Critical)
Version:	1.2.5 BETA	OS:	Windows (WinXP)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	foriegn keys, insert, quer browser, Unicode

Description:
Latests Query Browser will not insert Foriegn Key for unicode table.  I have marked it a S1 (critical).

How to repeat:
> create 'db1'
> create 'sale-1'
  .id 
  .idproducttype
> create 'type-1'
  .id
  .description
> create a FK for 'table-1' and link to type table
> FK will be added to DB but will not be valid or noticable by Query Browser

Suggested fix:
Ensure that when I add a FK for table called `what-ever` that Query Browser successfully apply's the change

Sample DB

Attachment: UnicdBug.sql (text/plain), 1.94 KiB.

This bug may best be suited to Marko Mäkelä.  Since he has played heavy part in unicode fixing in the past..

http://bugs.mysql.com/bug.php?id=18800

On closer inspection they keys are being added but Query Browser is not displaying them where the parent/foriegn table is unicoded i.e. `my-table`.

Thank you for the report.

Verified as described.

How long will an S1 issue like this take to get fix, since QB is my preffered database tool.

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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html