sqlite数据库文件损坏的问题解决

前端之家收集整理的这篇文章主要介绍了sqlite数据库文件损坏的问题解决前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。

再发生android.database.sqlite.sqliteDatabaseCorruptException: database disk image is malformed异常时候,以下是解决办法:

What is an sqlITE_CORRUPT error? What does it mean for the database to be "malformed"? Why am I getting this error?

AnSQLITE_CORRUPTerror is returned when sqlite detects an error in the structure,format,or other control elements of the database file.

sqlite does not corrupt database files,except in the case of very rare bugs (seeDatabaseCorruption) and even then the bugs are normally difficult to reproduce. Even if your application crashes in the middle of an update,your database is safe. The database is safe even if your OS crashes or takes a power loss. The crash-resistance of sqlite has been extensively studied and tested and is attested by years of real-world experience by millions of users."

That said,there are a number of things that external programs or bugs in your hardware or OS can do to corrupt a database file. Details can be found in the discussions on theatomic commitandlockingsupport in sqlite as well as in the mailing list archives.

Your can usePRAGMA integrity_checkto do a thorough but time intensive test of the database integrity.

Your can usePRAGMA quick_checkto do a faster but less thorough test of the database integrity.

Depending how badly your database is corrupted,you may be able to recover some of the data by using the CLI to dump the schema and contents to a file and then recreate. Unfortunately,once humpty-dumpty falls off the wall,it is generally not possible to put him back together again.

最近研究发现,当磁盘空间写满或写入了格式不正确的数据或在操作db过程中内存溢出,那么.db文件的镜像就会被破坏,这种情况下再去执行有关此db的操作,android就会把该db文件删除掉,如果db文件损坏了,可在adb shell下恢复其数据,做法如下:sqlite3 old.db(注:损坏的db文件).output tmp.sql.dump.quit然后读取数据到新的dbsqlite3 new.db.read tmp.sql.quit不过保险起见还是做好db的备份,因为一旦db文件损坏,在未知的情况下再去操作此db,android就会直接把此db给干掉(个人对android的这种做法不太满意)。我也郁闷了很久,看log和源码才知道的。

猜你在找的Sqlite相关文章