View Single Post
Old 07-28-2014, 09:20 PM   #13
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
What is the table? Is there some BLOB field?
Yes, it is a BLOB with what I assume is serialized data in it. I can see some info in them, but not enough to easily decode it. Or have a real desire to do so.
Quote:
Originally Posted by Lucas Malor View Post
There's a possibility that the problem is caused by nickel itself. Since db data are not as it expects, it could do something wrong and do a transaction without close it. I do not bet on it, but you never know.
I am pretty sure the driver is deleting everything correctly. If something is missed, it would be very bad if nickel killed the database because of it.

But, when do you see the corruption? If it is while the delete is done, then it isn't likely to be nickel. If it is the next connection, that might be different.
davidfor is offline   Reply With Quote