Quote:
Originally Posted by DaltonST
@Andys:
For Custom Columns, of course. Easy. Simply change table custom_columns in metadata.db for the specific Custom Column you wish to protect. Do this while Calibre is not running. See the attached example.
If you need a tool to do the edit, download the 'DB Browser for SQLite' tool from http://sqlitebrowser.org/
Needless to say, be careful what you touch in metadata.db. If appropriate, practice first on a test library. Also, close the tool before running Calibre.
DaltonST
|
Quote:
Originally Posted by Andys
Thanks!
I had to use global mouse tweak since I utilize a lot of default columns, and only several custom.
|
FYI: this is *not* guaranteed to work. The "editable" field was added way-back when we first introduced custom columns and neither really implemented nor removed. At this point, several years later, very few of the internal calibre functions check it. For example, bulk metadata search/replace doesn't. In addition, there is no guarantee that making such a change will not break something else. Finally, the APIs that *do* check it include the edit metadata functions, so you might be prevented from making changes to such a field when you want to.