On Tue, 29 Aug 2006 00:45:52 +0200, Josh Moore <[EMAIL PROTECTED]> wrote:

Sorry, myself, if there's nothing more anyone can say to versions being broken. Without input, though, I'll assume it's easier to roll our own.

If you by "roll our own" means make a fix for it then we would of course be interested in it.

As with all existing issues we need to prioritize them and issues with patches
has a very high tendency to be fixed before issues without patches.

/max


Thanks,
~Josh

Steve Ebersole wrote:
Sorry, I must have missed the patch implementing the fix.  Where do I
find that again?
 -----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Josh Moore
Sent: Thursday, August 24, 2006 1:25 PM
To: hibernate-dev@lists.jboss.org
Subject: [hibernate-dev] Possible to confirm that versioning is broken
forPersistentSets?
 Can anyone confirm if or add some insight to why versioning is broken?
Since Jan. 06 (v3.1.1), there's been an unassigned issue HHH-1401 saying
that versions are updated unnecessarily on merge. At least three other issues have been added with similar problems for delete and in general with PersistentSets. I just reconfirmed the failing testcase from 1401 for r10347. What's the story??
 ~Josh
The Openmicroscopy Environment
  ---[links]---
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1401
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1564
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1660
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1668


_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev



--
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
[EMAIL PROTECTED]
http://hibernate.org

JBoss a division of Red Hat
[EMAIL PROTECTED]
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Reply via email to