Entity Dependants & writable entities

Question

[att1.html]

Answer 1

In 7.0, CMR would be the most efficient route since it can read the bean
and its relation in one db round-trip.
If you want some more ideas, you'll have to answer my other questions in
the previous post.
-- Rob
"DAGHFAL Carole(LB Soft)" wrote:
I know that CMR works in this case but I'm searching for a solution
that minimize database round-trips and optimize performance!
For that I'm trying to avoid using CMRs by implementing the concept of
dependencies .
Rob Woollen wrote:
"DAGHFAL Carole(LB Soft)" wrote:
Hi all,
I have the Operation table in the database that has the operationId
as Primary Key ,this table is linked to another table called
OperationNormal by the operationId
For the Operation table I need to get the corresponding data from
the OperationNormal table.
In this case i had created the Operation as my Entity and the
OperationNormal as dependant class and get
the corresponding data using SQL statements in ejbLoad of
Operation.Is the Operation entity CMP or BMP? Do you want to load the
Operation and OperationNormal in one SQL Join?
But once I had to add a record in the operation table I should add
a corresponding one in the OperationNormal table.Yes, it sounds like you'll have to insert into the OperationNormal
table after you've done the operation insert.
Should I create two writable entities one OperationWrite and the
other OperationNormalWrite to be able to write into the two tables
?Are the Operation and OperationNormal beans read-only?
In this case I would use the dependant class only to read the data
from the OperationNormal table and the OperationNormalWrite to be
able to write to the OperationNormal table.
Or Should I implement the two tables as 2 entities with CMR
relation between them and forget about the dependant class????CMR would work fine in this case as well.
-- Rob
>
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com
[att1.html]