Re: [RCD] recipient selection problem

hi,

"2. all my tables were myisam, i updated to innodb"

i found out too, that all my tables were myisam, but roundcube initial database generator sql's are all making innodb.

i upped in a test environment a 0.3.x to 0.4 (on separate db servers) by importing the initial creator scripts in the 0.4 db and then making a backup using phpmyadmin on the old box, without structure data, using extended inserts and no delayed inserts.

So far, it seems okay, but message caching is not used so untested in this case.

On Thu, 19 Aug 2010 17:26:28 +0200, "Raoul Bhatia [IPAX]" r.bhatia@ipax.at wrote:

...

[Native message: Table 'roundcubemail.contactgroups' doesn't exist]

So the DB structure seems to be corrupted, I will modify it per hand.

creating the contactgroups table failed. things i did:

1. all my existing tables were of latin1_swedish_ci collation. i changed

that to utf8.

2. all my tables were myisam, i updated to innodb

3. users.user_id defaults to null. i do not know if the constraint

has been a problem too..

...

CREATE TABLE contactgroups ( contactgroup_id int(10) UNSIGNED NOT NULL AUTO_INCREMENT, user_id int(10) UNSIGNED NOT NULL DEFAULT '0',

users.user_id defaults null. contactgroups.user_id defaults '0'..

...

changed datetime NOT NULL DEFAULT '1000-01-01 00:00:00', del tinyint(1) NOT NULL DEFAULT '0', name varchar(128) NOT NULL DEFAULT '', PRIMARY KEY(contactgroup_id), CONSTRAINT user_id_fk_contactgroups FOREIGN KEY (user_id) REFERENCES users(user_id) ON DELETE CASCADE ON UPDATE CASCADE,

maybe this constraint might be an issue?

i then managed to create the table when ommiting the /*!40000 ENGINE=INNODB */ command and then altered the engine from myisam to innodb.

i also omitted the ENGINE declaration for contactgroupmembers and again altered the engine afterwards.

fyi: i'm running an older mysql 5.0 release.

maybe this will help you in tracking down this issue?

thanks for creating such a great release!

cheers, raoul