MySQL Bugs: #35000: Cascade 'unsigned' attribute on foreign keys

Bug #35000	Cascade 'unsigned' attribute on foreign keys
Submitted:	3 Mar 2008 13:48	Modified:	5 Mar 2008 17:32
Reporter:	moi meme	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.0.11b	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	foreign key, refresh, UNSIGNED

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
If you set a foreign key linked with an int, and that you make the original key as unsigned, foreign key will be incoherent (since it will stay signed).

How to repeat:
create a table with an int key.
create another table with this int key as foreign key.
change in the first table the int status to 'unsigned'.
export the create script and execute...

Suggested fix:
refresh foreign key when original one is modified.

Thank you for a reasonable feature request.

Duplicate of feature request #32907