Hi there,
Previously I'd managed to get RC0.1 to work with postgres, this morning I thought I'd try out the latest from CVS, I checked it out into a separate directory and tweaked the config files to point at proper mail and database servers, sharing the same database as RC0.1 but now using pear::mdb2 instead of pear::db
It essentially works, without having to do any of the tweaks I previosuly needed for postgres, but when on the message list page I get the following errors
DB Error in /var/www/roundcubecvs/roundcubemail/program/include/rcube_mdb2.inc (164):
MDB2 Error: constraint violation DB Error in /var/www/roundcubecvs/roundcubemail/program/include/rcube_mdb2.inc (256):
MDB2 Error: constraint violation Query: INSERT INTO cache (created, user_id, session_id, cache_key, data) VALUES (now(), ?, ?, ?, ?)
I couldn't see any changes to the cache table, it seems that between the value parameters passed to the insert statement and the table defaults all columns are being provided with a value, the only other constraint I can see is the reference to the session table, did I miss something else?
Andy Burns wrote:
Sorry to list mods, previous reply was from "wrong" account ...
I couldn't see any changes to the cache table, it seems that between the value parameters passed to the insert statement and the table defaults all columns are being provided with a value, the only other constraint I can see is the reference to the session table, did I miss something else?
I decided to clean out the cache and session tables to see if that helped, it didn't fix the error, but it allowed me to see that there are no entries being added to the session table when a user logs in, so presumably that explains the constraint error ...
I've installed/upgraded my pear components to have MDB2beta6 and that hasn't helped, I now notice that many (all?) of the save operarations when editing preferences/addressbook give the error
Fatal error: Call to undefined function: affectedrows() in /var/www/roundcubecvs/roundcubemail/program/include/rcube_mdb2.inc on line 189
Does that shed any more light?
Andy Burns wrote:
I couldn't see any changes to the cache table, it seems that between the value parameters passed to the insert statement and the table defaults all columns are being provided with a value, the only other constraint I can see is the reference to the session table, did I miss something else?
I decided to clean out the cache and session tables to see if that helped, it didn't fix the error, but it allowed me to see that there are no entries being added to the session table when a user logs in, so presumably that explains the constraint error ...