Quote:
Originally Posted by chaley
I know the problem is there because it happened to me today during upgrade testing. It took me several moments to figure out what had happened to my db. Fortunately, like you I had a backup and could get back to a known state so I could debug it.
|
It is nice to know I'm not alone. As it turns out Dropbox had 1080 backups of my metadata.db file over the last thirty days. Since I haven't added any books since March 4th it was easy to restore to a backup that included the #read column data.
Quote:
Originally Posted by chaley
Although it would be great if you could confirm it, given the size of your library the test would take ages. Only bother if you have those ages to spend.  |
This is what the beta process is all about. Since I currently only have 100 books on my device I'll be glad to test it. What are the circumstances required to replicate the error?