Bug 780717 (SOA-3170)

Summary: MySQL 5.5 - Type=InnoDB has changed to ENGINE=InnoDB
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Ivo Bek <ibek>
Component: Documentation, riftsawAssignee: Julian Coleman <jcoleman>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0 GACC: mbaluch
Target Milestone: ---   
Target Release: 5.2.0 GA, 5.2.0.ER2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3170
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-09 08:35:46 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ivo Bek 2011-07-14 07:13:33 UTC
project_key: SOA

I upgraded system including MySQL to version 5.5 without notice and if I tried to run SOA-P I received this syntax error "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB'". I found that 'TYPE=InnoDB' has been changed to 'ENGINE=InnoDB'. Don't be afraid, 'ENGINE=InnoDB' is supported in previous versions too.
I noticed that It's in deploy/riftsaw.sar/bpel-sql/mysql.sql but It can be somewhere else too.

Comment 1 Douglas Palmer 2011-08-02 10:53:35 UTC
Link: Added: This issue Cloned to RIFTSAW-409


Comment 2 Douglas Palmer 2011-08-02 12:13:13 UTC
Fix is in the RiftSaw 2.3.x branch; will be included in SOA-P 5.2.0.ER2.

Comment 3 David Le Sage 2011-08-29 00:43:36 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3170

Users who upgraded to MySQL version 5.5 and  tried to run SOA-P encountered an error message that stated, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB'". 

This was caused by the fact that 'TYPE=InnoDB' had been changed to 'ENGINE=InnoDB'. To rectify this issue, the BPEL engine has been updated to support the amended syntax.


Comment 4 Marek Baluch 2011-11-04 15:45:23 UTC
Will close as soon as we have the first version of release notes on the doc server,

Comment 5 Len DiMaggio 2011-11-07 18:44:38 UTC
Just to confirm - the bug was fixed in ER2 - the release note should inform users that both the old and new syntax are supported - correct?