View Single Post
Old 05-05-2013, 02:34 AM   #7
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 offby1 View Post
There's no metadata.db conflict; I assumed that must have been the case, but it turns out no. For what it's worth, the content server _only_ reads the DB, it never (at least, not under my control) writes to the DB.

I have resolved the issue, however; it turns out I'd misunderstood how and when calibre writes to the DB; it writes on exit, not on edit, which meant that my changes had not persisted until I quit Calibre on my editing host.

*facepalm*

Thanks for the feedback.
Excellent, thanks for the update.
DoctorOhh is offline   Reply With Quote