[
https://issues.apache.org/jira/browse/JDO-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650428#comment-14650428
]
Craig L Russell commented on JDO-745:
-------------------------------------
I think we are in agreement here. This would be an option:
static String OPTION_QUERY_BITWISE_OPERATIONS
= "javax.jdo.query.JDOQL.BitwiseOperations";
There is already an option "javax.jdo.query.JDOQL" so the new option would be
an extension.
If the underlying datastore supports bitwise operations, I'd expect (require?)
that the JDO implementation return this string from PMF.supportedOptions().
> TCK BooleanLogicalAND, BooleanLogicalOR testNegative don't allow an
> implementation to provide an extension of bitwise AND/OR
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JDO-745
> URL: https://issues.apache.org/jira/browse/JDO-745
> Project: JDO
> Issue Type: Bug
> Components: tck
> Reporter: Andy Jefferson
> Fix For: JDO 3.2
>
> Attachments: JDO-745.patch
>
>
> 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.3.4#6332)
