View Single Post
Old 03-18-2017, 03:27 PM   #5
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,777
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by theducks View Post
Columns are stored INSIDE the DB (because they are unique to that library).
Does the rest of Calibre (edit metadata) work correctly?


does it work if you start it from the commandline with PI's disabled?

Code:
calibre.exe  --ignore-plugins


@Margot1975 - is it one one the built-in columns (i.e. one of those shown in my previous screen shot) or a custom column? If latter what type of custom column?

Which OS = MS Windows, Apple OSX or Linux, if latter which one?

One other thought, you wrote

Quote:
But when I restart Calibre, then everything is the same as before the change the newly added column is not visible.
How do you normally terminate calibre in order to restart it?

Could you try this: after you make the change do a restart from within calibre by pressing Ctrl+R? That will terminate calibre and start it again automatically. Do you get the same mis-behaviour?

BR
BetterRed is offline   Reply With Quote