entity A or B,A:B=1:N(one2many)

every runs ok,but when i change the primary key of entity B,the jbuilder9t tell me the error:net.sf.hibernate.HibernateException: identifier of an instance of com.one2many.Publication altered from publication NO1111 to NO2222

at net.sf.hibernate.impl.SessionImpl.checkId(SessionImpl.java:2524)

at net.sf.hibernate.impl.SessionImpl.flushEntity(SessionImpl.java:2347)

at net.sf.hibernate.impl.SessionImpl.flushEntities(SessionImpl.java:2340)

at net.sf.hibernate.impl.SessionImpl.flushEverything(SessionImpl.java:2207)

at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2186)

at net.sf.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:61)

at com.one2many.hibernateupdate.main(hibernateupdate.java:73)

i just want when i change the primary key of b,the primary key of a is also changed by the code i write in the jbuilder9!!


Does my option change the primary key of some entity is total wrong!!!!

Primary key must not have more meaning than identity and you never need to change it.

the docment of hiernate always say : the primary key of the entity must not have any operation meaning,but at my viewpoint,i want integrat many,many operation meaning to the primary key.

why i like do this is because the primary key that have operation meaning is very facility!!! at the past project,i always like use the primary key that contains a lot of operation meaning.

I DO NOT understand why the hibernate advocate the meaningless primary key??
I DO NOT understand!!!

never need to change it???
Does this viewpoint is the very strict rule to the programmer?

It is not for hibernate, primiry key must meaningless for any database in theory, meaning can change if key has more meaning than identity, so you can loose the main meaning, identity.

See http://opensource.atlassian.com/project ... key=HB-817 for a (partial) solution for updatable primary keys

Primary key update is a poor DB schema design symptom, ask DBA before to do it.