MySQL Bugs: #28885: Foreign Keys Dropped

Bug #28885	Foreign Keys Dropped
Submitted:	4 Jun 2007 20:32	Modified:	5 Jun 2007 14:25
Reporter:	Mr Wakazula	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.12	OS:	Windows (XP Pro SP2)
Assigned to:		CPU Architecture:	Any

Description:
Good afternoon,

I have spent the day cleaning up a project's schema.  During this process, I have noticed that foreign keys are being dropped.

BACKGROUND
- I can guarantee that I am the only user accessing the database server
- This problem has happened at least 3 times over the past 8 hours
- As far as I can tell, not all keys are being dropped
- Database Server:
   > MySql 5.0.41 community-nt TCP/IP
- My PC:
   > Windows Xp Pro SP2
   > MySql Client 1.2.12

How to repeat:
Unfortunately, I have yet to figure out the sequence of steps required to reproduce the problem.

As best as I can tell...

1) Open Query Browser
2) Right click `Edit Table` (assume we are working on TableA)
3) Add a foreign key
4) Click `Apply Changes`
...
5) Go and do something else (drop tables, rename fields, add more FKs)
...
6) Right click `Edit Table` on `TableA`
7) One or more foreign keys may have been dropped

Suggested fix:
I recognize that this does not help to isolate the problem.  Hopefully someone else will be able to provide additional insight.

Thank you for the bug report. I was not able to repeat the behavior reported,
could you please describe step by step a sample case to reproduce that
behavior. Thanks in advance.

Hi Miguel.

As previously mentioned, I have yet to determine the exact steps required to reproduce the problem.  

I fully understand that with the information provided taht there is little you can do. My hope is that others may be able to provide additional information when they see this ticket.

Thank you for the feedback. Please be free to re-open this bug report when
you are able to provide the sample test case or any else can do. Thanks
in advance.

This may be related to Bug #38710