Thread: Kobo Bug thread
View Single Post
Old 06-04-2013, 09:40 PM   #122
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Lucas Malor View Post
I found where they store searched strings: under `Kobo eReader.conf`. I could be conceited, but I found it a very stupid place to use as searched terms storage, when you have a database and you record any single dictionary activity...
Those are terms used for library searches. If you look in the database at the table content_settings, the "RecentBookSearches" column stores searches done within a book. This is searching for occurrences of a word in the book, not the dictionary.
Quote:
Anyway it's strange that new rows with EventType=9 are created, since they have all ContentID = NULL and the primary key should block this.
A quick search tells me that SQLite allows nullable columns to be used in the primary key. It is a known bug that they would cause problems to fix. And once you allow nulls in the PK, allowing multiple entries in the index with NULL is the correct behaviour.
Last edited by davidfor; 06-04-2013 at 09:42 PM. Reason: grammar
davidfor is offline   Reply With Quote