You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... but only when the .db file looks like it is (near) empty, so that we don't loose a (lot of) wrongfully inserted metadata info along the way.
"Not a lot of metadata" means the .library file is less than, say, 6KB, which is about 1KB larger than the Qiqqa library template which was used to create that illegal .library file.
The text was updated successfully, but these errors were encountered:
…ext to an already existing S3DB file, delete it. We explicitly delete it to the RecycleBin so the user MAY recover the database file on the off-chance that this was the wrong choice.
- fixjimmejardine#144 :: Do not try to create a Qiqqa.library DB when the directory already has an S3DB database file
- some work done to find out how jimmejardine#142 came about.
- `WebLibraryDetails_WorkingWebLibraries_All`: make sure all 'Guest' libraries are added to the sync set: under very particular circumstances you CAN have multiple guest libraries, e.g. when manually recovering multiple Qiqqa libraries you extracted from your backups of previous qiqqa runs/releases.
- performance: speed up the sync metadata info collect action by NOT calculating the precise storage size of each library as that entails a HUGE I/O load as each library document's file system metadata would be queried for its filesize -- which is only used in the UI in an overview table and is deemed non-essential right now.
... but only when the .db file looks like it is (near) empty, so that we don't loose a (lot of) wrongfully inserted metadata info along the way.
The text was updated successfully, but these errors were encountered: