Hi Craig, Thanks for the help. Let me see if I understand correctly. 1. our oracle 10g database only supports "read committed", "serializable" and "read only" tranasction isolation levels. 2. on the "write side", issuing an entitymanager.flush(), forces the changes to the database.
my question: "I thought since the underlying database is set to "read-committed", after executing the flush, only connections within the current transaction would be able to read the changes to the database until commit time." Is this correct? Hi Charlie, > > If you're looking for the "write side" of the issue, try issuing an > EntityManager.flush() to force writing changes to the open connection. > Then, any connection with read uncommitted semantics will see the > changes. > > I don't know how to handle the "read side" if you cannot set read > uncommitted on the connection properties. > > Craig > > On Mar 24, 2008, at 3:03 PM, Charlie Walker wrote: > > -- Charlie Walker - Registered Linux User #62358 "Now and then we had a hope that if we lived and were good, God would permit us to be pirates." - Mark Twain
