[feature request] multiple databases support

Asked by TBeholder on 2018-04-12

Thanks!
qpdfview is great for reading/reference purpose (as opposed to quick viewing) without being cumbersome in the way some "library based" e-book readers are.

Per question #221717, a separate tabs table for keeping "sessions" would be great.
But also, it would be great if qpdfview could keep several bookmark + per-file databases too, named and completely independent. Perhaps either integrated or associated by name with the default "session" tabs table, i.e. just like database is now, but allowing to switch between them; the bases could be discovered in the default database path (or a list of paths in config, to support removable devices), or added and selected via command line. One for work, one for books, one for your favorite RPG, that sort of thing. Having documents for different purpose listed in different bases could immediately improve several areas, from reducing bookmark clutter to greater portability between computers.
The latter could be also improved by adding separate sets of associated base paths, relative to which the files recorded in the database are supposed to be located (even if those are from repositories, different distros sometimes place things in different places). Also, this would make it easier to move stuff around (e.g. from ".../downloaded" to ".../archive").
But even switching between databases alone could help a lot.

Question information

Language:
English Edit question
Status:
Answered
For:
qpdfview Edit question
Assignee:
No assignee Edit question
Last query:
2018-04-12
Last reply:
2018-05-03
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Adam Reichold (adamreichold) said : #2

Hello TBeholder,

sorry for getting back to you so late! I am seeing several distinct features here:
- per-instance bookmarks and per-file settings as with the tabs table, so that instances as defined via --instance or --choose-instance do not share those entities (this could be done completely by extending the existing database schema)
- store relative paths in those database tables which are then resolved w.r.t. some configurable root directory to simplify roaming setups (this could be done using the existing schema by extending the configuration, but would need some compatibility work as we are currently storing absolute file paths)
- have the database file somewhere else than the default data location which should already be possible by setting the XDG_DATA_HOME environment variable so that qpdfview searches there instead of in ~/.local/share.

If I understood you correctly, I would encourage to open a wishlist bug report for those of the above that would best support your use case.

Best regards,
Adam.

Can you help with this problem?

Provide an answer of your own, or ask TBeholder for more information if necessary.

To post a message you must log in.