| 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 (4001 days ago) |
| Due | |
| Updated | 01/20/2016 (3434 days ago) |
| Assigned | |
| Resolved | 01/20/2016 (3434 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
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.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Groupware Webmail Edition
Summary ⇒ install error when MyISAM
Type ⇒ Bug
State ⇒ Unconfirmed
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