Thanks, Jarek. I had actually stumbled onto that already and just haven't updated my post. I tried upgrading to 10.4.1.3, but that didn't solve the problem that 10.3.2.1 seemed to solve. I'm working on trying to understand the problem better so I can fix it somehow.
On Wed, May 14, 2008 at 1:13 PM, Jarek Gawor <[EMAIL PROTECTED]> wrote: > Please run the little sql shown in my comment on > https://issues.apache.org/jira/browse/GERONIMO-3545 to verify the > problem is fixed in 10.3.2.1. From > https://issues.apache.org/jira/browse/DERBY-3094 it looks like the > problem was fixed in 10.3.2.2 and 10.4.1.3 so 10.3.2.1 might not work. > > Jarek > > On Tue, May 13, 2008 at 3:53 PM, Jason Warner <[EMAIL PROTECTED]> wrote: > > I'd like to update our derby version to 10.3.2.1 in branches/2.1 and > trunk. > > This is directly related to the update of tomcat and resolves some TCK > > issues introduced by the tomcat update. This is all assuming TCK remains > > happy. > > > > -- > > ~Jason Warner > -- ~Jason Warner
