delete « Field « JPA Q&A

1. How to delete Hibernate @Embeddables containing nullable fields? stackoverflow.com

When deleting an @Embeddable object, I run into some problems. I have the following domain classes: SwitchVoipTrunkGroup and PrioritizedCodec. The latter contains several fields that are nullable.

class SwitchVoipTrunkGroup {

    ...

2. Attempt to Delete causes Update with Null on non null field forum.hibernate.org

Okay I'm sure I'm doing it wrong, but I can't figure out what the right way is. Everything I have tried (short of having no object associations) is causing update statements instead of deletes. I have the following mappings: Code:

3. Delete causes updating not-null fields to null forum.hibernate.org

Hi, I am trying to delete an object which has collection of child objects. The main object has some not null fields that Hibernate tries to update to null before delete. This causes error: SEVERE: Could not synchronize database state with session java.sql.BatchUpdateException: ORA-01407: cannot update ("MYPROJECT"."USER_VIEWS"."NAME") to NULL. I have seen a very similar posting where the answer was to ...

4. Refresh the objects if the db field was updated/deleted forum.hibernate.org

Hello! Does someone know, how to refresh the objects,if i deleted,or update the object in the database? e.g. i call a contactlist of my user " test", there's a contact called "myfriend" with user.getContacts() now in a query, i delete or update the contact "myfriend" if i take a look at my "test" user, the contact "myfriend" still exist or the ...

5. problem deleting with only id field. forum.hibernate.org

hibernate 3.0.5 I'm having problems deleting entities. I have a dao layer in which I pass in the ID only and not the class. This is done mainly so that I don't have to take a round trip to the db if I receive just an ID from the client tier. So I don't want to have to call the dao ...

6. replacing delete with timestamp of a delete field forum.hibernate.org

I'd like to implement a replacement for delete. It does everything exactly as delete does, but instead of actually deleting the record (and all of its cascades), it just puts a current timestamp in a field (that is in all my tables) called "deleted". All my persistent objects derive from a single AbstractPersistentObject and this AbstractPersistentObject has a field that maps ...