[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipselink-dev] Updated Proposal for submitted DatabasePlatform integration

Sounds good, but in the particular case of SQL Anywhere, doesn't match the
reality: While my contributed code at runtime is superior to the existing
code, the existing code passes more tests. Sad but true, this is not a
problem of the platform, but of the particular tests. As many of them are
not well documented, it is nearly impossible to understand what they intend
and what the reason is why they not pass. In the SQL Anyhwere scenario many
of the tests are written in the expectation that SQL Anywhere is derived
from Sybase ASE, which it actually is not the case. So it is quite obvious
that the tests will pass with a "wrong" platform much better than with a
"correct" one. In the end, this cannot be solved without massive help of
Oracle to either document or rewrite the tests.

> -----Original Message-----
> From: eclipselink-dev-bounces@xxxxxxxxxxx [mailto:eclipselink-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
> Sent: Donnerstag, 18. Februar 2010 16:34
> To: dev mailing list for Eclipse Persistence Services
> Subject: [eclipselink-dev] Updated Proposal for submitted
> DatabasePlatform integration
> Hi All,
>    I have updated the proposal for lowering the barrier for integrating
> contributer-submitted DatabasePlatforms into the product.  Please
> provide
> feedback either via this mailing list, or the Discussion page.
> http://wiki.eclipse.org/EclipseLink/Development/Incubator/Extensions/Da
> tabasePlatformPromotion
> -Tom
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev