Hibernate version: 2.1.8

Name and version of the database you are using: MySQL 4.1.9

Typical schemaexport SQL:

alter table XXXX drop foreign key YYY;
...
drop table XXXX if exists;
...
create table XXXX ....

In 2.1.6 schemaexport didn't create the alter table statements. Now it does. If schemaexport is run against an empty database the attempt to alter a table that does not exist unsurprisingly causes a "table does not exist" error.

Have I missed a new configuration option?

Rych

Use MySQLMyISAMDialect.

Oh, oops, that is HB3.


Just ignore the extra alter tables. They don't hurt. SchemaExport is designed to not stop when a failure occurs.

(Otherwise, you can create a custom dialect for MyISAM, just like in HB3.)

I can, of course, manually edit the generated SQL to delete the alter statements but that kind of blows the automatic build process we have ;-)

Rych

Oh, and I'm using the InnoDB engine too....

Then the alter table statements should be correct.

Syntactically they are but MySQL/InnoDB complains if you try to "alter table .. drop foreign key..." on a table that does not exist. There isn't an equivalent "if exists" statement extension that can be added in the same way as "drop table ..." uses it. The error reported by MySQL seems reasonable to me. I have no knowledge of whether other database engines permit you to alter tables that don't exist.

On the same topic, I'm having trouble getting SchemaExport to create InnoDB tables, due to the addition of the "alter table" & "drop table" statements.

The method suggested in the FAQ (setting delim = "type=InnoDB;") doesn't work anymore. Output such as the following is generated:

This is broken syntax.

Apart from configuring the MySQL server to create all tables as InnoDB, is there any other workaround to creating InnoDB tables for the Hibernate entities?