On 1/25/08 7:22 PM, "Tore Halset" <[EMAIL PROTECTED]> wrote:
> pom.xml asks for derby 10.2.2.0. "alter table ... drop column ..." was > added in derby 10.3. 10.2.2.0 is from december 2006 and the first 10.3 > is from august 2007. Would it be ok to bump up to derby 10.3 for trunk? > > After upgrading to 10.3 (locally) and patching some small issues in > trunk (r615405), I got the merging part of derby running. Only(?) the > following 3 issues left with derby. > > testDifferentEntity > (org.apache.cayenne.access.DataContextEJBQLSubqueryTest) > testExists(org.apache.cayenne.access.DataContextEJBQLSubqueryTest) > testBinaryPK2(org.apache.cayenne.dba.PkGeneratorTest) > > I think we should go for Derby 10.3. > > - Tore. I'm for it, but we should add a note to the merge docs about incompatibility with older versions. I'd hazard to say that Derby is far easier to upgrade than most other traditional RDBMS servers, but we should still support users of older versions in any capacity that we can (within reason, of course). -- Kevin
