On Thu, 8 Sep 2005, Joerg Lehmann wrote:
I finally got around to do some little PyTone work. Since there were some complaints about the huge disk space consumed during the song db upgrade, I now added an alternative, non-atomic database upgrade code and prompt the user before an upgrade. This is contained in the next prerelease, which can be found here:
http://www.luga.de/pytone/download/PyTone-2.3.0-pre2.tar.gz
If you still have an old database lying around, please give it a try - as always, I would really appreciate feedback on this change.
It worked very well on my laptop and I would make it the default method. Why would it need to be atomic ? Can't we perform the upgrade on a copy and if everything is ok, move it back (atomic) ?
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]