On 30 Jul 2013, at 5:04am, techi eth wrote:
>> Could be many rows in many tables were corrupted. If SQLite3 knew exactly
>> what had >been corrupted it could just go and fix it without even needing
>> your help.
>
> Here i am thinking of getting details about table & infected
> row,SQLite3 doe
Many Thanks for comment.
I shall agree with your view.
>Could be many rows in many tables were corrupted. If SQLite3 knew exactly
what had >been corrupted it could just go and fix it without even needing
your help.
Here i am thinking of getting details about table & infected
row,SQLite3 doesn't
On 29 Jul 2013, at 10:21am, techi eth wrote:
> Reference from below link gave me hint about integrity check failure case
> recovery by Export/Import of database.
>
> Please let me know is this is correct & way to handle integrity failure
> check.
This is not the correct way to handle integrity
Reference from below link gave me hint about integrity check failure case
recovery by Export/Import of database.
Please let me know is this is correct & way to handle integrity failure
check.
http://blog.niklasottosson.com/?p=852
http://community.spiceworks.com/how_to/show/1468-how-to-fix-corrup
4 matches
Mail list logo