How do I have to setup an EntityBean if a foreign key is referenced by a CASCADE ?

Thread View: comp.lang.java.programmer

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Arnold Peters Tue, 05 Oct 2004 19:10

#270

Author: Arnold Peters
Date: Tue, 05 Oct 2004 19:10

22 lines
2243 bytes

Assume I defined (at least) two SQL tables. The first table contains a foreign key of the second.
The primary key of the second table is defined similar to

CREATE TABLE ..... 
ADD FOREIGN KEY(customer_id) REFERENCES customer (customer_id) ON DELETE CASCADE;

Pay attention to the "DELETE CASCADE". Thus if I delete a record of the second table
automatically the referenced record in the first table is deleted as well.

Ok, now I define for each of the tables (resp. possible records) an EntityBean.

What do I have to change in the setup/coding of each of the two EntityBeans in order
to treat the foreign key REFERENCE correctly?

Do I really have to do nothing more?

That would mean an EntityBean would recognize the reference by itself without help.
I cannot believe that.

Does someone have an experience with that scenario?

Arnold

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads