06-02-2013, 07:24 AM | #106 |
Member
Posts: 19
Karma: 41366
Join Date: May 2013
Device: Kindle Voyage, Oasis
|
|
06-02-2013, 07:49 AM | #107 | ||
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Quote:
|
||
Advert | |
|
06-02-2013, 07:55 AM | #108 |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Whatever they are doing with those rows is weird. I deleted all except one row. After a few dictionary lookup, that row was unchanged, but the new ones where all 1 higher than it. I thought it might have been recording all lookups, but only counting the lookups in kepubs. A quick test showed that doesn't seem to be the case.
|
06-03-2013, 03:34 AM | #109 |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
|
06-03-2013, 06:17 AM | #110 |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
|
Advert | |
|
06-03-2013, 07:08 AM | #111 |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
|
06-03-2013, 07:58 AM | #112 |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Interesting. I reset my Touch over the weekend, but hadn't done any reading with it. There was no EventType 9 rows, but a few dictionary lookups and I had one row with count of 17. I have deleted the rows from the Glo as well. I'll see what happens.
|
06-03-2013, 08:22 AM | #113 | |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Quote:
I looked into a backup copy of the db from the short time when I used FW 2.5.0. There is exactly one EventType 9, and the EventCount is 10. So this bug seems to have been introduced later. Last edited by tshering; 06-03-2013 at 08:25 AM. |
|
06-03-2013, 08:33 AM | #114 |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Now I looked up an older packup. Don't know the FW, but db version is 55. There I have one EventType 9 with EventCount 460.
Last edited by tshering; 06-03-2013 at 08:44 AM. |
06-03-2013, 08:40 AM | #115 | ||
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Quote:
Maybe it is "Reading Life". Do you happen to have that on or off? |
||
06-03-2013, 09:01 AM | #116 | |
Wizard
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
Quote:
Edit: I switched Reading Life on and did some dictionary look-ups. EventCount is now on 19. Still only one EventType 9. My assumption that a previous FW stopped registering dictionary look-ups after 10 proved wrong. So it seems, it was by chance that I switched Reading Life off after exactly 10 dictionary look-ups. Or does it count until 10 independent of the reading life setting? I am not going to check this now. Last edited by tshering; 06-03-2013 at 09:17 AM. |
|
06-03-2013, 02:41 PM | #117 |
Pain in the arse
Posts: 758
Karma: 77856
Join Date: Apr 2013
Device: Kobo Aura One, Kindle 4
|
Probably we want to collect some statistics about dictionary lookup, so they can sort them by usage and date.
|
06-03-2013, 07:34 PM | #118 | |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
The data doesn't look right for that. They aren't storing the word that was looked up or the book. And the rows all have the same EventCount. While they can see when I looked up a word, I'm not sure how useful that is. As we have shown the extra rows are not always added, it seems to be a bug to add them. |
|
06-04-2013, 04:03 AM | #119 |
Pain in the arse
Posts: 758
Karma: 77856
Join Date: Apr 2013
Device: Kobo Aura One, Kindle 4
|
I get a look to my db (I have firmware 2.4): there's only one EventType=9 row, that is updated every time I search in dictionaries. There's also an ExtraData column, that seems empty. There's no related trigger under the Master Table. I have not found any dicionary word inside the db... maybe they are stored outside?
PS: searched strings can be associated to the event table row through the ID. |
06-04-2013, 07:20 AM | #120 | |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
No, there isn't a useful key. The primary key is EventType plus ContentID. For EventType=9, ContentID is always blank. The row isn't updated, it is deleted and a new one is insert. You can tell that from the rowid. If the row was updated, this wouldn't change. Because of that, the rowid isn't useful elsewhere. It could be used, but it would be a pain And the mention of the primary key tells me what I think has happened. In all the duplicates in my backup databases, the ContentID is NULL. That is allowing multiple rows in the database with the same EventType. I deleted all the EventType=9 rows the other night and the new has an empty string for the ContentID. There can only be one of those in the database. I would say that sometime in the distant past, a firmware version erroneously inserted the row with NULL ContentID. The code obviously doesn't handle this correctly and didn't delete the rows but was able to insert the new row. The new row was probably created from the memory copy of the row read from the database, and hence inherited the null ContentID. This also explains the performance problem. I have a sneaking suspicion that the code is selecting all rows with EventType=9 expecting there to be only one. A cursor is opened on this and then, instead of just using the first row found, it reads all of them. That would be OK if there was only one row, but when there are several thousand, it takes time. The fix is to delete all the rows or delete al except one and change its ContentID to an empty string. And I suspect the firmware has already been fixed to prevent this incorrect row being created in the first place. |
|
Tags |
pocket app |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Probably a Kobo bug. | eXistenZ | Kobo Reader | 19 | 06-13-2014 09:16 PM |
[Old Thread] Bug in downloading metadata | Dasun | Library Management | 3 | 03-21-2011 07:31 PM |
Possible bug or misfeature when a thread is closed | tompe | Feedback | 7 | 10-05-2010 09:38 AM |