View Single Post
Old 01-14-2013, 03:07 AM   #7
chaley
"chaley", not "charley"
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 4,926
Karma: 802238
Join Date: Jan 2010
Location: France
Device: Many android devices
Quote:
Originally Posted by Sabardeyn View Post
I just went back to the original database, with the errors. I performed the search, altering the column name, cycling through each of my real custom column's names. I got back 26 responses for one custom column (#universe), but none of the books shown were the titles that caused the error.

I also tried to edit the metadata on the 26 books. The Edit Metadata screen appeared without throwing an error at all. Perhaps, since I'm now using 9.14 and that should include the fix you mentioned, maybe calibre is handling things internally properly? So these "new" errors are not occuring, but the old ones exist in the database already, thus the continuing complaints?
Your experiment indicates that the bug probably has nothing to do with your current problem. The fix was to ensure that the value of a custom series index is set to 1 when the series is applied to a book. It is later changed to what the user specified, assuming something was specified. This is the same behavior as the standard series.
Quote:
Would your fix require previously "damaged" entries to be corrected manually, or would the correction be done in some automated fashion?
The entries need to be corrected manually. The fix ensures that no new ones will be made. The errors are corrected by editing the custom series.
Quote:
BTW, I think I found another error with composite columns and series/series_index. But one error at a time.
Ohhhh, I can hardly wait.
chaley is offline   Reply With Quote