[
https://issues.apache.org/jira/browse/JDO-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14637387#comment-14637387
]
Andy Jefferson commented on JDO-745:
------------------------------------
FWIW bitwise AND, OR, XOR were removed from the spec "after draft 0.9"; before
my time. Not all RDBMS allows them, and in fact it is a minority that do
support them (or at least using the equivalent &, |, ^ syntax - PostgreSQL,
MySQL/MariaDB, SQLServer and NuoDB do). Perhaps that is why they were removed?
Anyway, I'm in favour of allowing them as optional, and also of making them
available via the JDOQLTypedQuery within the NumericExpression interface as
bor(), band(), bxor() methods (which can throw JDOException if not supported
for that datastore/provider).
> 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
> 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)
