Hi All, I've been talking to bsag about yaml importing. Recently I needed to import some yaml data into a clean tracks install, so I wrote up some code to do it. But this would only work if you wanted to start from an empty database, or override existing data with what you have in your yaml file (ie, restoring to a saved point).
Bsag mentioned that the plan was to integrate yaml_db somehow. But the down side to this is that it is used for dumping the whole database, a useful feature, if you are the admin ... but for single user backups (or in the case of a hosted version of tracks) this isn't really an option So, my question to you is, where do you see the yaml export's going? Should we make an interface for the users(well admins) to use yaml_db to backup/ restore. Should we stick with the current, per user, export, import. My feeling is that it might be worth having both options. What do you think? what are the benefits of these options? -- Geoffrey Donaldson _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
