View Single Post
Old 07-07-2013, 11:28 PM   #166
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 PeterT View Post
Ugh; that's kind of ugly. I suppose naive me had assumed that the volume-id / serial # / some unique value would also be stored, allowing one to easily swap between multiple SD cards without the need to re-scan them each time.

So many items seem to have a good initial thought to them, and then some poor implementation choices.
There is an id for the card stored in the ExternalId column in the content table. It is an 8 character hex value and I have no idea where it comes from. I have seen different values in the column. I could match one value to a card, but not the other. I assumed the cleanup when the new card had been inserted failed.

Also, the hex id is in the "Kobo eReader.conf". It's that "90164EF8=true" line. I have seen a couple of these in the file at the same time, but only one of them was used in the database.
davidfor is offline