Bug: Deleting catalog.db also deletes ResourceCollectionManager.db

From time to time it's necessary to rebuild our Library Catalog. When then happens there's no need for Logos to delete all our collections, too! Or at least if it is doing to delete all our collections it should re-sync them back. At the moment, it doesn't. This is a serious bug. Logos shouldn't delete stuff from the Documents folder without syncing it back.

(The problem is that the LibraryCatalogId gets changed in catalog.db, which then doesn't match the value in ResourceCollectionManager.db so Logos wipes the whole ResourceCollectionManager.db.)

Find more posts tagged with

Comments

Mark Smith

At the moment, it doesn't.

I agree with this completely having lost all my collections like this twice. I was fortunate to have another computer with Logos on it and could get the collections there to sync and finally show up on the computer that lost the collections. Time consuming since you have to alter each collection to get it to resync, but at least I didn't lose everything permanently.

Milford Charles Murray

Peace, Mark! Happy Birthday and may our Gracious God bless you and your loved ones! *smile*

That sounds horrible! Lots of work to set up the collections. Please report back on this ....

Galatians 6:2

Mark Barnes

I agree with this completely having lost all my collections like this twice. I was fortunate to have another computer with Logos on it and could get the collections there to sync and finally show up on the computer that lost the collections. Time consuming since you have to alter each collection to get it to resync, but at least I didn't lose everything permanently.

I keep a backup of the files in Documents, but restoring ResourceCollectionManager.db on it's own doesn't work. You have to restore, then manually edit the value of LibraryCatalogId to match the new value in catalog.db (sorry I didn't work this out when you had the problem - I remember trying [and failing] to help!)

Mark Smith

(sorry I didn't work this out when you had the problem - I remember trying [and failing] to help!)

The first time I had the problem you fixed it for me. The next two times I used the method above.

We need a way to locally backup and restore data. It might be a nightmare to create but most of us have too much work put into a lot of different databases in L4 to afford to lose them by accident, glitch, or inadvertent error, and then have no recourse.

Dave Hooton

From time to time it's necessary to rebuild our Library Catalog.

Why is it necessary for you to rebuild it?

This is a serious bug. Logos shouldn't delete stuff from the Documents folder without syncing it back.

When re-installing Logos with the Documents folder in place** the Collections disappear from their db but the two db's end up with the same LibraryCatalogId.

When fresh installing on another computer Collections are the only document not restored.

This is a known, serious, problem and I'd like to know why it has not been fixed.

** when uninstalling, Logos does not remove the Documents folder.

Mark Barnes

Or at least if it is going to delete all our collections it should re-sync them back.

This is reported as fixed in 4.5a beta 3.