Custom Cascades?

andreas_eriksson · **Posted:** Wed Dec 10, 2003 6:48 am

Hi, is there any smart way to customize the cascades in Hibernate?

Consider the following object graph:

Code:

Table1 ---* Table2 *--- Table3
             |
             *
           Table4
             *
             |
           Table5

I'd like to have the following cascades:

Code:

* If a row in Table1 gets deleted, all related rows in Table2 should be
  deleted and the related rows in Table3 IF NOT those rows are related
  to other Table1 rows through Table2.

* If a row in Table3 gets deleted, all related rows in Table2 should be
  deleted and related rows in Table4. Related rows in Table5 should be
  deleted IF NOT the're related to some other Table3 row through Table4.

Could someone give me a hint?

Kind regards, Andreas

themax · **Posted:** Wed Dec 10, 2003 9:41 am

A database trigger would definitely allow u to code that.. assuming your DBMS supports triggers....

andreas_eriksson · **Posted:** Wed Dec 10, 2003 11:15 am

Thanks for the respons!

Not "allowed" to use triggers or stored procedures.

Kind regards, Andreas

themax · **Posted:** Wed Dec 10, 2003 11:21 am

Ouch.. From what the manual says about cascades in Hibernate, I'd say you don't have a way to do this right now then..

Quote:

cascade="all|none|save-update|delete"

emmanuel · **Posted:** Wed Dec 10, 2003 11:27 am

Have a look at interceptor, might help.

gavin · **Posted:** Wed Dec 10, 2003 11:38 am

Not Interceptor, but Lifecycle.

andreas_eriksson · **Posted:** Wed Dec 10, 2003 11:48 am

Lifecycle, ok thanks!

Kind regards, Andreas

andreas_eriksson · **Posted:** Wed Dec 10, 2003 2:16 pm

Well, while I was searching this forum on 'Lifecycle' I found a post where Gavin said:

I don't use Lifecycle. I think it was a mistake. Its one of the very few things I just ripped unthinkingly from other ORM solutions back in the dim dark days.....

Is there another way of making the special cascades I'd like?

Seems like I bind my VO's to be only Hibernate VO's by implementing Lifecycle interface.

Another thing is; how can a Table3 VO tell that it's "parent" row in Table1, who's getting deleted, is the only one associated with the object?

Kind regards, Andreas

andreas_eriksson · **Posted:** Thu Dec 11, 2003 5:27 am

Pushing it up....