When I map a class hierarchy with the table-per-class hierarchy mapping, a discriminator column is created as the first column in the table definition that Hibernate creates. Is there a way to make the primary key (ID field in the Abstract entity class) be the first column, and the discriminator column the second column. This is purely aesthetic, having no impact on the function. Thanks for a wonderfully useful project!

Well, it can be easily placed in the beginning or in the end, but I don't want to have it in the end.
Placing it in between is much harder. Does it worth it? I believe it does not :)

No it isn't a big problem. I'm just used to seeing primary keys as the first column. Some dbs (like MySQL - I think) have the ability to change the natural ordering of the columns, so it could be possible in those cases to have an additional table alter command to come behind the create statement to adjust column ordering. But it's probably not widely enough supported operation to merit a Hibernate feature request. Thanks for confirming at least that it isn't currently implemented.