Your comments
For my own instance, I allow Ubooquity to use up to 1GB of memory ( -Xmx1024m).
Not because of the size of the database (about 10k books), but because of some big/complex PDF files that required a lot of memory to be rendered.
I'm not sure your database file issue was linked to the mount of allocated memory though...
In progress. ETA: 2019.
Ubooquity require Java 8. (you are using version 11)
Compatibility with Java 9 and above will come in a future release.
I don't know exactly what happened, but your database file definitely seems unusable. :(
If you want to make a test before getting rid of it, you can rename it (after stopping Ubooquity) in case you want to restore it later: the file is named "ubooquity-5.mv.db".
Could you post the rest of the error you get after these two lines ?
I think your database file is corrupted (but show me your error before reimporting everything).
Thanks for the bug report and the fix info !
I'll test the fix and try to include it in the next version of Ubooquity.
Hello Dmitry,
I confirm that the size of your database is not normal. It should not be this big.
Do you have any error in the Ubooquity log file ?
Customer support service by UserEcho
Hi Scott,
I'm in the process of merging books and comics in Ubooquity. This has of course a lot of impacts on the database and the way the metadata is stored.
This merge will make it easier to provide full theming (HTML templates in addition to CSS) for Ubooquity.
The interesting point is that, under the hood, the themes will use maps of metadata.
So exposing them through an API should not be too complex.
BUT I want to finish books/comics merge, theming and read/unread status (and release a version) before anything else.
So an metadata API will not be part of the next version, but feel free to remind me of your idea once the version is released (I might have forgotten it by then), as I find it quite interesting.