SQL syntax error in table creation statements

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Drop all fakedata2 tables
2. Start SnoFyre with option create tables on
3. Examine schema contents

What is the expected output? 

Lots of tables, recreated

What do you see instead?

Not tables, and a load of mySQL syntax errors in the logfile

Table create statements have 'type=myisam' argument, instead of 
'engine=myisam'. Older 'type=' format is deprecated from mySQL 4.1 and no 
longer works at all in current 5.5

Original issue reported on code.google.com by jeremy.r...@googlemail.com on 20 Jan 2011 at 3:10

[GoogleCodeExporter]

Grrr.... alright I've had to create a custom MySQL5MyISAMDialect for this! I'll 
be a Hibernate whiz soon! 

Apply patch and change line #15 in fakedata-db.properties 
from 
hibernate.dialect=org.hibernate.dialect.MySQLMyISAMDialect 
to
hibernate.dialect=uk.nhs.cfh.dsp.snomed.persistence.orm.MySQL5MyISAMDialect
Try dropping fakedata2 schema and recreating all tables the usual way

Original comment by jay.kola on 20 Jan 2011 at 8:00

• Changed state: Fixed

Attachments:

• uk.nhs.cfh.dsp.snomed.persistence.jar

[GoogleCodeExporter]

Confirm fixed: SnoFyre over MySQL 5.5 with (now standard) InnoDB as default 
table creation strategy actually creates MyISAM tables, as directed by SnoFyre.

Original comment by jeremy.r...@googlemail.com on 20 Jan 2011 at 8:31

[GoogleCodeExporter]

@jay.kola thx for this patch for MySQL 5.5

Original comment by seba.wag...@gmail.com on 7 Mar 2011 at 10:06

[GoogleCodeExporter]

@seba - The patch should already be included in the latest version of Snofyre 
available via TRUD. Using the jar from here might lead to issues with the OSGi 
dependency resolution... Also check out the post of Snofyre Users Group for 
other MySQL version 5.5 related info.

Original comment by jay.k...@biomedicalontologies.com on 7 Mar 2011 at 5:11