UPDATES EasyBlog 6.0.14 Released! Joomla 5.x and PHP 8.x compatible now!

Helpdesk

Your Time
Our Time
Response Time
24 — 48 hours
We strive to provide the fastest ever response possible. However, we are not super beings.

Allow at least 24 — 48 hours
  Support is offline
Our team is away during the weekend. Some answers may already be available on our documentation

Rest assured that we will get back to your posts as soon as the week starts!
  Support is offline

EasySocial Database Warnings

Neel · ·
8:50 PM Friday, 07 November 2014
None
I am getting the following MySQL Warnings in my server log file where some of them are relating to EasySocial tables:


141107 13:48:24 [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 from `joom_social_profiles_maps` where not exists ( select `id` from `joom_social_profiles` where `profile_id` = `id` )


141107 14:04:38 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO `joom_finder_terms` (`term`, `stem`, `common`, `phrase`, `weight`, `soundex`, `language`) SELECT ta.term, ta.stem, ta.common, ta.phrase, ta.term_weight, SOUNDEX(ta.term), ta.language FROM `joom_finder_tokens_aggregate` AS ta WHERE ta.term_id = 0 GROUP BY ta.term


141107 14:04:38 [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: UPDATE `joom_finder_terms` AS t
INNER JOIN `joom_finder_tokens_aggregate` AS ta ON ta.term_id = t.term_id
SET t.`links` = t.links + 1


141107 14:10:53 [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: INSERT IGNORE INTO `joom_finder_terms` (`term`, `stem`, `common`, `phrase`, `weight`, `soundex`, `language`) SELECT ta.term, ta.stem, ta.common, ta.phrase, ta.term_weight, SOUNDEX(ta.term), ta.language FROM `joom_finder_tokens_aggregate` AS ta WHERE ta.term_id = 0 GROUP BY ta.term


141107 16:25:58 [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: INSERT INTO `joom_social_privacy_items` (`privacy_id`, `user_id`, `uid`, `type`, `value`) SELECT `d`.`id` AS `privacy_id`, '946' AS `user_id`, `a`.`id` AS `uid`, `d`.`type`, `d`.`value` FROM `joom_social_fields` AS `a` LEFT JOIN `joom_social_fields_steps` AS `b` ON `b`.`id` = `a`.`step_id` LEFT JOIN `joom_social_apps` AS `c` ON `c`.`id` = `a`.`app_id` LEFT JOIN `joom_social_privacy` AS `d` ON `d`.`rule` = `c`.`element` WHERE `d`.`type` = 'field' AND `b`.`type` = 'profiles' AND `b`.`uid` = '1' AND `a`.`id` NOT IN (SELECT `e`.`uid` FROM `joom_social_privacy_items` AS `e` WHERE `e`.`type` = 'field' AND `e`.`user_id` = '946')


141107 16:25:58 [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: INSERT INTO `joom_social_privacy_map` (`privacy_id`, `uid`, `utype`, `value`) SELECT `a`.`id` AS `privacy_id`, '946' AS `uid`, 'user' AS `utype`, `a`.`value` FROM `joom_social_privacy` AS `a` WHERE `a`.`type` = 'field' AND `a`.`id` NOT IN (SELECT `b`.`privacy_id` FROM `joom_social_privacy_map` AS `b` WHERE `b`.`uid` = '946' AND `b`.`utype` = 'user')


141107 16:28:34 [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: INSERT IGNORE INTO `joom_finder_terms` (`term`, `stem`, `common`, `phrase`, `weight`, `soundex`, `language`) SELECT ta.term, ta.stem, ta.common, ta.phrase, ta.term_weight, SOUNDEX(ta.term), ta.language FROM `joom_finder_tokens_aggregate` AS ta WHERE ta.term_id = 0 GROUP BY ta.term


141107 16:46:20 [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: UPDATE joom_menu SET template_style_id = 0 WHERE template_style_id in ( SELECT s.id FROM joom_template_styles s WHERE s.template = 'templatename' AND s.client_id = 0)


141107 18:02:12 [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: UPDATE `joom_menu` SET `alias` = 'OSE Fileman™', `path` = 'OSE Fileman™', `published`=1, `img` = '"components/com_osefileman/favicon.ico"' WHERE `component_id` = ( SELECT extension_id FROM `joom_extensions` WHERE element ='com_osefileman' ) AND `client_id` = 1
The replies under this section are restricted to logged in users or users with an active subscription with us