session « Key « JPA Q&A

  1. JPA Q&A
  2. Key
  3. session




1. does a table need primary key to participate in hibernate session?    coderanch.com

It is sort of possible but ill advised. This gets asked a lot in these forums so have a search for a more complete answer, but basically an entity in a relational database that does not have a unique identifier is not able to participate in relationships so is (by definition) not relational data. And you can't expect any tool whose ...

2. Non-explicit primary keys across sessions    forum.hibernate.org

Hi there, This is my first post to the Hibernate forums - I'm a big fan of the architecture (I worked on another persistence framework that could have been a kissing cousin of Hibernate). Here is my inaugural question. I have an application framework that I am integrating Hibernate with. One of the features of this framework is the fact that ...

3. session.get(clazz, key) returns Proxy?    forum.hibernate.org

Hibernate version: 2.1.6 I call session.get(clazz, key) and in one case the proxy is returned and in another the persistent object. After studying "Hibernate in Action" I still don't have a clue, why in one case the proxy is returned and in the other case the persistent object. The proxy is an interface and my persistent object implements this interface. Since ...

4. Urgent: Session unusable after unique key constr. violation    forum.hibernate.org

Beginner Joined: Mon Nov 22, 2004 11:21 am Posts: 42 Hello, I need urgently some advice, please help. I have an unique constraint defined on column Directorynumber in table Keydirectory. The app uses a dialog to create new Keydirectories. When I try to insert a new Keydirectory with an already existing Directorynumber (upon pressing the accept or the ok button), I ...

5. auto-increment key returns the same value across sessions    forum.hibernate.org

6. Session.save() not returning true primary key value.    forum.hibernate.org

Hi friends, In our database whenever we add a new record using session.save() it returns a wrong primary key. After successful insertion of record in Database actual primary key assigned to the record is different form the one which is returned by session.save(Object) method call. On addition to that to our surprize database table doesn't have any record for the value ...