maria-developers team mailing list archive

Thread
Date

Re: Rev 3966: MDEV-4439 ALTER TABLE .. [ADD|DROP] FOREIGN KEY IF [NOT] EXISTS does not work if constraint name is not used

To: maria-developers@xxxxxxxxxxxxxxxxxxx
From: Sergei Golubchik <serg@xxxxxxxxxxx>
Date: Sat, 1 Feb 2014 21:54:09 +0100
Cc: holyfoot@xxxxxxxxxxx
In-reply-to: <20140201125819.AD7412C4185@mail.askmonty.org>
User-agent: Mutt/1.5.22 (2013-10-16)

Hi, Holyfoot!

On Feb 01, holyfoot@xxxxxxxxxxxx wrote:
> revno: 3966
> revision-id: holyfoot@xxxxxxxxxxxx-20140201114304-7bi0ug2yg3eyyhlr
> parent: psergey@xxxxxxxxxxxx-20140121100700-9g8hl8vx8nmk1e2w
> committer: Alexey Botchkov <holyfoot@xxxxxxxxxxxx>
> branch nick: 10-hf
> timestamp: Sat 2014-02-01 15:43:04 +0400
> message:
>   MDEV-4439 ALTER TABLE .. [ADD|DROP] FOREIGN KEY IF [NOT] EXISTS does not work if constraint name is not used.
>     Patches for server and the Innodb engine.
>     Server is fixed so it does nothing if no indexes left to alter.
>     Innodb parser is fixed so it looks for the IF [NOT] EXISTS option in a string.
>     Another change is that it uses the index name for the internal dictionary.
>     Prior to that it only used the CONSTRAINT name for it.

ok to push

Regards,
Sergei