Craig,
I'd love to (I did something similar for Pentaho recently). But the
latest SVN doesn't build for me. I get stuff like this:
/workspace/openjpa-trunk/openjpa-lib/src/main/java/org/apache/openjpa/lib/jdbc/DelegatingConnection.java:[47,7]
org.apache.openjpa.lib.jdbc.DelegatingConnection is not abstract and does not
override abstract method createStruct(java.lang.String,java.lang.Object[]) in
java.sql.Connection
A test case, I've already got, alas. I'll make a more general one once I
resolve it.
I don't have JIRA rights, however. Been asking other people to handle
that for me in the past.
Regards,
Tim
On Mon, 2008-06-02 at 08:55 -0700, Craig L Russell wrote:
> Hi Tim,
>
> On Jun 2, 2008, at 7:31 AM, Tim Holloway wrote:
>
> > I've always found it difficult to trace back to where merges caused
> > stale copies of an object to appear, resulting in Optimistic Locking
> > Exceptions.
> >
> > Q: Would it be reasonable to add some functionality to the
> > StateComparisonVersionStrategy such that if a conflict is encountered
> > that the offending field and its conflicting values be displayed,
> > either
> > in the Exception itself or in the log? It looks like
> > ArrayStateImage.sameVersion would need to reflect back the failing
> > column index.
>
> Sounds like a good idea to me. Can you write a) a patch; b) a test
> case; c) a JIRA?
>
> Craig
> >
> >
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:[EMAIL PROTECTED]
> P.S. A good JDO? O, Gasp!
>
