Hi Madhumita Sadhukhan,
although I did not receive your attachments,
please allow me to make some considerations to point 5 and successive:
point 5:
When you load using updated natural-ids values, it should depend on the
isolation level you use, whether you retrieve a result or not.
With levels
Hello Steve and Guenther,
Thanks for sparing some time to look into this.
The entitymapping information for Person is in file
HibernateNativeAPINaturalId2LCachingTestCase.java in string testmapping.
For convenience I have uploaded the test to my AS7 github as follows:
https://github.com/madhumit
More on in.relation.to - http://in.relation.to/Bloggers/HibernateValidator430CR1
--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Could this be a common enough issue that Hibernate includes a
work-around type so that everyone doesn't have to write their own?
We've had to address this wonderful Oracle "feature" via a custom user
type as well, ours is based on http://usertype.sourceforge.net/ and the
NullSafeStringType and
Thank you Madhumita , finally I was able to reproduce all steps.
Whilst point 6 represents definitely a bug (I opened
https://hibernate.onjira.com/browse/HHH-7287)
I'm not so sure about point 5:
the NaturalIdLoadAccess's internal query does 'see' the new values, when the
used isolation level is
The problem with this analogy is that really what is being tried here
is much more like changing the entity's primary key behind the scenes.
Hibernate wont clean up cache entries (persistence context nor L2C) in
that case either.
Like I said before, IMO this is really just a bad use case. He
On 04/30/2012 04:32 AM, Madhumita Sadhukhan wrote:
> Steve,
> I am following the normal pattern followed by most jpa/hibernate integration
> testcases in AS7 where the methods/actions involving the Transaction or
> Session is handled in the (SF/SL)Session Bean which in turn is invoked from
> the
On 04/30/2012 08:30 AM, Demetz, Guenther wrote:
> Whilst point 6 represents definitely a bug (I opened
> https://hibernate.onjira.com/browse/HHH-7287)
Well, again, I am not so sure this is a bug.
First, in the test you go out of your way to mix transactional and
non-transactional access to the
Hi Steve, hi Madhumita,
>> If you change your non-transactional access to instead be transactional, it
>> works.
Yes, that's true (thanks to the new paradigma with inline natural-id sync
processing).
Madhumita, can you please confirm, that also your test-case is using
non-transactional access
