Talk:Backup 2.0: Difference between revisions
From MoodleDocs
(New page: backup/restore one topic only (not just one activity)? --~~~~) |
Oleg Sychev (talk | contribs) (New section: Semi-automatic backup) |
||
| Line 1: | Line 1: | ||
backup/restore one topic only (not just one activity)? --[[User:Samuli Karevaara|Samuli Karevaara]] 07:35, 2 February 2009 (CST) | backup/restore one topic only (not just one activity)? --[[User:Samuli Karevaara|Samuli Karevaara]] 07:35, 2 February 2009 (CST) | ||
== Semi-automatic backup == | |||
Actually install.xml already contains most information that are needed to backup/restore component tables. If it will have some new features (mostly to describe id-links between a tables), it should be possible to make semi-automatic backup/restore in core, lifting from the modules a weight of backup code (which is really duplicates same pattern most of the way). The modules may still want some recoding capabilities on restored content if needed, but main backup/restore would be coded in core. Not very easy to implement, but quite an improvment to system architecture. --[[User:Oleg Sychev|Oleg Sychev]] 19:21, 7 February 2009 (CST) | |||
Revision as of 01:21, 8 February 2009
backup/restore one topic only (not just one activity)? --Samuli Karevaara 07:35, 2 February 2009 (CST)
Semi-automatic backup
Actually install.xml already contains most information that are needed to backup/restore component tables. If it will have some new features (mostly to describe id-links between a tables), it should be possible to make semi-automatic backup/restore in core, lifting from the modules a weight of backup code (which is really duplicates same pattern most of the way). The modules may still want some recoding capabilities on restored content if needed, but main backup/restore would be coded in core. Not very easy to implement, but quite an improvment to system architecture. --Oleg Sychev 19:21, 7 February 2009 (CST)
