Re: ChangeLocation - fist try



Hi

Much appreciated.

On Wed, 2007-11-14 at 00:24 +0100, Lorenzo Milesi wrote:
> ciao
> 
> i've given a first try to the extension, as promised.
> 
> first: if the update gets interrupted, something "nasty" happens on the
> db. and you have to re-run ChangeLocation a few times to understand what
> happened and restore the db to a working situation. I believe I didn't
> myself clear on this, but I need to do some further tests to better
> undestand what happens. I'll tell you later.

:) Yes, I do not have to much disaster recovery in this extension, both
for exceptions as well as power failure.
Perhaps I should backup the database first as a safety option?
Hmm. Will need to think of some exception handling also perhaps.
Only way I can see is first to create some internal arrays with the
photos to change path of, and second to change the database. If
something happen you reverse the changes. Power failure can be handled
by automatic backup of the database.
If no negative comments to this plan I'll come out with 0.9.1 with this
kind of exception handling :)

> 
> second: ui lock. I've just run the ext on a small db, ~210 pics. after I
> press "apply" and the ext ui disappears, I get back to f-spot. sadly,
> after few photo clicks, cpu spin up to 100% and f-spot seems hanged.
> after some cpu/disk time, normal operations are resumed. I neither see
> the progress bar increasing, the dialog just goes away.

This one sounds weird, but could it be that you try to use f-spot to
quick after, and the database is not completely updated? When I tested
on a large database, the extension gui disappeared but the database took
another hour or two for the update to be finished.
Have no clue how to deal with this one, suggestions?

Thanks for the report :)

/Bengt



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]