I do not want to use the primary key of my user table to reference a row from a user interface.

So I wanted to add a public_id column generated (from an oracle sequence) on create, never updated, unique, non-nullable. However @Generated may only be used on @Id columns (http://opensource.atlassian.com/project ... e/HHH-2907).

I've seen someone offer the workaround of a one-to-one relationship. I can create a public_id to user_id join table with the public_id as @Id,@Generated and put a one-to-one inside the user table. If I then add a non-insert, non-update property while keeping the one-to-one lazy, I can fetch without the overhead of an additional join. However, non-nullability and foreign-key constraints are an issue at creation time. Which comes first, the map table or the user table and how do you enforce data integrity without creating them both at the same time (non-nullability constraint)?

Does anyone know of any way to do this with hibernate?

Hmmm... the examples at http://docs.jboss.org/hibernate/stable/ ... ml#d0e2322 shows @Generated being used with a String column. I have not used it, so maybe there is an issue with it. The HHH-2907 seems to consider properties that are generated by something else than the database.

I have to use SQL for this. Otherwise I'd setup a database-side trigger to insert the the sequence into public_id on insert. If I could do that, I would just turn insert and update to false and use it like a regular property.

Maybe I am missing something, but doesn't "public_id column generated (from an oracle sequence)" mean that the value is assigned automatically by the database? Or does it only work for primary key columns?

Hmmm... I searched the net and realized that I was missing something. The value is not automatically generated. But... maybe you can map your class using a custom <sql-insert> statement. This could include something like:



See http://docs.jboss.org/hibernate/stable/ ... erysql-cud for some more examples. The drawback is reduced portability and that you have to make sure that the SQL matches what Hibernate expects.