I recently upgraded MySQL and decided to watch its error log to see if there were any problems. I notice a bunch of warnings regarding the writing to JomSocial tables as shown below. Since these are programming issues there is nothing I can do on my end. Should I be concerned? Thanks. -- Rik

PS: Using JomSocial 4.2.5 and Joomla 3.6.2.

161013 14:25:04 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE `member` FROM `jos_community_events_members` member INNER JOIN `jos_community_events` event ON member.`eventid` = event.`id` WHERE member.`status`= '0' AND event.`enddate` < '2016-10-13 19:25:04'
161013 14:25:04 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE `featured`.* FROM `jos_community_featured` AS `featured` INNER JOIN `jos_community_events` AS `events` ON `events`.`id` = `featured`.`cid` WHERE `featured`.`type` = 'events' AND `events`.`enddate` < CURDATE()
161013 14:30:01 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE `member` FROM `jos_community_events_members` member INNER JOIN `jos_community_events` event ON member.`eventid` = event.`id` WHERE member.`status`= '0' AND event.`enddate` < '2016-10-13 19:30:01'
161013 14:30:01 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE `featured`.* FROM `jos_community_featured` AS `featured` INNER JOIN `jos_community_events` AS `events` ON `events`.`id` = `featured`.`cid` WHERE `featured`.`type` = 'events' AND `events`.`enddate` < CURDATE()
161013 14:35:01 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE `member` FROM `jos_community_events_members` member INNER JOIN `jos_community_events` event ON member.`eventid` = event.`id` WHERE member.`status`= '0' AND event.`enddate` < '2016-10-13 19:35:01'
161013 14:35:01 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE `featured`.* FROM `jos_community_featured` AS `featured` INNER JOIN `jos_community_events` AS `events` ON `events`.`id` = `featured`.`cid` WHERE `featured`.`type` = 'events' AND `events`.`enddate` < CURDATE()

Hi Rik

Thank you for reporting, this is not important issue, just warning, but indeed we need to take care this.

Regards!

Anyway, What mysql version are you using?

Dimas:

Dimas wrote: Anyway, What mysql version are you using?