View Single Post
Old 05-09-2023, 05:55 PM   #8
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,824
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by chaley View Post
Of course that means that the permitted interleaved updates will probably scribble on each other. That is why ACID semantics are generally accepted as a good thing. But in the end, up to you ...
I was responding to the assertion:

Quote:
Having the book open in ANY viewer will lock files.
The "ANY" is not my emphasis… it's @theduck's.

Of the "viewers" I use frequently, I get one of three behaviours if I change a book title in calibre whilst they have the file open, e.g.:

a) they lock the files and calibre won't allow me to change the book title - PDF xChange and MS Word.

b) they discover the file location has disappeared when the file is saved - Sigil, calibre ebook-editor.

c) they detect the change as it happens and have a whinge about it - Notepad++.

I suspect most calibre users would associate ACID with something they had in the '60s or the Doors or Jefferson Airplane rock bands. Changing a book's metadata in calibre whilst one of its format files is open in another program is like ACID in one respect… best avoided without medical supervision

BR
BetterRed is online now   Reply With Quote