Bug 384024 - [17.08] Akonadi server fails to start with sqlite backend
Summary: [17.08] Akonadi server fails to start with sqlite backend
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: server (show other bugs)
Version: 5.5.3
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-25 20:29 UTC by Daimonion
Modified: 2017-08-26 10:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 5.6.1


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daimonion 2017-08-25 20:29:36 UTC
After upgrade to 17.08 (Arch linux, both of my installations) akonadi server refuses to start with configured sqlite backend:

```
% Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QSqlDatabasePrivate::removeDatabase: connection 'initConnection' is still in use, all queries will cease to work.
org.kde.pim.akonadiserver: DBUpdater: query error: "near \"DROP\": syntax error Unable to execute statement" " "
org.kde.pim.akonadiserver: Query was:  "ALTER TABLE PartTable DROP COLUMN external;"
org.kde.pim.akonadiserver: Target version was:  35
org.kde.pim.akonadiserver: Mandatory:  true
org.kde.pim.akonadiserver: Failed to commit transaction for database update
org.kde.pim.akonadiserver: Unable to initialize database.
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally...
```

My ~/.config/akonadi/akonadiserverrc file contains:

```
[Debug]
Tracer=null

[%General]
Driver=QSQLITE3

[QSQLITE3]
Name=/home/username/.local/share/akonadi/akonadi.db

```
Comment 1 Daniel Vrátil 2017-08-26 10:05:56 UTC
Git commit 2fcd7c4c4f6cc512de9d7778ab67d637934e7638 by Daniel Vrátil.
Committed on 26/08/2017 at 10:04.
Pushed by dvratil into branch 'Applications/17.08'.

Fix SQLite DB schema upgrade to version 35

SQLite does not support DROP COLUMN and our upgrade language is not
expressive enough to handle that in another way, so for now we just
leave the 'external' column in PartTable on SQLite, it will simply
be ignored. On other backends the column is removed as expected.
FIXED-IN: 5.6.1

M  +2    -1    src/server/storage/dbupdate.xml

https://commits.kde.org/akonadi/2fcd7c4c4f6cc512de9d7778ab67d637934e7638