Bug 880544 - Declare InnoDB as default MySQL engine in schema generation scripts
Summary: Declare InnoDB as default MySQL engine in schema generation scripts
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-27 09:50 UTC by Martin Weiler
Modified: 2021-10-15 11:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Task
Embargoed:

Attachments (Terms of Use)

Description Martin Weiler 2012-11-27 09:50:49 UTC 
Description of problem:
If MySQL is configured with MYISAM as default engine, the tables in the SOA-P schema will be mixed, as not all components explicitly declare the engine type in the schema creation scripts:

* jBPM -> InnoDB
* BPEL -> InnoDB
* jUDDI -> MYISAM (not defined)

In addition, jUDDI won't deploy as at least one of the tables is hitting the MYISAM restriction of 1000 bytes for keys:

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes

All MySQL schema generation scripts inside the platform should declare the engine type.
Note You need to log in before you can comment on or make changes to this bug.