Storing catalog configuration in database (bib, csv, xml)

Bug #1730500 reported by Terisa de Morgan on 2017-11-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Undecided
Unassigned

Bug Description

It add a config module and stores catalog configuration (bib, csv, xml) in the database, so it can be different across libraries. It recovers the json configuration if it is the first time the catalog is generated with this new version.

The other catalogs still recover their configuration from the json file.

Kovid Goyal (kovid) wrote :

Sorry, it is going to be a little while before I can get to this.

Terisa de Morgan (terisam) wrote :

If you prefer, I can try to do a pull request.

Kovid Goyal (kovid) wrote :

It's fine, I just am busy with something, so I dont have the time to review the code and merge it.

Kovid Goyal (kovid) wrote :

I have implemented it for CSV/XML. If you need it for bib as well, feel free to send a pull request, using the same technique I used for csv/xml.

Fixed in branch master. The fix will be in the next release. calibre is usually released every alternate Friday.

 status fixreleased

Changed in calibre:
status: New → Fix Released
Terisa de Morgan (terisam) wrote :

Thank you very much, bib was only for completeness, but there are no big changes, real problem was csv.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers