Page MenuHomePhabricator

Fix up core logging spec
Closed, ResolvedPublic4 Story Points

Description

In digging on using logging / reverts on staging I identified some ways in which the data storage definition should be reviewed

  1. The INNODB storage engine is much better than ARCHIVE - I added the ability to define the table definition by hook

https://issues.civicrm.org/jira/browse/CRM-18193

  1. The wmf_xx tables are being missed off because they do not start with wmf_

https://issues.civicrm.org/jira/browse/CRM-18180

  1. The use of the non-unique CONNECTION_ID() as log_conn_id introduces all sorts of complexity that is not helpful

https://issues.civicrm.org/jira/browse/CRM-18193

Event Timeline

Change 277928 had a related patch set uploaded (by Eileen):
Fix for enable loggin in multisite

https://gerrit.wikimedia.org/r/277928

Change 277929 had a related patch set uploaded (by Eileen):
CRM-18193 create all new log tables with log_conn_id = varchar(17)

https://gerrit.wikimedia.org/r/277929

Change 277930 had a related patch set uploaded (by Eileen):
CRM-18193 add routine for converting log tables to support new log_conn_id format & hook spec

https://gerrit.wikimedia.org/r/277930

Change 277934 had a related patch set uploaded (by Eileen):
Add hook to define log tables, specifying INNODB & indexing contact fields

https://gerrit.wikimedia.org/r/277934

atgo removed a subscriber: atgo.Mar 30 2016, 10:05 PM

Change 277934 merged by jenkins-bot:
Add hook to define log tables, specifying INNODB & indexing contact fields

https://gerrit.wikimedia.org/r/277934

mmodell removed a subscriber: awight.Jun 22 2017, 9:51 PM