Content of akonadiserver.error: DATABASE ERROR: Error code: 42601 DB error: "FEHLER: Syntaxfehler bei \u00BB(\u00AB\nZEILE 1: EXECUTE (TRUE, TRUE, 1)\n ^\n(42601)" Error text: "FEHLER: Syntaxfehler bei \u00BB(\u00AB\nZEILE 1: EXECUTE (TRUE, TRUE, 1)\n ^\n(42601) QPSQL: Es konnte keine Abfrage erzeugt werden" Query: "SELECT CollectionTable.id, CollectionTable.remoteId, CollectionTable.remoteRevision, CollectionTable.name, CollectionTable.parentId, CollectionTable.resourceId, CollectionTable.enabled, CollectionTable.syncPref, CollectionTable.displayPref, CollectionTable.indexPref, CollectionTable.referenced, CollectionTable.cachePolicyInherit, CollectionTable.cachePolicyCheckInterval, CollectionTable.cachePolicyCacheTimeout, CollectionTable.cachePolicySyncOnDemand, CollectionTable.cachePolicyLocalParts, CollectionTable.queryString, CollectionTable.queryAttributes, CollectionTable.queryCollections, CollectionTable.isVirtual FROM CollectionTable LEFT JOIN CollectionMimeTypeRelation ON ( Collection_id = CollectionTable.id ) WHERE ( ( CollectionTable.enabled = :0 OR CollectionTable.referenced = :1 ) AND MimeType_id IN ( :2 ) ) GROUP BY CollectionTable.id" DATABASE ERROR: Error code: 23505 DB error: "FEHLER: doppelter Schl\u00FCsselwert verletzt Unique-Constraint \u00BBcollectiontable_parentandnameindex\u00AB\n(23505)" Error text: "FEHLER: doppelter Schl\u00FCsselwert verletzt Unique-Constraint \u00BBcollectiontable_parentandnameindex\u00AB\n(23505) QPSQL: Es konnte keine Abfrage erzeugt werden" Query: "INSERT INTO CollectionTable (name, parentId, resourceId, queryString, queryAttributes, queryCollections, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6) RETURNING id" I tested the sql script against postgresql with pgadmin, grouping is not correct. There is no aggregation or something else you need ' group by ' statement for. Using arch linux x64 with akonadi 15.08,1-1. Reproducible: Always Steps to Reproduce: 1. start akonadi server with external postgresql database (same database does work with kde 14.x)
Hi, what version of postgresql are you testing against?
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.