AFAIR the last time we discussed this (last summer in Austin with
Steve and Gavin) we came to the conclusion that R_C was optimal for
the 2LC use case.
On 17 Jul 2008, at 22:59, Brian Stansberry wrote:
Hmm, good point. Potentially also Session.refresh(...), although I'm
not sure if the imp
Hi all,
I've found a recommendation for a source code header at
http://www.hibernate.org/438.html
I'm not seeing this header on the code?
What are the guidelines, should we add it to new classes?
regards,
Sanne
___
hibernate-dev mailing list
hibernate-de
yes it should
--
Emmanuel Bernard
http://in.relation.to/Bloggers/Emmanuel | http://blog.emmanuelbernard.com
| http://twitter.com/emmanuelbernard
Hibernate Search in Action (http://is.gd/Dl1)
On Jul 18, 2008, at 07:28, Sanne Grinovero wrote:
Hi all,
I've found a recommendation for a source
BTW the intelliJ codestyle is here
http://www.hibernate.org/438.html#A4
--
Emmanuel Bernard
http://in.relation.to/Bloggers/Emmanuel | http://blog.emmanuelbernard.com
| http://twitter.com/emmanuelbernard
Hibernate Search in Action (http://is.gd/Dl1)
On Jul 17, 2008, at 10:58, Sanne Grinovero
Manik Surtani wrote:
AFAIR the last time we discussed this (last summer in Austin with Steve
and Gavin) we came to the conclusion that R_C was optimal for the 2LC
use case.
Yep. I was looking for reasons to flat out say "never use R_R, always
R_C" in docs and such. Seems it's a bit more sub
refresh() always goes to the db, and only potentially triggers a 2LC
update - not a read.
Perhaps we should revisit whether the scenario below warrants the cost
of repeatable_read, given that entity eviction from session cache is
typically used only to minimize memory usage when iterating through
Galder Zamarreno wrote:
Paul Ferraro wrote:
refresh() always goes to the db, and only potentially triggers a 2LC
update - not a read.
[OT] A concern I have is whether the refresh() removes the item from the
2LC before doing the subsequent Hibernate cache put(). If not our
putForExternalRea
I am trying to check out the source for hibernate according to instructions
on http://www.hibernate.org/6.html.
This page refers to the module "Hibernate3" in a couple of places, and in
one spot even provides an svn command
that suggests where I can get the branched version:
Important note, the c
Should we need a readerProvider.destroy()?
ReaderProvider typically keep IndexReaders open till they are in use
or if the index has been updated. But it has no hook to close the
"current" IndexReaders when Hibernate Search goes down.
I imagine the current code can become problematic on some
