Talk:Backup 2.0: Difference between revisions
From MoodleDocs
Oleg Sychev (talk | contribs) (New section: Semi-automatic backup) |
|||
| Line 4: | Line 4: | ||
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) | 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) | ||
::Hi Oleg, absolutely! I've had that sort of "declarative backup and restore" in my mind since ages ago. I'm not sure if install.xml file will be the source for that sort of information or, perhaps, we could have one "parallel" structure, mainly because I'm sure we'll need to support some extra bits like custom functions and so on to be specified. In any case, install.xml can be the start for that, sure! --[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 08:30, 2 March 2009 (CST) | |||
Revision as of 14:30, 2 March 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)
- Hi Oleg, absolutely! I've had that sort of "declarative backup and restore" in my mind since ages ago. I'm not sure if install.xml file will be the source for that sort of information or, perhaps, we could have one "parallel" structure, mainly because I'm sure we'll need to support some extra bits like custom functions and so on to be specified. In any case, install.xml can be the start for that, sure! --Eloy Lafuente (stronk7) 08:30, 2 March 2009 (CST)
