Thread: do not support
View Single Post
Old 05-13-2019, 07:32 AM   #16
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by compurandom View Post
I wasn't implying you should remove the message.
I was more interested in what "a long time ago" was, but I can't remember time intervals well either.

Actually, I was thinking that it might be a good idea to look for big* schema changes and if seen, ignore the checkbox for all those who just have it permanently checked now, but maybe you already do that?



* for some very special definition of "big"
The problem is "big". This firmware has one new table. And a couple of new columns. But, calibre doesn't look at them. Even main table that is used has had multiple columns added with no real impact. It is unlikely anything will happen, but there is some risk.

The topic has come up in the calibre forum as well. If I can come up with the right wording, I might try what I suggest at the end of that thread.
davidfor is offline   Reply With Quote