Thanks guys for taking this into consideration.
I've seen those negative tweets lately, regarding the JIRA issues and maybe
helping people provide more focused unit-tests is for the best.We could
integrate those easily into Hibernate main test suite and we can address them
more rapidly too.
I ne
That's indeed interesting. It is like a RDBMS that uses Hadoop as the
underlying storage engine.I see that others have managed to run the TPC-C suite
against Trafodion too:
http://hammerora.sourceforge.net/hammerdb_trafodion_oltp.pdf
I think this could be a good opportunity for Hibernate to appr
That's a good idea. After I'm done with the first part of my book, I'll review
all 5.0 changes and collect them all in one presentation for our local JUG too.
Vlad
On Wednesday, October 21, 2015 4:35 PM, Sanne Grinovero
wrote:
Remind me of this when we meet next week!
Happy to wa
Hi Steven,
I'm trying to integrate FlexyPool ( https://github.com/vladmihalcea/flexy-pool
) with Java EE Application servers, and the only work-around I found is to add
a new Hibernate ConnectionProvider that extends the
DataSourceConnectionProvider and exposes a DataSource proxy, instead of the
Hi Steve,
I was thinking of having a Metrics gathering API for all sorts of
database-related operations:
- connection acquiring/lease time- connection wait time- transaction durations-
SQL query logger
- slow queries threshold- number of queries per transaction threshold
Something similar to htt
From a performance perspective, I'm glad we'll be able to override the EAGER
fetching on a query-basis. We could have an UNFETCH directive to do the
opposite of the current FETCH one.
The bytecode enhancement dirty-checking is also a plus.
Vlad
On Friday, May 29, 2015 11:09 AM, Emmanue
Vlad Mihalcea
On Tuesday, May 5, 2015 1:52 PM, Mihalcea Vlad wrote:
Hi,
When an entity is updated for the
"CacheConcurrencyStrategy.NONSTRICT_READ_WRITE", the cache entry is removed
twice:
1. Once from update:public boolean update(Object key, Object value, Object
currentVersio
Hi,
When an entity is updated for the
"CacheConcurrencyStrategy.NONSTRICT_READ_WRITE", the cache entry is removed
twice:
1. Once from update:public boolean update(Object key, Object value, Object
currentVersion, Object previousVersion)
throws CacheException {
remove( key );
return fa
Hi guys,
Taking this comment as a starting point
http://vladmihalcea.com/2015/04/27/how-does-hibernate-read_only-cacheconcurrencystrategy-work/comment-page-1/#comment-3404
To reduce cache entities hydration, we could simply use the:
"hibernate.cache.use_reference_entries" setting, but that's too
Hibernate native) is historically non typed, I
> >> wonder if that is worth introducing these new typed version and add more
> >> overloaded methods on Session.
> >> Do you think it is worth the additional complexity?
> >>
> >> Steve, do you have some
Hi,
Setting the "hibernate.cache.default_cache_concurrency_strategy" property
doesn't have any effect.
This setting is inspected in
AnnotationBinder.prepareDefaultCacheConcurrencyStrategy method, but thatmethod
is never called.
Here's a test to replicate the issue:
https://github.com/vladmihalc
Hi,
Although many rely on the Java Persistence API, Hibernate still offers specific
features, like mapping a native SQLQuery result set to a DTO:
.setResultTransformer(Transformers.aliasToBean(DTO.class));
Is it possible to add TypedQuery and TypedSQLQuery, analogous to the JPA specs,
so you can
Hi,
While INSERT sorting is handled by ActionQueue.InsertActionSorter, DELETE
statements are not sorted at all.
A DeleteActionSorter woudl have to rearrange DELETES in the opposite order as
the INSERT sorting, the Children having to be deleted first.
The current work-around is to dissociate all C
Hi,
While investigating how Lock Cascading works, I realized that the lock "scope"
is only applied for detached entities.
Object entity = source.getPersistenceContext().unproxyAndReassociate(
event.getObject() );
//TODO: if object was an uninitialized proxy, this is inefficient,
// resulting
Hi,
According to JPA specification, when using PessimisticLockScope.EXTENDED:
In addition to the behavior for PessimisticLockScope.NORMAL, element
collections and relationships owned by the entity that are contained in join
tables will be locked if the javax.persistence.lock.scope property
15 matches
Mail list logo