[Maria-developers] Error 1422 - Explicit or implicit commit is not allowed in stored function or trigger

Hello Alexander, I'm facing to a new issue with my stored procedures. Some of them are called directly or from trigger. When these procedures are called directly, they manage the transaction and when they are called from trigger, they doesn't manage the transaction. This works fine on Oracle,

Re: [Maria-developers] Interaction between rpl_slave_state and rpl_binlog_state

Hi All, On Tue, Nov 28, 2017 at 3:03 PM, Sachin Setiya wrote: > Hi Kristian, Andrei > > I have some question related to rpl_slave_state. Suppose A circular > async replication between A < -- > B (gtid_ignore_duplicates on) > Now, we set some temp server_id on server A

Re: [Maria-developers] Interaction between rpl_slave_state and rpl_binlog_state

Sachin Setiya writes: > I have some question related to rpl_slave_state. Suppose A circular > async replication between A < -- > B (gtid_ignore_duplicates on) Why do you set gtid_ignore_duplicates? This option is for multi-source replication:

[Maria-developers] Interaction between rpl_slave_state and rpl_binlog_state

Hi Kristian, Andrei I have some question related to rpl_slave_state. Suppose A circular async replication between A < -- > B (gtid_ignore_duplicates on) Now, we set some temp server_id on server A , lets say `X`. Now the problem is each event group which originates from A is executed 2 times. For

Re: [Maria-developers] Interaction between rpl_slave_state and rpl_binlog_state

Kristian, howdy. Thanks for a simple CHANGE MASTER ... IGNORE_SERVER_IDS that you remind us about! (This time evaded myself alone :-)) It perfectly covers a cluster circular case. What motivated me to consider this option for looking for duplicates also in gtid_binlog_pos was the following

Re: [Maria-developers] Interaction between rpl_slave_state and rpl_binlog_state

I am sure you can find some who would want something that ignores replicated GTIDs that duplicate GTIDs originating locally. I can only say that my experience is that this can cause unexpected problems, and requires a lot of thought to get a well-defined semantics that users can understand and

Re: [Maria-developers] Error 1422 - Explicit or implicit commit is not allowed in stored function or trigger

Hi Jerome, On 11/28/2017 02:33 PM, jerome brauge wrote: > Hello Alexander, > I'm facing to a new issue with my stored procedures. > Some of them are called directly or from trigger. > When these procedures are called directly, they manage the transaction and > when they are called from trigger,

[Maria-developers] MariaDB 10.2 now available on CentOS 6 &7 via SCL !!

Hello everybody, In case you missed it, I just want to share an announce of availability of MariaDB 10.2 on CentOS 6 & 7 as a Software collections. Here are the announce emails from CentOS mailing list, which contains most basic howto: