After fixing HHH-6848, Hibernate throws IllegalStateException when merging
entity 'x' if it has references to 2 detached entities 'y1' and 'y2' obtained
from different sessions, and y1 and y2 represent the same persistent entity. In
other words, y1 != y2.
I've pushed some FailureExpected test c
Please bear with me, it's 1:45am and someone on the internet is wrong :-).
Somehow this triggered a knee-jerk reaction to an issue that is rather
minor, hasn't bothered me in months (every now and then I come across the
comment in our source code that references this particular hibernate issue,
an
What I am thinking at the moment is to change up
org.hibernate.metamodel.spi.binding.EntityIdentifier to look like:
public class EntityIdentifier {
private final EntityBinding entityBinding;
private EntityIdentifierNature nature;
private IdentifierAttributeBindings attributeBindings;
priv
Good points, we definitely need to make it easier to contribute, be it
just a least resistance path for making a test.
For what it's worth, when I started contributing more seriosly, the
"tipping point" which transformed me from an average user to a
fanatical contributor, was to understand how the
Y, Ehcache will work clustered both in transactional (JTA), read-only and
read-write just fine (non strict will work, only blows the race wider open
and inconsistent data will be noticed "quicker").
Am trying to think hard what a cache provider "conceptually needs" to
support clustered scenarios. O
But Martijn, you're still missing my main points.
"...awaiting a response from the core team..."
"...without any evidence of a core member looking at the issue..."
"...your users..."
You're still thinking of this community in a proprietary product sense. It's
not. The core team is small and fo
Hi Martijn, I'm CC'ing the mailing list -- there are a few misconceptions I'd
like to clear up for everyone.
First and foremost, statements like "But nobody from the Hibernate has ever
taken a look" are frankly frustrating. Hibernate is an open source project,
not a proprietary product with se
Hi all,
On another note I just wanted to mention the new release of Ology,
www.ology.com.br.
It's a social network that can be seen as a mix between Facebook and
LinkedIn exclusively for physicians that runs on Spring, Hibernate,
Hibernate Search, YUI. Although this is not a technical topic, and I
Fair enough. It's a shame though. Like it or not, there are tons of people
using Spring and I'm guessing the vast majority will not be on 4.0 any time
soon, even though they might want to. So, this will certainly impact the
uptake of Hibernate latest version (including the amount of bug reports
aga
I simply do not consider Spring a valid reason to keep older Hibernate
release families active. So to say its "not on the Spring team" and imply
it is all Hibernate's problem is a bit misleading. Early in
Spring/Hibernate integration they used to work with us to flesh out
integration points. Of
I've been spending a lot of time the last 2 weeks trying to get a good
"mental model" as to how to best model the information pertaining to an
entity's primary key. Most of this effort went into trying to understand
JPA's "derived identity" support.
First and foremost I want to get away from mode
2014-04-04 15:06 GMT+02:00 Gunnar Morling :
> 2014-04-04 13:54 GMT+02:00 Sanne Grinovero :
>
> I did a bit of maintenance while looking at the OGM job.
>> It looks like that the OGM jobs actually finish in a reasonable time,
>> but the status is not being reported, or the workspace was containing
12 matches
Mail list logo
