Re: persistency troubles

Klemens,

The current production version of HSQLDB, 1.7.1, does have some known
problems with cleanup after a crash. That's one of the reasons I've
been telling everyone in this group that they should *backup* their
pixory database-- it's essential. Even if HSQLDB were perfect at
recovering from crashes, Pixory could introduce bugs that could affect
data  integrity.

That said, in my experience, HSQLDB 1.7.1 has been very good (though
not perfect) at recovering from crashes. I routinely kill the Pixory
process and almost never see data corruption. Also, the authors of
HSQLDB have substantially rewritten core pieces of their database to
greatly improve  robustness of HSQLDB 1.7.2. That version, 1.7.2, is
getting close to production release.

But in your case, maybe you don't have to worry too much. A lot of
important album information does not originate from the DB-- it's
stored in the .alb XML files under each album directory. These XML
files have so far been completely resistent to corruption. Here is the
persistence story:

In the DB:

Contacts
Shares
Configuration Information

In the .alb XML files:

everything else (rotation, captions, ordering, etc.)


If your database gets wiped out, you only permanently loose Contacts,
Shares and some Configuration Information. The rest of the information
that goes into the DB can be repopulated from the .alb XML files by
using "Configuration->Advanced->Indexing->rebuild now". Uhmmm, that
is, you will be able to "rebuild now" as soon as I reenable it, which
should be a few days.

regards,

joe



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/pixory-beta/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/