To: sqlite-users@sqlite.org
Subject: EXTERNAL:[sqlite] Vacuum'ing database returns a 'PRIMARY KEY must be
unique' error in 3.7.0
I decided to vacuum my places.sqlite database (used by Firefox to
store its history and bookmarks) and got a primary key violation.
The database passes the analyzer and dumper
I decided to vacuum my places.sqlite database (used by Firefox to
store its history and bookmarks) and got a primary key violation.
The database passes the analyzer and dumper with no errors. select
count(*) from the different tables also shows no errors.
However, a dump and attempted restore
Hi,
If this is a production system? Then I'd do the following:
1. Make a backup.
2. Run Vacuum manually.
I would automate this as part of a periodic maintenance schedule,
(weekly/bi-weekly etc..)
This is given then number of bugs and issues with DB corruption when
3 matches
Mail list logo