I have the cleaner for the PerlMonks backup dumps ready in some way, but I have some questions remaining on the tables which are needed for Everything operation. Especially the various approval tables escape my understanding - which of these tables are necessary?
What follows is the relevant excerpt of the config file I use to drive the process of copying/purging/passing the tables from the MySQL mysqldump files into a fresh dump file which is cleaned of sensitive data. I hope it is self-explanatory - "output" copies the CREATE and INSERT statements, "drop" removes the CREATE and INSERT statements, "purge" only copies the CREATE statement.
output approval (approved_id,user_approved,whenapproved,status) output approvalhistory (approves_id,user_approves,whenapproves,section +_id,action) output approvalstatus (approved_id,user_approved,whenapproved,status) output approved (user_id,node_id,action,tstamp) #output approves (approves_id,user_approves,whenapproves,action,sectio +n_id) drop approves drop backup_scratchpad drop backup_user # What is protouser? drop protouser # ??? drop rating # These seem to be more used drop testpolls drop testpollvote # The stuff in the tomb is gone for mortals purge tomb #version.version_id #version.version drop version
Any hints on what other tables can be dropped are welcome too.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: What tables are necessary for PM/Everything operation?
by demerphq (Chancellor) on Jun 29, 2006 at 15:24 UTC |