Re: [eclipselink-dev] rewriting updateall queries clean-up code in tests

[Tom Ware <tom.ware@xxxxxxxxxx>]

Hi Dies,

  That sounds correct to me.

-Tom

Dies Koper wrote:
> Hi Tom,
>
> Just confirming, but the following failing tests would need to be 
> skipped for Symfoware because of the multi-table entity update/delete 
> queries. Would you agree?
>
> * org.eclipse.persistence.testing.tests.jpa.jpql.JUnitJPQLExamplesTestSuite
> - testDeleteExpression
> - testComplexDeleteExpression
> - testUpdateExpression
>
> * org.eclipse.persistence.testing.tests.jpa.jpql.JUnitJPQLModifyTestSuite
> - simpleUpdate
> - updateEmbedded
> - updateEmbeddedFieldTest
> - updateUnqualifiedAttributeInSet
> - updateUnqualifiedAttributeInWhere
>
> Thanks,
> Dies
>
>
> On 12/01/2010 08:26, Tom Ware wrote:
> > > > *
> > > > jpa/eclipselink.jpa.test/src/org/eclipse/persistence/testing/tests/jpa/jpql/JUnitJPQLComplexTestSuite.java 
> > > >
> > > >
> > > >
> > > > complexConditionCaseInUpdateTest
> > > >
> > > > This test fails because it uses a multi-table entity. If I would 
> > > > rewrite
> > > > it to use an entity that is mapped to a simple table, it might pass.
> > > > Should I try, or should I just skip these type of tests on Symfoware?
> >
> > Let's just skip this kind of test for Symfoware. Altering the test will
> > reduce our testing of multi-table.
>
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev