HibernateTools 3.2.0.beta9a

When I use hibernate-tools hbm2ddl to create ddl from hbm.xml files, fields in the resulting "create tables" DDL are in a consistent order from invocation to invocation. When I create ddl from JPA-annotated classes, the fields seem to be emitted in random order. This causes "svn diff" to report spurious differences where there are none, making it difficult to detect whenthe schema has changed.

Is there a way to cause hbm2ddl to emit fields in a predictable order?

Thanks!

This is because JPA uses the order the vm returns the properties/methods.

I seem to recall that emmanuel added or want to add something that makes this more predictable.

But making it exactly the same as what hbm.xml's would do I guess is not really possible.

I'll ping emmanuel to let him comment on this one.

Making it the same as hbm.xml order is not a requirement for me - but making JPA emit predictable order vs. a previous invocation of itself would be very desirable. Even just a simple lexical sort of the field names would solve my problem (comparing one DDL script with an earlier one).

It is a lexical order starting with Hibernate Annotations 3.3.0. I had to do that because the VM does not guarantee the order when reading methods and fields from a class.

When can we expect a version of hibernate-tools to include annotations 3.3.0? I just tested tools 3.2.0-beta11 and it still uses annotations 3.2.1.GA.

you should be able to put in hibernate-anntations 3.3.0 into hibernate tools and it should work - if not then please let me know.

I realize this thread is long dead, but I would like to ask again.

At the time Max replied, I tested the 3.3.0.GA annotations jar and did not see success. I thought perhaps it was a configuration error on my part, and since this was not a vital requirement for my project, I put it aside.

It has now become more important (the DBA at my customer is complaining about diff'ing DDL scripts :))

I've now updated to hibernate-tools 3.2.0.GA (which includes hibernate-annotations-3.3.0.GA). I still see the same unsorted behavior. For example, here's the result of regenerating the schema after making a simple name change in a different table's field (via @JoinColumn(name="new_name")):



(the diff has hundreds of these sorts of changes -- both the original and new ddl were created with the same hibernate-tools version and the only change between each DDL is a single field name change on an unrelated table.

I don't know what else to try. Here's the hiberanate.cfg.xml I'm using when running the ant task. Is there something missing in here that would cause the annotations code to sort my properties?



Thanks for any advice!

you will need to take a deep dive in to the code to figure out why this is happening....or create a test case that illustrates the behavior and report it against hibernate annotations or hibernate core (or in the unlikely case it is hibernate tools doing some weird sorting)