View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sqlserver-jtds-testsuite?log=log20070411024417Lbuild.10
BUILD COMPLETE - build.10Date of build: 04/11/2007 02:44:17Time to build: 13 minutes 19 secondsLast changed: 04/10/2007 10:54:07Last log entry:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20070411023148Lbuild.9
BUILD COMPLETE - build.9Date of build: 04/11/2007 02:31:48Time to build: 11 minutes 34 secondsLast changed: 04/10/2007 10:54:07Last log entry: HHH-2533:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle9-testsuite?log=log20070411021644
TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:112: The following error occurred while executing this line: /qa/services/cruis
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-pgsql-testsuite?log=log20070411015429
TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:161: The following error occurred while executing this line: /qa/services/cruisec
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20070411012950Lbuild.10
BUILD COMPLETE - build.10Date of build: 04/11/2007 01:29:50Time to build: 23 minutes 36 secondsLast changed: 04/10/2007 10:54:07Last log entry: HHH-25
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20070411010823
TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:126: The following error occurred while executing this line: /qa/services/cruise
Max Rydahl Andersen wrote:
That means if you want different behavior for the different "types" of
caches you need separate caches. If the JGroups multiplexer is
available, that's not too bad, as the caches can share a channel. If
we think it through well, they can likely share an overall conf
Steve Ebersole wrote on 04/03/2007:
> Also, is the db2 instance still accessible? My VPN is finally working
> and I finished the release I was working on, so I'll try to look at all
> these today.
Hi,
Have you managed to look at hibernate testsuite hanging on DB2?
Could you provide us with any s
Steve Ebersole wrote:
Re: #4 : what exactly are these differences? Now is the time to
merge it back...
Forgot to attach the diff to my last message. Here it is.
- Brian
---
C:\dev\hibernate\Branch_3_2\Hibernate3\src\org\hibernate\cache\TreeCache.java
Mon Feb 19 17:05:11 2007
+++ C:\de
Max Rydahl Andersen wrote:
So I started breaking out 3.3 as a separate code base on the Hibernate
svn trunk. The first thing done was this org.hibernate.cache.Cache
splitting. So at this point we now have the ability to be completely
free in how we cache entity-data versus collection-data v
But now looking back at #1, I am no longer certain of the conclusions;
and to me the wiki did not make it clear to me what the "long term"
solution was supposed to be (nor really what the "short term" solution
is/was either). Anyone remember the specific conclusions with regards
to this
Manik can better comment on plans for having separate configurations
(e.g. optimistic vs pessimistic, invalidation vs replication) for
different regions of the cache. But, I know it's not a soonish thing.
That means if you want different behavior for the different "types" of
caches you need
Long-term:
In Hibernate - use seperate caches which you have done for 3.3
Not quite true. What I have done so far is to introduce this
possibility. What happens right now is that there is only a single
RegionFactory implementation which simply "bridges" to the old
CacheProviders. Or per
Long-term:
In Hibernate - use seperate caches which you have done for 3.3
Not quite true. What I have done so far is to introduce this
possibility. What happens right now is that there is only a single
RegionFactory implementation which simply "bridges" to the old
CacheProviders. Or perhap
14 matches
Mail list logo
