Page MenuHomePhabricator

configure database backups for new log_civicrm database
Closed, InvalidPublic4 Story Points

Description

log_civicrm needs backup like civicrm

(Killing this as they are all in one DB & triggers are covered elsewhere)

Event Timeline

Jgreen created this task.Apr 25 2016, 11:22 PM

Hi Jeff,

Are we definitely going with the same DB? I think we are - in which case I need to tweak the mysql for Monday to that

Yes, let's go same db.

@Jgreen does anything still need to be done here?

The tables are already backed up, included with the rest of the civicrm
database.

I'm not sure what to do about the triggers--since they're code and not
data I'm not sure of the additional value of backing them up over what's
already tracked in revision control.

@awight any concerns with leaving backing them up in favour of relying on the git version / the fact that they can be regenerated at will

Eileenmcnaughton closed this task as Invalid.May 25 2016, 10:37 PM
Eileenmcnaughton updated the task description. (Show Details)

@Eileenmcnaughton
The only benefit I can think of is that backups would give us a record of which triggers were actually deployed, but that seems pretty secondary.

Should we make another TODO, to generate the trigger SQL as part of any schema changes and be sure that it's always up to date?

AFAIK a dump only provides the state of the database at dump time, so I
don't think it can be used to establish a cronology of queries vs which
triggers were in play at the time of the query.

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