[
https://issues.apache.org/jira/browse/DERBY-6605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-6605:
-----------------------------
Attachment: DERBY-6605.diff
rrefsql9241891.html
Attaching DERBY-6605.diff and rrefsql9241891.html, a preliminary patch for this
issue.
M src/ref/rrefsql9241891.dita
I added a shortdesc and made a few other formatting tweaks near the top, but I
found only a couple of things to change.
Are deferrable constraints part of SQL92E or SQL92F? On the wiki page they are
shown as F, but for a later version of the standard. I am guessing they were in
SQL-92 in some form, since DERBY-532 was filed pretty early and they have been
mentioned (as unsupported) in the "Derby support for SQL-92 features" topic.
I added support for NATURAL JOIN. When did CROSS JOIN come into SQL -- after
92? It's not listed in the table as unsupported.
What should I say about scrolled cursors? The table says "Partial support
(scrollable insensitive result sets through JDBC 2.0)". That seems outdated.
I didn't see anything else that looked obvious. Please let me know what needs
changing. Thanks!
> "Derby support for SQL-92 features" topic in Reference Manual needs updating
> ----------------------------------------------------------------------------
>
> Key: DERBY-6605
> URL: https://issues.apache.org/jira/browse/DERBY-6605
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.11.0.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-6605.diff, rrefsql9241891.html
>
>
> The topic "Derby support for SQL-92 features" in the Reference Manual
> (http://db.apache.org/derby/docs/10.10/ref/rrefsql9241891.html) seems not to
> have been substantively updated since about 2007.
> For one thing, the parenthesis "(non-deferrable)" needs to be removed from
> Table 8 (constraint support). Also, I think we've supported natural joins for
> some time.
> Could someone more knowledgeable than I am go through the items marked "No"
> and see if any more need updating? I think those two might be the only ones,
> but I am not quite sure.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
