[ http://issues.apache.org/jira/browse/DERBY-499?page=all ]
Rick Hillegas updated DERBY-499:
--------------------------------
Attachment: bug499_jdk13tests_rev2.diff
I have attached a second rev of the patch to fix the problems in the jdk13
testrun: bug499_jdk13tests_rev2.diff. I hope that this patch addresses Kathey's
concerns:
1) Still tests the version related metadata calls.
2) Allows the tests to pass on all jvms
3) Keeps a single bumpversion target for release
This version of the patch differs from the previous version as follows:
o Re-instates the explicit printing of the version information from the
metadata calls
o Eliminates any need to change the odbc_metadata canons
o Adds the new metadata canons to the list managed by the bumplastdigit release
target in tools/release/build.xml
I have cleanly run derbyall against this patch. I have also cleanly run the
metadata and syscat tests in embedded, DerbyNetClient, and DerbyClient modes on
jdk1.3 and jdk1.4. The patch contains the following:
M tools\release\build.xml
M java\testing\org\apache\derbyTesting\functionTests\tests\lang\syscat.sql
M
java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\metadata_test.java
M
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNet\syscat.out
D
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\metadata.out
D
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\syscat.out
A
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\jdk13
A
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\jdk13\metadata.out
A
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\jdk13\syscat.out
A
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\jdk14\metadata.out
A
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\jdk14\syscat.out
M java\testing\org\apache\derbyTesting\functionTests\master\syscat.out
> Expose BOOLEAN datatype to end users
> ------------------------------------
>
> Key: DERBY-499
> URL: http://issues.apache.org/jira/browse/DERBY-499
> Project: Derby
> Type: New Feature
> Components: SQL
> Versions: 10.1.1.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: BooleanFS.html, bug499.diff, bug499_doc.zip,
> bug499_jdk13tests.diff, bug499_jdk13tests_rev2.diff, bug499_rev2.diff,
> bug499_rev3.diff, bug499_rev4.diff, jdk131BooleanFailures.zip
>
> Veaceslav Chicu started an email thread on 8 August 2005 titled "boolean
> type". He was disappointed that Derby doesn't support the ansi BOOLEAN
> datatype. On closer inspection, Derby does internally support this type but
> does not expose this support to end users.
> Derby should let users declare table columns of type BOOLEAN. This should be
> an indexable datatype.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
