Engine-independent foreign keys would be really useful. MariaDB has a lot of nice storage engines, and improving the interaction between them is simply great.
I am currently work on a project where it is necessary to enforce consistency between Maria and SQL Server in every point in time. If we had the ability to build a FK from InnoDB to CONNECT, I would have an easy solution for this problem.
Regards
Federico
--------------------------------------------
Dom 19/7/15, Sergei Golubchik
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. Right. My first idea was to add some kind of a callback for a storage engine to inform the server about cascading operation. Then it could fire a trigger. We already can fire triggers for low-level row operations, this is used in our "RBR triggers" feature: https://mariadb.com/kb/en/mariadb/running-triggers-on-the-slave-for-row-base... 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