I believe this only comes into play if you are using query caching. We
had to turn that off for this very reason.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel
Bernard
Sent: Sunday, November 11, 2007 5:29 PM
To: Markus Heiden
Cc: hibernate-dev@
No what I am talking about is not related to the caching system.
On Nov 12, 2007, at 17:31, Shawn Clowater wrote:
I believe this only comes into play if you are using query
caching. We
had to turn that off for this very reason.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EM
Sorry, I should have been clearer. The memory consumption we were
seeing was caused from the following from the ActionQueue.
public void execute(Executable executable) {
final boolean lockQueryCache =
session.getFactory().getSettings().isQueryCacheEnabled();
if ( e
Starting with 3.3 I plan on introducing hibernate-extras, which will be a
separate jar which will include code which is un-tested and un-maintained by
committers. The impetus for this move is simply to make it clear to users
what pieces of functionality are tested in an ongoing fashion and are
Hi Shawn,
I experienced some time ago, that turning off the 2nd level could help
getting rid of memory consumption problems, but wasn't able to track down
the problem exactly. Your problem is the same problem as mine. As a solution
I suggested to cut the references to the instances (applicatio
Honestly I think that the WebSphere TransactionManager Lookups should
remain in the "core" bundle. I know that it is a pain to test and
maintain but I think that Hibernate is Quote popular in WS environments
Cheers,
Mike
Am 12.11.2007 um 22:41 schrieb Steve Ebersole <[EMAIL PROTECTED]>:
Sta
On Monday 12 November 2007 04:04:22 pm Michael Plöd wrote:
> Honestly I think that the WebSphere TransactionManager Lookups should
> remain in the "core" bundle. I know that it is a pain to test and
> maintain but I think that Hibernate is Quote popular in WS environments
Funny, the WS TM lookups a
PS: Nachricht ist kurz, wurde von meinem iPhone gesendet.
Am 12.11.2007 um 23:14 schrieb Steve Ebersole <[EMAIL PROTECTED]>:
On Monday 12 November 2007 04:04:22 pm Michael Plöd wrote:
Honestly I think that the WebSphere TransactionManager Lookups should
remain in the "core" bundle. I know th
Sorry for the last message I need to get used to my iPhone :-(
I totally see your point but judging from my experience the WS
customer is an extremely conservative one that wants everything to be
"supported" within the "1st class" Jar file. I know this is hillarious
but that's the way I saw
> IMO, the thing that is being missed here is the ideal of open-source, which is
> that someone with a stake in these WS TM lookups steps up and maintains it.
Agree.
Btw, i think that H2Dialect and SybaseAnywhereDialect could be moved too.
> On Nov 12, 2007 7:14 PM, Steve Ebersole <[EMAIL PROTE
Yep, I missed the SybaseAnywhereDialect
I actually use the H2 one myself for local testing, and I will be having that
one set up on CI later.
On Monday 12 November 2007 04:30:33 pm Diego Pires Plentz wrote:
> > IMO, the thing that is being missed here is the ideal of open-source,
> > which is th
Btw, talking on dialects, I've started to talk with Postgre developers
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2942
They asked for a way to dynamically add functions to the dialect,
doing some query's on db metadata. Another thing is to send database
minor version to Dialec
12 matches
Mail list logo
