Details
-
Bug
-
Resolution: Fixed
-
Low
-
4.3.4
-
4.03
-
Description
With JIRA 4.3+ we require users to use InnoDB storage engine when integrating with MySQL
However, this isn't the default engine for MySQL (MYISAM) also for various reason ppl may not wish to change the default engine to suite our application.
Anyway, this request is completely unnecessary as MySQL allows to define storage_engine as an attribute for a session.
Funny enough other ATL product already use it... Confluence or Bamboo:
http://confluence.atlassian.com/display/BAMBOO/MySQL+5.x
Unaware users will see in fatal errors in their log file:
2011-06-01 23:26:55,334 main ERROR [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following: CREATE INDEX idx_goup_attr_dir_name_lval ON cwd_group_attributes (directory_id, attribute_name, lower_attribute_value) Error was: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes SQL Exception while executing the following: CREATE UNIQUE INDEX uk_group_attr_name_lval ON cwd_group_attributes (group_id, attribute_name, lower_attribute_value)
Currently our configurer (config.sh/bat) does not allow to set this attribute on the connection.
Attachments
Issue Links
- duplicates
-
JRASERVER-24124 MySQL Index Creation Fails With Error "specified key was too long"
- Closed
- is duplicated by
-
JRASERVER-25636 Create MySQL tables using InnoDB engine by default - session variable
- Closed
- was cloned as
-
JRASERVER-25636 Create MySQL tables using InnoDB engine by default - session variable
- Closed