[Evolution-users] table sqlite_sequence may not be dropped
Milan Crha
mcrha at redhat.com
Wed Sep 24 14:00:50 UTC 2025
On Wed, 2025-09-24 at 09:58 +0200, Ralf Mardorf via evolution-users
wrote:
> After renaming the files, I started Evolution from the command line,
> and it ran without stderr or stdout messages, but the folder.db files
> were recreated.
Hi,
I won't say "but", but rather "and", in the above sentence :)
It looks like the accounts are very old, according to the timestamps of
the surrounding files at least. It's possible the tables had some
AUTOINCREMENT columns back in those days, then the table had been
carried over from one version to another. The "problem" arose only
because I wanted to clean up the folders.db file and delete "all the
other tables", not realizing there can be some dedicated to the SQLite
itself. The accounts were not visible in the GUI, because their
initialization failed due to this migration failure.
It's taken care of in the sources (3.58.1 material), both skipping this
table and by not making the table/index deletion a fatal error, in case
there would be some other special undeletable table or index.
Thanks for using evo for that long.
Bye,
Milan
More information about the evolution-users
mailing list