I have a simple database set up in mysql 5.0 with a couple of foreign keys (i.e. one-to-many relationships). The code generation doesn't seem to be detecting these and it does not generate the appropriate one-to-many mappings. Any ideas?

Thanks,
Scot

edit: I am using mysql 5.0 with a 5.1.6 connector.

1) check that you are using a MySQL storage model that actually supports and reports foreign keys, MyISAM does not - InnoDb does.

2) check that you really are using a jdbc driver that supports foreign keys

Yes, using an Innodb engine. Just to check, I did a SHOW CREATE TABLE in mysql and can see all the foreign keys just fine.

I am also using the latest mysql connector, mysql-connector-java-5.1.6-bin.jar, which is supposed to be able to retrieve foreign key info.

I can only say it works perfectly for me and everyone else who said mysql did not reverse engineer properly and then verified they actually had the right driver and right db type.

The driver seems to be working fine. Using the same driver through an eclipse sql editor, I can see the foreign key constraints without any trouble at all.

What else can I do to verify that I am using the correct database and driver? All of my tables are built with engine=InnoDB explcitely defined and I am using a 5.0 driver from mysql-connector-java-5.0.8-bin.jar. I switched from the earlier 5.1 driver because I know someone who has a working configuration that was using that driver. Either one is very recent and should be good.

Any ideas? I'm really stumped here. If it's not the driver or the database, what else could be causing it to not see my foreign keys?

My database is version 5.0.51a

if you can then submit the simplest SQL schema creation script that you cannot reverse engineer and tell me what you actually do in jira and ill look into it.

Well, I figured out what was going on. I don't understand it. Perhaps you can explain. It all came down to this one property:

<property name="hibernate.connection.url">jdbc:mysql://localhost/custord</property>

If I put the database name in upper case, it will not detect my foreign keys. Like this:

<property name="hibernate.connection.url">jdbc:mysql://localhost/CUSTORD</property>

Something is wrong somewhere. I don't think MySQL is supposed to be case sensitve anymore.

well we just read what the database metadata is telling us.

So looks like mysql is case sensitive in the metadata look ups.

My guess is it's related to this bug which has been open for almost 2 years now.

http://bugs.mysql.com/bug.php?id=21317

I can confirm that there si a problem with the case of the database name.
I had a database named SeamDB and the tools didn´t work with the foreign keys. After renaming the database to seamdb everything worked fine.