| Bug #34511 | errorno.150 | ||
|---|---|---|---|
| Submitted: | 13 Feb 2008 1:48 | Modified: | 19 Jan 2009 8:17 |
| Reporter: | JESSA AYO | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | CPU Architecture: | Any | |
[13 Feb 2008 1:48]
JESSA AYO
[13 Feb 2008 5:15]
Valeriy Kravchuk
Please, send the exact CREATE TABLE statement you use. Error 150 is: MySQL error code 150: Foreign key constraint is incorrectly formed So, looks like this is not about bug in MySQL, but likely about some incorrect syntax you use.
[14 Mar 2008 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[19 Mar 2008 16:33]
Susanne Ebrecht
We still need to know if we can close this bug report because it was just a syntax error.
[19 Apr 2008 23:01]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[18 Jan 2009 15:01]
Giorgi Alkhazishvili
I have the same situation. There was not syntax error. In my case I was trying to create connect foreign key by connecting the fields with different data types. After correcting data types every thing work fine
[19 Jan 2009 8:17]
Valeriy Kravchuk
So, looks like in all cases reported so far the reason was user's mistake, not a bug in MySQL's code.
