Quote:
Originally Posted by TIHTCM
Hi Christoph,
Hope you're doing well. I’ve been following your new project and it looks really promising, so I wanted to reach out. I’d definitely be interested in helping test it as things move forward — I run a pretty large Calibre setup and would love to put it through real‑world stress.
Two features I rely on heavily in Calibre are duplicate detection and full‑text indexing/search. Are those already implemented in your system, or planned for a later phase? They’re core parts of how I manage my library, so I’m curious how you’re handling (or planning to handle) those workflows in the new architecture.
I also had a technical question about the database model:
Is metadata.db still required, or is your PostgreSQL database intended to be the primary/only metadata store?
My library is over 50k books, and the SQLite metadata.db tends to corrupt more often than I’d like. If your project allows relying on PostgreSQL alone, that would solve a major stability issue for me.
Thanks again for putting this together — happy to help test, stress, and break things if that’s useful.
Best,
TM
https://www.mobileread.com/forums/sh...54#post4575254 |
Hi TM,
Thanks for your mail. Testing is already done and the App is just released, see my other forum message. You can download it from
https://www.dcm-works.net/
Regarding your questions:
1. The App detects duplicates during import process.
2. There is a full text index search on the books page. You can also filter on the categories.
3. The App still relies on the SQLite metadata.db. But i think it would be easy to implement that you can switch it off and working only on the postgresql database. Please check out the App and if you still have problems with the SQLite database return to me and i will implement it. Thanks!
Best regards
Christoph Weller