db.set_custom on custom series column ignores [number]

Bug #1220914 reported by Jim Miller
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Fix Released
Undecided
Unassigned

Bug Description

Both calibre 1.1.0 and trunk (at time of writing) have this problem. 0.9.44 does not.

If I set a custom series type column using db.set_custom, it sets the number to [1], ignoring the number included in the string.

db.set_custom(book_id, "Series text [5]", label="#text_series", commit=False)

#text_series for that book is now "Series text" with index=1.0

The same code in 0.9.44 leaves "Series text" with index=5.0

Revision history for this message
Kovid Goyal (kovid) wrote : Fixed in master

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

 status fixreleased

Changed in calibre:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.