[
https://issues.apache.org/jira/browse/DERBY-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4613:
---------------------------------
Attachment: derby-4613-01-ac-correctBehavior.diff
Attaching derby-4613-01-ac-correctBehavior.diff. This adds compatibility tests
to the previous version of the patch.
I verified the new tests by running them against combinations of the following
client and server versions on jdk1.4, Java 5, and Java 6: I believe this patch
is ready to be committed.
10.0.2.1
10.1.1.0
10.2.2.0
10.4.2.1
10.6.1.0
Trunk (10.7.0.0)
Touches the following additional files:
M
java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/CompatibilitySuite.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/JDBCDriverTest.java
> Make client driver treat BOOLEAN columns the same way as the embedded driver
> does.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-4613
> URL: https://issues.apache.org/jira/browse/DERBY-4613
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.6.1.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-4613-01-ab-correctBehavior.diff,
> derby-4613-01-ac-correctBehavior.diff, derby-4613-fs.html
>
>
> The only operation currently allowed on BOOLEAN columns is to select them
> from the system tables. For instance, the following query selects BOOLEAN
> values:
> select systemalias from sys.sysaliases;
> There are discrepancies in how the embedded and client drivers handle these
> BOOLEAN columns. The embedded behavior is correct and the client behavior
> should conform. I will attach a spec describing what needs to be done.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
