[ http://issues.apache.org/jira/browse/DERBY-499?page=all ]
Rick Hillegas updated DERBY-499:
--------------------------------
Attachment: bug499_jdk13tests.diff
Hi Kathey: The attached patch bug499_jdk13tests.diff fixes the regressions you
found in the metadata.java and syscat.sql tests under jdk13:
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\metadata.out
M
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNet\syscat.out
M
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNet\odbc_metadata.out
D
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\metadata.out
D
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\syscat.out
M
java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\odbc_metadata.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\metadata.out
M java\testing\org\apache\derbyTesting\functionTests\master\syscat.out
M
java\testing\org\apache\derbyTesting\functionTests\master\odbc_metadata.out
Along the way I made the following improvements to these tests:
o I removed the printing of version numbers in the output of metadata.java.
Instead, this test now compares version numbers internally. Keeping this test
in sync with the release variables in dnc.properties now involves changing a
couple constants in metadata.java rather than updating 10 canons. As extra
credit, someone may want to further improve this test by removing the
hard-coded version constants and, instead, get version information from
Configuration.java. That depends on one's feelings about what the point of this
version check is.
o I removed a potential instability from syscat.sql by adding ORDER BY clauses
to several queries whose results were not well-defined.
My first attempt at fixing these regressions did not catch odbc_metadata. So I
had 3 failures in derbyall: odbc_metadata under embedded, DerbyNetClient, and
DerbyNet. I have fixed them. I have verified that all three tests (metadata,
odbc_metadata, and syscat) run cleanly in all three configurations (embedded,
DerbyNetClient, and DerbyNet) under jdk1.4 and jdk1.3.
I believe there is a remaining piece of cleanup here: the j9_foundation canons
for metadata and odbc_metadata. I would appreciate it if those canons could be
fixed by someone who has installed the small device configuration.
> 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_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
