Quote:
Originally Posted by chaley
Unless the value is precomputed for each book (book, not format), a custom column would be a performance catastrophe. Reason: touching any custom column for a book record causes the computation of them all. Sorting on something would compute the word count for all books in the library. Doing that for 10,000 books could take many minutes.
|
I was thinking the plugin would work this way:
- User highlights a list of books, selects 'Calculate Word Count'. (or whatever it's called)
- Grab of 'one' of the books formats (probably use the preferred format list to choose the best one)
- Get the word count, compute it, and populate the custom field/column (field chosen in plugin config).
In other words the user would need to manually populate the field by using the plugin - this would be the equivalent of what you mean by pre-computed, correct?
If the user did select several thousand books and ask to compute word count for them all this would indeed be a hit of many minutes, but I think it would be one time this way, right?
My problem might have been my use of the term 'custom column', not sure if that means a column that's dynamically populated to some people.