View Single Post
Old 03-05-2013, 09:42 PM   #47
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 Rev. Bob View Post
You misunderstand me. When I say device-to-sqlite-to-server, I'm not talking about directly touching the database.
I suppose I did. But, you had also suggested blowing the database away in another post, so what I said wasn't inconsistent with your advice.
Quote:
Instead, I mean that the database is an intermediate step between the device interface and the server, one that it seems has certain limitations that the apps' interfaces do not share. That's why the apps can Really Truly delete shelves, and syncing the device after such a pass means that instead of the faulty device-to-sqlite path, the changes propagate down the server-to-sqlite path instead. Since the device's sync date is older, good data comes down and bad data doesn't go up. That's why the sequence is so crucial: delete on server via app, THEN refresh device, THEN refresh app, repeat until done. It keeps the app "in charge" and negates the bad data on the device.
That is a good explanation of how it seems to work. But, I don't think there is a real difference between how the app and devices work. With my Touch and Glo, I have done the tests to check the syncing of shelves between the two. It works perfectly. And I very much doubt if there is a difference in how the basic way that the apps do their delete.
Quote:
Now, once you get your server info clean that way, of course you should log out of the device before doing anything else (to stake its database once and for all, before it can pollute the server again) and then log back in to build a fresh, clean one. Yes, I wound up doing this "the bad way" by just deleting the database wholesale, but the principle of "quarantine, treat, eradicate" remains sound.
That is way overkill. If the deletes and syncs all worked, then the database will be clean.

But, of course, if what you say about the apps doing it better, then your instructions are overkill, especially when you add the logout step. Solution is simple:

- Logout on the device
- Delete all the shelves on the app
- Sync the app
- Login on the device.

If that doesn't sort it out, then nothing will.
davidfor is offline   Reply With Quote