mysql table reflection misdirects cross-schema foreign keys?

First noted on the list or channel.

Poked at this a bit with a 5.0 server instance and it seemed like unqualified references in SHOW CREATE TABLE output should resolve to the schema of the table. Quickly eyeballing the reflection code, it looks like it's doing the right thing. Need to verify if there's an issue here & that test coverage is in place.