db.set_custom on custom series column ignores [number]
Bug #1220914 reported by
Jim Miller
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_
#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
To post a comment you must log in.
Fixed in branch master. The fix will be in the next release. calibre is usually released every Friday.
status fixreleased