[pLog-svn] update to 1.1
Jon Daley
plogworld at jon.limedaley.com
Fri Mar 24 03:38:18 GMT 2006
On Thu, 23 Mar 2006, Oscar Renalias wrote:
> It's quite difficult to do a rollback of this kind of changes... How can we
> know at which point an installation was stopped so that we can restart from
> that point in case the process needs to be restarted?
Yes, that is true. But, being able to hit next, after the user
thinks the problem has been solved (maybe not anyway for him to actually
solve the problem anyway??) and have the wizard not fail because the
wizard is duplicating the steps he already did, would be nice.
I guess it would make things more complicated, but if the wizard
was trying to add a column called, "stuff", and wanted it to be a varchar,
etc. and when he goes to modify it, he sees that there is already a
varchar column called "stuff", he could just skip it or something.
Once mysql 5 is more common, I think it has transactional
rollbacks, doesn't it?
More information about the pLog-svn
mailing list