View Single Post
Old 08-15-2018, 09:18 AM   #12
DoctorOhh
US Navy, Retired
DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.
 
DoctorOhh's Avatar
 
Posts: 9,897
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Kindle PaperWhite SE 11th Gen
Quote:
Originally Posted by sternbyname View Post
OK, so maybe CC has been programmed to do that (but surely this behaviour is an unfortunate side-effect rather than deliberate?) but it surely looks very like a bug from the user end.
This is not a CC issue, it is a unique user work case issue that rarely ever occurs in calibre. The reason this does not occur in calibre is because if folks want to update a book they simply drag the new version to the book details panel of the existing book and the book is updated without the need for a new ID. This process updates only the book, not any of the metadata.

There is no reason I can see for deleting a book then re-adding the book to update that book in calibre. This process creates a completely new book as far as calibre is concerned. This work flow is unique to you.

Last edited by DoctorOhh; 08-15-2018 at 09:22 AM.
DoctorOhh is offline   Reply With Quote