Kastlunger [users.giulie...@gmail.com]
Sent: Tuesday, October 27, 2015 5:39 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Contacts db issue
Okay, I added the pragma_version; everything seems fine and legit - contacts
show and load faster than before!.
Out of curiosity, which update u
> ----------
>> *From:* devel-boun...@lists.sailfishos.org [
>> devel-boun...@lists.sailfishos.org] on behalf of Tone Kastlunger [
>> users.giulie...@gmail.com]
>> *Sent:* Tuesday, October 27, 2015 5:10 PM
>> *To:* Sailfish OS Developers
>> *Subject:*
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Contacts db issue
Here's what I did:
a) I followed your instructions, this gave me a new database (with imported
contacts) and the integrity errors as per the mail above;
b) I did a
mv contacts.db broken.db;
sqlite3 contacts.db
.r
rivileged shell):
> $ contacts-tool list
>
> Thanks,
> Matt
>
> --
> *From:* devel-boun...@lists.sailfishos.org [
> devel-boun...@lists.sailfishos.org] on behalf of Tone Kastlunger [
> users.giulie...@gmail.com]
> *Sent:* Tuesday, October 27, 2015 5:10 PM
> *To:* Sailfish OS Dev
ailfish OS Developers
Subject: Re: [SailfishDevel] Contacts db issue
Hey Matthew;
thanks for the fast reply!
Here's what I get from the new DB (after having run sqlite3
qtcontacts-sqlite/contacts.db "pragma integrity_check;" on the newly created
db):
[nemo@Jolla Contacts]$
Okay! After doing it from the sqlite3 shell another time, the
integrity_check succeeded on the new file.
Thanks!
On Tue, Oct 27, 2015 at 9:10 AM, Tone Kastlunger
wrote:
> Hey Matthew;
> thanks for the fast reply!
>
> Here's what I get from the new DB (after having run sqlite3
> qtcontacts-sqli
Hey Matthew;
thanks for the fast reply!
Here's what I get from the new DB (after having run sqlite3
qtcontacts-sqlite/contacts.db "pragma integrity_check;" on the newly
created db):
[nemo@Jolla Contacts]$ sqlite3 qtcontacts-sqlite/contacts.db "pragma
integrity_check;"
*** in database main ***
On
Hi Tone.
Yes, it sounds like you have a corrupted contacts database. Any idea how that
might have happened?
In any case, you can try to recreate the database to fix the issue. You need
to do something along the lines of the following (but please sanity-check these
instructions before running
