Quote:
Originally Posted by Kumabjorn
See, this makes sense, now I understand why it is the way it is. From a laywoman's perspective this begs two questions:
1. Can a plug-in scan the columns and determine their names?
2. Is there a specific reason Calibre needs to restart when a column is added?
Thank you for a rational explanation. I'd send you karma if I wasn't on Tapatalk.
|
#2
When you 'add' a column in the GUI and click Apply, that only sets up the task.
The db must be detached, then the field is created (and all the linkage custom column magick happens)
The restart allows the GUI to 'discover' and display the column .
#1 can't happen until the column exists from #2 restart (attach horse to cart)
BTW You probably noticed the many plugins need a restart when first installed. Same sort of thing. Get all the pieces in place then 'discover' them while building up the GUI.