View Single Post
Old 08-29-2021, 04:28 PM   #11
ownedbycats
Custom User Title
ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.
 
ownedbycats's Avatar
 
Posts: 11,018
Karma: 75555555
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
Question: Is it possible that the threading violation error could result in database changes no longer saving as described in this thread?

I read the other thread in Development but it was not clear whether it was a silent error (which I would not have noticed as I keep the debug log minimized) or not.

I did do a bulk-edit (if relevant, changing the value of an enumerated column) with the bugged version of Last Modified activated. I checked the books and the #lastmodified datetime was written to OPF and restored with the rest of the database.

Last edited by ownedbycats; 08-29-2021 at 04:54 PM.
ownedbycats is offline   Reply With Quote