View Single Post
Old 05-06-2010, 03:41 PM   #9
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by itimpi View Post
Just a check - if I want to use the beta is it only the metadata.db file that has changed dramatically and that would need restoring to revert to te non-beta release? Are the ebook files and folder structure unchanged?
To the best of my knowledge, you are correct. The changes are to the DB, not to anything stored in the filesystem. Ahh -- I remember some bug reports about EPUB svg covers, but the related changes should be in both the released and beta versions

Quote:
If that is the case as I start Calibre with custom batch files that explicitly name the location of the:
- Calibre program files
- metadata database
- config files
- ebook files
I should be able to use two in parallel as long as I only add books via one of them? A bit easier than committing myself up front.
Again, yes. In particular, the gui.py config file has changed to accommodate the custom columns and user-defined categories, so separating the config files out is a good idea.

I have had some luck with moving between production and beta by deleting and re-creating the config directories, which reinforces your intuition. I did have a couple of situations where I was forced to recreate the config files because columns simply disappeared. These seemed to be related to exceptions in the production version raised when unknown columns appeared in either the saved geometry or the column list.
chaley is offline   Reply With Quote