Quote:
Originally Posted by library addict
I think the second option is better as well.
Changing the lookup name would be rare as you said. And it seems to have less chance for side affects.
|
Quote:
Originally Posted by PatNY
Hello Charles,
I much prefer the option that has the fewest unpredictable results. I've changed lookup names maybe once or twice over the last 4 years, so this wouldn't be a major problem. Long sync times are not a problem with me either, as long as I know it's a normal thing -- and not a freeze. So if you go with the second option, you may simply want to make sure all the instances that could cause long sync times are listed in your FAQ section.
--Pat
|
Thanks to both of you for your opinions. I am leaning more strongly to the second option. One reason is that I figured out a way to make the DB upgrade run much faster in this case, around 8 or 9 books per second.
@Pat: the problem isn't sync times. Those won't change. The problem is that when you set or change a lookup name, CC must change the database. This process can be long, and while it is going on the user cannot use the grouping drawer or connect to calibre. If you have 4000 books in your library the process will take around 10 minutes.
If I go down this road then I will change the dialogs where you enter the information to be clear that tapping OK will trigger the upgrade, permitting the user to choose a convenient time to do it.