Sorry.  Ok so I'll read a little slower next time.

Now that you've explained it, how would it work to use database RI
underneath an EJB application.  If the bean is in memory but disappears from
the database that isn't all that good.  If he's using commit option C, then
next client to reference the bean will get what?  Object does not exist when
they try to execute a method on the bean?

Cheers

-----Original Message-----
From: danch (Dan Christopherson) [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 15, 2001 1:38 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] ejbStore() delay seems to be a serious problem


He's not removing the modified bean: he's removing a bean that the 
modified bean used to refer to. The issue is that the remove causes a 
data change immediately, while the table behind the modified bean still 
has the foreign key for the row that's being removed. This violates 
referential integrity - boom!

<snip>

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to