View Single Post
Old 06-10-2009, 04:18 AM   #5
gwynevans
Wizzard
gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.
 
gwynevans's Avatar
 
Posts: 1,402
Karma: 2000000
Join Date: Nov 2007
Location: UK
Device: iPad 2, iPhone 6s, Kindle Voyage & Kindle PaperWhite
Quote:
Originally Posted by tklaus View Post
Or if someone can point me to a location in the source where I can hack an alternate path to the metadata.db file, I'll try this experiment myself.
Probably the line "self.dbpath = os.path.join(library_path, 'metadata.db')" in "LibraryDatabase2.__init__" in "calibre.library.database2.py" is where you need to start. Try commenting that out & setting an absolute path to your local 'metadata.db' & see if that works/makes any difference.

To test, you'll either need to build calibre fully from source (best for debugging, etc) or failing that, get the source that matches your released version and use calibre-debug to replace the frozen module (in library.zip - take your own backup ) in the distribution.
gwynevans is offline   Reply With Quote