Thanks for investigating it. On Mon, Dec 7, 2015 at 9:40 PM, Gail Badner <gbad...@redhat.com> wrote:
> This is something that got broken in 4.3 when we moved to using load > plans. I agree this needs to be fixed. I will get to this later this week. > > On Mon, Dec 7, 2015 at 12:18 AM, Vlad Mihalcea <mihalcea.v...@gmail.com> > wrote: > >> Hi, >> >> Someone on Twitter pointed out this issue: >> https://hibernate.atlassian.net/browse/HHH-9764 >> I managed to add a test case using the Hibernate ORM Test Templates and >> the >> issue is replicated. >> >> The question is whether we should run the version check when loading >> entities from the database. This issue is caused by initializing a >> collection that contains a previously loaded entity which has changed in >> between. >> >> I also think we shouldn't raise the exception in this case because the >> client might not modify the data anyway. >> >> Vlad >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
