Quote:
Originally Posted by Stevex
(1) arrgh you are right it's a trigger not an sp embarrassing
(2) I also have 000's of books on the device but it doesn't have any noticeable performance effect whatever*. I know what you mean about overkill but I just wanted to be sure it runs and the tile thing is guaranteed updated.
|
If it performing OK, then good. But, updating a lot of extra rows when not needed is something I really try to avoid.
Quote:
(3) I can think of quite a few improvements, and in fact last night I just did one last night after I posted because it was in my head, but it's just not worth it to beautify it much the thing is simple took me about a minute to do and works
(4) you are right I don't have any purchased books only sideloads but I don't -think- pushing dateread into the past (which is all this does) would impact anything?
|
I didn't think it through yesterday, it just gave me an uncomfortable feeling.
The main affect will be for people using multiple devices or the apps. When you open a purchased book, it contacts the server to get the latest reading position. If you have been reading on another device, you get a prompt to ask if you want to go to the new position. The check is based on the timestamp, not the actual position in the book. And if a sync is done, the position from the later timestamp is taken without any prompts.
And I think it will mean a sync takes a lot longer. Every purchased book with a series number will trigger a change when they haven't really changed.
And of course, for anyone who is using my Kobo Utilities to store the reading status, there are going to be some consequences.
Quote:
* PS: To me, on my aura glo hd, in my use case, caveat caveat etc etc ;-)
PPS It's an easy thing to try, it's brilliant for me, and for anyone else who wants to try it it's at the worst a bit of fun really as long as you back the db up first
|
Yes, everyone, back up your databases before messing with them.