Hi,

Foreign keys need support in SE to fix the first item. Cascading operations don't work for triggers, but even worse, they don't work for RBR replication if a) storage engines differ on master and slave or b) the slave lacks the constraints. This is because InnoDB does cascade operations internally, because the SE interface doesn't support foreign keys, thus the cascade operations only work on the slave if the SE matches and the constraints match. This basically is a RBR/pseudo-SBR mix that simply doesn't work.

--Justin

On Sun, Jul 19, 2015 at 2:19 AM, Sergei Golubchik <serg@mariadb.org> wrote:

Hi, Ludwig!

On Jun 21, Ludwig Gramberg wrote:
> Hi,
>
> I was wondering if mariadb plans to overcome mysqls limitations such as
> - foreign key operations do not start triggers
> - triggers can’t be recursive (error 1442)

I haven't heard about any plans about these specific limitations.
That's because nobody requested that yet.

But by all means, do request these feature requests at mariadb.org/jira
and then we will certainly consider them for the next major version (and
then for the following major version if they won't made it into the
next, and so on).

> But besides additional features, is there a chance that mariadb could
> ever overcome limitations? Is this even a goal of this project?

Yes, sure. But we cannot do everything at once, so we prioritize
tasks that our users wants us to do.

Regards,
Sergei

_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp