Hmm it's either mysql or microsoft sql server... However if they supported that feature, how would you suggest I procedede.. Calling em.flush or? Anyhow I guess I could call em.flush, instead of refreshing every object retrieved from the em.
However calling it when it's only relevant would be a lot more performant.. 2010/6/7 Miłosz <[email protected]>: > Hi Nino, > > If you can stick to database-specific API, check whether your database > supports some sort of change propagation mechanism. > > Examples: > Oracle - Data Change Notification [1] > PostgreSQL - LISTEN/NOTIFY [2] > > Regards, > Milosz > > [1] http://www.oracle.com/technology/obe/11gr1_db/appdev/dcn/dcn.htm > [2] http://jdbc.postgresql.org/documentation/83/listennotify.html > > > > >> Hi >> >> I have a case where I need to check the database on each query, >> because there can be modifications to the data from a 3rd party non >> java application. Currently I have to refresh each object, otherwise >> it could be stale data however this approach are really slow and feels >> very wrong.. >> >> Any ideas on what I could do? >> >> regards Nino > >
