UPDATE after INSERT in CMR

[mkyaj]

Hi,

To put my problem with an example i have a CMR USER(1) -ADDRESS(m).
When i create an User, it will create the corresponding Addresses(say 3 different addresses for this instance) also.
It is calling
INSERT INTO ADDRESS(field1,field2,USER_FK) VALUES(?,?,?).
INSERT INTO ADDRESS(field1,field2,USER_FK) VALUES(?,?,?).
INSERT INTO ADDRESS(field1,field2,USER_FK) VALUES(?,?,?).

and after that it is again calling
UPDATE ADDRESS set USER_FK=? WHERE ID=?
UPDATE ADDRESS set USER_FK=? WHERE ID=?
UPDATE ADDRESS set USER_FK=? WHERE ID=?

How to stop updating immediately after creation?

Murali.

[mkotsbak]

Did you find any solution to this? We have the same problem with postgres, which is fast to run the INSERT statements, but takes many seconds for each UPDATE statement...

[mkotsbak]

Did you find any solution to this? We have the same problem with postgres, which is fast to run the INSERT statements, but takes many seconds for each UPDATE statement...

[aloubyansky]

<insert-after-ejb-post-create>true</insert-after-ejb-post-create>

[mkotsbak]

"loubyansky" wrote:

<insert-after-ejb-post-create>true</insert-after-ejb-post-create>

Thanks. I actually found this myself also, and it actually works :-) It speeds up our code >60X!.

Why isn't this the default?

[aloubyansky]

Because the spec says insert after ejbCreate and before ejbPostCreate.