The problem with the schemaupdate on "update" is that it will try to alter table and add foreign key constraints that are already there. Saw in another thread that it also does this for indexes. I don't think schemaupdate should try to add things to a column that already exists.

I get this every single time using HSQLDB:
SEVERE: Column types do not match in statement [alter table usersys_User add constraint FK42F982E8D1B foreign key (id) references consys_Contact]

And when it does this in mysql, you get mysql complaining about reaching it's maximum.

What do you think about it not trying to do this type of thing if the column that it is trying to do it on already exists?
[/code]

The mysql problem is fixed in CVS, and we don't care about ignoring some exceptions about already existing constraints.

Awesome, so that'll be in next release?