MobileRead Forums - View Single Post

chaley · 07-12-2013, 05:57 PM

My theory, supported by the new apk working, is the B&N "improved" the database code in android to more aggressively recover space. This would be appropriate for devices like the nook color that are severely memory challenged. It is much less appropriate for the newer devices like the hd that are reasonably well configured.

To be a bit more precise, I think B&N decided to delete temporary tables when a transaction completes, not when the app terminates. That would cause the table to suddenly disappear. Changing it to a permanent table prevents that from happening.

We are very happy this change solved the problem. We will roll out the change to everyone else over the weekend.

Thanks for your help!

07-12-2013, 05:57 PM	#14
chaley Grand Sorcerer Posts: 12,476 Karma: 8025702 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	My theory, supported by the new apk working, is the B&N "improved" the database code in android to more aggressively recover space. This would be appropriate for devices like the nook color that are severely memory challenged. It is much less appropriate for the newer devices like the hd that are reasonably well configured. To be a bit more precise, I think B&N decided to delete temporary tables when a transaction completes, not when the app terminates. That would cause the table to suddenly disappear. Changing it to a permanent table prevents that from happening. We are very happy this change solved the problem. We will roll out the change to everyone else over the weekend. Thanks for your help!