[
https://issues.apache.org/jira/browse/DERBY-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047565#comment-14047565
]
Knut Anders Hatlen commented on DERBY-6609:
-------------------------------------------
In addition to the features mentioned in the first comment, I've found
that these SQL:2011 part 2 features are supported:
F382 Alter column data type
- partial: it only allows altering VARCHAR, BLOB and CLOB columns, and
it only allows changing the length. That is, you can use it to
change the type from VARCHAR(10) to VARCHAR(100), but not from
VARCHAR(10) to CLOB(100).
F383 Set column not null clause
- supported via non-standard syntax. The standard syntax is
{code:sql}
ALTER TABLE t ALTER COLUMN c SET NOT NULL
ALTER TABLE t ALTER COLUMN c DROP NOT NULL
{code}
whereas the Derby syntax is
{code:sql}
ALTER TABLE t ALTER COLUMN c NOT NULL
ALTER TABLE t ALTER COLUMN c NULL
{code}
F690 Collation support
- partial. Should be listed instead of F691 "Collation and
translation", which seems to have been removed in newer revisions of
the standard.
F763 CURRENT_SCHEMA
- partial: Non-standard syntax (CURRENT SCHEMA instead of
CURRENT_SCHEMA), and it is not allowed in a DEFAULT clause
F850 Top-level <order by clause> in <query expression>
- fully supported
T021 BINARY and VARBINARY data types
- non-standard type names CHAR FOR BIT DATA and VARCHAR FOR BIT DATA
instead of BINARY and VARBINARY
T101 Enhanced nullability determination
- supported (fully, I think)
> Documentation for SQL features should reflect current standard
> --------------------------------------------------------------
>
> Key: DERBY-6609
> URL: https://issues.apache.org/jira/browse/DERBY-6609
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.11.0.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Attachments: DERBY-6609-2.diff, DERBY-6609-2.zip, DERBY-6609-3.diff,
> DERBY-6609-3.diff, DERBY-6609-3.stat, DERBY-6609-3.zip, DERBY-6609-3.zip,
> DERBY-6609-4.diff, DERBY-6609-4.stat, DERBY-6609-4.zip, DERBY-6609-5.diff,
> DERBY-6609-5.stat, DERBY-6609-5.zip, DERBY-6609.diff, DERBY-6609.stat,
> DERBY-6609.zip
>
>
> We document Derby as an SQL-92 database. This standard is now very old, and
> we should describe how Derby conforms to the most current standard
> (SQL:2011). Knut Anders Hatlen listed the relevant features in a comment to
> DERBY-6605.
> This will involve at a minimum replacing the "Derby support for SQL-92
> features" topic
> (http://db.apache.org/derby/docs/10.10/ref/rrefsql9241891.html) with a new
> one that describes Derby's support for current features, with notes as needed
> indicating when the support is partial. Only features Derby supports, fully
> or partially, should be listed. We should state that features not listed are
> not supported.
> The information would be taken from
> http://wiki.apache.org/db-derby/SQLvsDerbyFeatures (which currently goes only
> through the 2003 standard). Listing the Feature IDs in the documentation
> would also be helpful.
> Other topics should be changed as needed. For example, is the term
> "SQL92Identifier" still correct?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
