6.0.0-alpha12
6/12/25

[#13311] install error when MyISAM
Summary install error when MyISAM
Queue Horde Groupware Webmail Edition
Queue Version 5.1.4
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester nethubonline (at) gmail (dot) com
Created 07/02/2014 (3998 days ago)
Due
Updated 01/20/2016 (3431 days ago)
Assigned
Resolved 01/20/2016 (3431 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
01/20/2016 02:05:58 PM Jan Schneider Comment #3
State ⇒ Not A Bug
Reply to this comment
See the MySQL bug referenced from the mailing list post that you 
linked to. This is an arbitrary limitation set by MySQL developers and 
breaking a huge bunch of code. Use a different DB, a different storage 
engine, or a different collation.
07/02/2014 10:19:52 AM nethubonline (at) gmail (dot) com Comment #2 Reply to this comment
I just tested  and confirmed problem exists also in version 5.2.0RC2
07/02/2014 08:40:47 AM nethubonline (at) gmail (dot) com Comment #1
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Groupware Webmail Edition
Summary ⇒ install error when MyISAM
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
Actually the Horde Groupware Webmail Edition I am testing is 5.1.6, 
but not 5.1.4


When MySQL starting with "skip-innodb" and only uses MyISAM, 
webmail-install would generate the error below:

Fatal Error:
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key 
was too long; max key length is 1000 bytes
In /usr/share/psa-pear/pear/php/Horde/Db/Adapter/Pdo/Base.php on line 201


From the MySQL query log, I can know that the last query which cause 
the problem:
CREATE  INDEX `index_horde_dav_objects_on_id_external` ON 
`horde_dav_objects` (`id_external`)

If innodb is enabled, there is no problem for the installation.

In Horde website, I can't find any info about innodb is required or 
not, so I expect Horde supports both MyISAM and InnoDB. So above error 
should be avoid for MyISAM DB?


I found it was reported before, however I think the solution of it 
(Changing to latin1) is not a final solution and not suitable for all 
Horde users.
http://lists.horde.org/archives/horde/Week-of-Mon-20140217/050689.html

Saved Queries