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
> If w
Hibernate Annotations is copyright Red Hat, Inc. and the various @author listed
in the javadoc. and is LGPL 2.1
On 8 avr. 2010, at 16:54, Murray Gibb wrote:
>
> There is no copyright notice anywhere in hibernate-annotations for versions
> 3.4.0 and earlier. What is the correct copyright statem
There is no copyright notice anywhere in hibernate-annotations for versions
3.4.0 and earlier. What is the correct copyright statement for these versions.
I am specifically looking for the copyright for 3.3.0.
I see that when hibernate-annotations was merged into Hibernate Core the
copyrigh
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, Emmanue
I vaguely remember to have overheard that PostgreSQL supports
something similar, would be really nice; sorry don't have a reference.
If it works nicely for second level caches, you might extend it to Search too.
2010/4/8 Emmanuel Bernard :
> There's an interesting feature in Oracle that let's you
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 prototyp
