Guys,

You are assuming CMP only. But how about BMP? If someone wants to implement a 
timestamp or rowversion in his table and "reuse" the instance under Option B, the 
current JBoss 2.4.4 implementation would not be able to support it.

Henri

-----Original Message-----
From: marc fleury [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 12:44 AM
To: Dain Sundstrom
Cc: Henri Chen; [EMAIL PROTECTED]; Bill Burke
Subject: RE: [JBoss-dev] RE: Bug in
EntityMultiInstanceSynchronizationInterceptor.java ?


|I agree, but the problem is that there is very little we can reuse.  We
|have to throw out all cached data, because we currently have no way to
|verify if it is still in sync with the database.

that is correct, and as you state a timestamp or incremented field as a
default for tables we create would make a lot of sense.

This is for the 3.11 for workgroups version... for 3.0 final it will be like
the 2.4 codebase and basta. Let's get this puppy out of the door.

marcf
[¢Ëz÷¥¢™žžÙšŠX§‚X¬´–è²Ç^½éh¦g§¶X¬¶Ë(º·~Šàzw­†Ûi³ÿåŠËl²‹«qçè®§zßåŠËlþX¬¶)ߣøÛ¢Ëz÷¥¢™žž


Reply via email to