Does the primary key have to be the first column in the tabl

mflavell · **Joined:** Tue Jun 20, 2006 12:06 pm **Posts:** 2

Hi there,

just trying to plug hibernate into some legacy tables and have come a bit unstuck with the primary key.

In one of the tables the primary key is the second column in the table. Now when I create the objectname.hbm.xml I have to declare the ID before the property columns. This seems to imply that the primary key (or composite PK) has to be first in the table.

Does anyone know a way around this at all - changing the table is not an option.

Thanks in advance.
Cheers,
Maggie.

cscashby · **Posted:** Tue Jun 20, 2006 1:05 pm

mflavell wrote:

<snip>
In one of the tables the primary key is the second column in the table. Now when I create the objectname.hbm.xml I have to declare the ID before the property columns. This seems to imply that the primary key (or composite PK) has to be first in the table.

Does anyone know a way around this at all - changing the table is not an option.

There's absolutely no requirement that columns are in the same order in the database; in fact SQL doesn't specify column / fields ordering either.

Try it and see - it should work just fine as long as the column names are correct!

Christian Ashby

mflavell · **Joined:** Tue Jun 20, 2006 12:06 pm **Posts:** 2

Cool, thanks for that.

I hadn't tried with the existing database, just used a new one for testing that was created from the xxx.hbm.xml files hence I thought there was a problem.

Cheers,
Maggie.

cscashby · **Posted:** Wed Jun 21, 2006 5:21 am

Thanks! Please don't forget to rate!