* dlenev@stripped <dlenev@stripped> [08/04/18 23:29]:
> ChangeSet@stripped, 2008-04-18 23:00:57+04:00, dlenev@stripped +7 -0
> Fix for for bug #35524 "Foreign keys: constraint name can be incorrect".
>
> In --foreign-key-all-engines mode one was able to create foreign key
> constraints with empty name or name ending with space.
>
> This happened because we used check_identified_name() function instead
> of check_table_name() for checking of constraint names. The latter does
> all checks done by the former but also covers case with empty name and
> name ending with space. This fix simply uses correct function for
> checking of constraint names.
OK to push.
--
Konstantin Osipov Moscow, Russia
MySQL Server Runtime Team Lead Database Group, Sun Microsystems