Part of the /user/ dir can be a tmp file that is writeable ( I
already have one for my lifestream plugin ), and we can put the
backups in there. I just thought of it when talking to Morydd.
Most people won't backup their DB's before upgrading, and if we can
build in something like that, I think it would be really nice.
Thoughts?
Chris
As I'm sure skippy will attest, this is harder than you might think.
Owen
It's an _awesome_ idea. I really like the idea of making Habari be so
cautious as to execute a backup before upgrading.
It is, of course, non-trivial. If it works, it'll work well. If it
doesn't work, it'll break badly and then Habari will be seen as a poor
product. :(
Some sort of checklist might be possible, such that Habari tries to
determine whether it can backup first. If it can, Habari should
probably prompt first, to make sure the user is aware of what's going to
happen in the event of a foul-up.
> On Aug 13, 2007, at 10:46 AM, Owen Winkler wrote:
>
>> On 8/13/07, Chris J. Davis <c...@chrisjdavis.org> wrote:
>>> How about we hook an auto db backup to the db-delta process?
>>>
>>> Part of the /user/ dir can be a tmp file that is writeable ( I
>>> already have one for my lifestream plugin ), and we can put the
>>> backups in there. I just thought of it when talking to Morydd.
>>> Most people won't backup their DB's before upgrading, and if we can
>>> build in something like that, I think it would be really nice.
>>>
>> As I'm sure skippy will attest, this is harder than you might think.
>>
>> Owen
--
GPG 9CFA4B35 | ski...@skippy.net | http://skippy.net/