The following issue has been CLOSED ====================================================================== http://dbmail.org/mantis/view.php?id=955 ====================================================================== Reported By: waza123 Assigned To: ====================================================================== Project: DBMail Issue ID: 955 Category: Database layer Reproducibility: always Severity: minor Priority: normal Status: closed target: Resolution: reopened Fixed in Version: ====================================================================== Date Submitted: 09-Jan-12 15:50 CET Last Modified: 09-Jan-12 17:09 CET ====================================================================== Summary: SQL error table create Description: CREATE TABLE `dbmail_usermap` ( `login` varchar( 255 ) NOT NULL , `sock_allow` varchar( 255 ) NOT NULL , `sock_deny` varchar( 255 ) NOT NULL , `userid` varchar( 255 ) NOT NULL , UNIQUE KEY `usermap_idx_1` ( `login` , `sock_allow` , `userid` ) ) ENGINE = MYISAM DEFAULT CHARSET = utf8;
MySQL said: Documentation http://dbmail.org/mantis/view.php?id=1071 - Specified key was too long; max key length is 1000 bytes same with dbmail_replycache dbmail_usermap ====================================================================== ---------------------------------------------------------------------- (0003388) paul (administrator) - 09-Jan-12 16:27 http://dbmail.org/mantis/view.php?id=955#c3388 ---------------------------------------------------------------------- MyISAM tables are not supported. ---------------------------------------------------------------------- (0003389) waza123 (reporter) - 09-Jan-12 16:40 http://dbmail.org/mantis/view.php?id=955#c3389 ---------------------------------------------------------------------- are you sure? I'm using them since 2.0 , all works fine. MySAMI is much more stable than InnoDB. Some years ago i was using dbmail with innodb and data center lost electricity, innodb got broken, and there is not any good tool to restore info from innodb. MyISAM has better ability to restore data on crash. ---------------------------------------------------------------------- (0003390) paul (administrator) - 09-Jan-12 17:09 http://dbmail.org/mantis/view.php?id=955#c3390 ---------------------------------------------------------------------- Yes I am sure. You are misinformed. InnoDB recovery is very well documented on the mysql site. http://dev.mysql.com/doc/refman/5.0/en/forcing-innodb-recovery.html Also: on MySQL only InnoDB supports key-restraints and cascaded. Those have been required for proper operations since early in the 2.0 series. Issue History Date Modified Username Field Change ====================================================================== 09-Jan-12 15:50 waza123 New Issue 09-Jan-12 16:27 paul Note Added: 0003388 09-Jan-12 16:28 paul Status new => closed 09-Jan-12 16:28 paul Resolution open => no change required 09-Jan-12 16:36 waza123 Note Added: 0003389 09-Jan-12 16:36 waza123 Status closed => feedback 09-Jan-12 16:36 waza123 Resolution no change required => reopened 09-Jan-12 16:40 waza123 Note Edited: 0003389 09-Jan-12 17:09 paul Note Added: 0003390 09-Jan-12 17:09 paul Status feedback => closed ====================================================================== _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
