Elena Stepanova added a comment - 2013-12-02 19:39 - edited Hi, Sorry for the delay. What you observe is actually a documented behavior, although not quite obvious. Here is what happens here: when you create table b1, you define FOREIGN KEY on b1.a_id. Since the column doesn't have an index, it's created automatically, as described here: http://dev.mysql.com/doc/refman/5.5/en/create-table-foreign-keys.html <quote> In the referencing table, there must be an index where the foreign key columns are listed as the first columns in the same order. Such an index is created on the referencing table automatically if it does not exist. </quote> If you run SHOW CREATE TABLE b1, you'll see the index on the column. So, when you later create c1, it works all right since there is an index. when you create b2, you define the constraint "inline". It does not work at all, as described here: http://dev.mysql.com/doc/refman/5.5/en/create-table.html <quote> MySQL does not recognize or support “inline REFERENCES specifications” (as defined in the SQL standard) where the references are defined as part of the column specification. MySQL accepts REFERENCES clauses only when specified as part of a separate FOREIGN KEY specification. </quote> If you run SHOW CREATE TABLE b2, you'll see there is no FK constraint on the table. Since the clause is ignored, the index is not created automatically, as it happened with b1, so when you later create c2, it complains and refuses to work. One thing that might be considered a documentation bug here is the vague wording in the second quote. It says that the inline references are not "recognized" or "accepted", while in fact they don't cause a syntax error, but are just ignored. If you wish, you could suggest a better wording to MySQL documentation team at bugs.mysql.com. Please comment if you have further concerns on the topic.