- The column order checks are correct already but the error message returned differ
  comapred to the legacy engine.
 - Change the error message to be same as legacy engine.
- Note that ndbcluster allow creating foregin keys referencing unique indexes
  in parent table with different column order than the child table. This is ok
  as long as the unique index covers all columns wherea there will only be one
  or zero rows regardless of column order.
 - Add test showing that legacy and ndb have the same error code when non matching
  parent are found