Thread: Custom Column Filter - Unexpected behaviour
View Single Post
Old 09-25-2022, 06:14 AM   #11
Comfy.n
want to learn what I want
Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.
 
Posts: 1,641
Karma: 7908443
Join Date: Sep 2020
Device: none
Quote:
Originally Posted by chaley View Post
Never mind. I think I found it. It is an interaction between composites containing 'numbers' and blank columns. Indeed, in this case not #r:true does not equal #r:false.
Nice, anyway I'm attaching the metadata.db from a portable install (Calibre 6.5, Windows 10), in which the same behaviour was reproduced
Attached Files
File Type: zip metadata.zip (17.5 KB, 64 views)
Last edited by Comfy.n; 09-25-2022 at 07:17 AM.
Comfy.n is offline   Reply With Quote