Hi! I would strongly recommend you not to mix persistence mechanism within a transaction. Either get around with CMP only, or use bached prepared statements (updateBatch) to gain the same performance advantage as you get from CMP.
If you need a quick-and-dirty solution, that may not work with later releases of WebLogic, sending a dummy EJB QL statement after the last CMP update. In order to deliver a consistent search result (cache vs db), WebLogic flushes CMP changes to the database before executing the sql generated from the EJB QL. /johan Den 03-06-16 21.07, skrev "Dongmei Cao" <[EMAIL PROTECTED]>: > Hi, > > I have a question, which is somewhat WebLogic 7 specific. If anyone > has any suggestions, it is highly appriciated! > > I have a transaction. In the first half, I use CMP beans to insert/update > data to database. After all the data are inserted/updated, I use SQL > directly to make a copy of the data. The problem I noticed is that some of the > data are not copied. I think what is going on is that the update happened > at the end of the transaction so that the the SQL copy couldn't pick > up some of the data. I have the "delay-updates-until-end-of-tx" set to true. > I can not really set it to false becuase it's going to cause lots of > other problems. My question is that whether there is a way to > flush the cached data into database manually. > > Thanks, > Dongmei Cao > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
