The issue was in the handling of multi-column foreign key constraints
where one of the columns was an integer primary key.  The error has
always been in the code.  It was simply masked by the prior error
of ticket The fix in
check-in is correct.  That
fix did not introduce a new problem; it merely brought an existing
problem into view.

The Severity of this ticket is downgraded to Important since one
can easily argue that any schema that has a multi-column
foreign key constraint where one of the columns is a primary key
is a broken schema.  Even so, we ought to handle even broken
schemas correctly, which should be the case after check-in