Sounds definitely promising. It would be interesting to see how this behaves performance-wise. When reading the documentation, I wondered how to exclude changes made by Hibernate itself from the notification mechanism, but I guess, there will be some way.
Gunnar 2010/4/8 Steve Ebersole <[email protected]> > If we could make it generic enough so it could work with other > notification schemes (other vendor extensions, user written triggers, > etc) then I'd be all of including this. > > Of course starting off with targeting a specific one and growing out > from there is ok :) > > > On 04/08/2010 07:29 AM, Emmanuel Bernard wrote: > > There's an interesting feature in Oracle that let's you register to > database changes events > > http://download.oracle.com/docs/cd/E11882_01/java.112/e10589/dbchgnf.htm > > > > We could use that to invalidate second level caches properly even if a > third-party app update the DB. > > > > Worth considering a prototype in Hibernate? > > _______________________________________________ > > hibernate-dev mailing list > > [email protected] > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > > -- > [email protected] > http://hibernate.org > _______________________________________________ > hibernate-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/hibernate-dev
