[
https://issues.apache.org/jira/browse/JDO-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187457#comment-16187457
]
Andy Jefferson commented on JDO-745:
------------------------------------
Does Apache Derby now support some bitwise operators? because it certainly
never used to (hence DataNucleus not supporting it). If it still does not then
is the test of value when the TCK only runs with Derby?
See
https://stackoverflow.com/questions/11101333/bitwise-operator-in-apache-derby
Regarding having the TCK runnable on other RDBMS, I'd welcome that, but the
significant blocker on that is that the "exectck" was written explicitly to use
this Derby "ijs" seemingly, rather than using JDBC, like the code in
https://github.com/datanucleus/datanucleus-rdbms/blob/master/src/main/java/org/datanucleus/store/rdbms/RDBMSStoreManager.java#L4349
> Support bitwise operations in JDOQL
> -----------------------------------
>
> Key: JDO-745
> URL: https://issues.apache.org/jira/browse/JDO-745
> Project: JDO
> Issue Type: New Feature
> Components: specification, tck
> Reporter: Andy Jefferson
> Assignee: Michael Bouschen
> Fix For: JDO 3.2
>
> Attachments: JDO-745.patch, JDO-745-patch2.txt
>
>
> The tests BooleanLogicalAND.testNegative, BooleanLogicalOR.testNegative don't
> test use of a boolean logical AND/OR. They actually test for an integer being
> used with the "&" and "|" operators. Sadly this means that any implementation
> that attempts to provide a vendor extension of support for bitwise AND/OR
> (for those RDBMS that support it) cannot pass the TCK.
> Perhaps add an "optional feature" for the vendor to support bitwise
> operations, and then don't run that test if so.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
