[ 
https://issues.apache.org/jira/browse/DERBY-6605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027968#comment-14027968
 ] 

Kim Haase edited comment on DERBY-6605 at 6/11/14 8:46 PM:
-----------------------------------------------------------

After some offline discussion we agreed that for 10.11 we should just update 
the current topic to make it correct for SQL-92. However, I filed DERBY-6609 to 
bring the documentation up to date and cover our compliance with the most 
current SQL standard, probably 2011.


was (Author: chaase3):
After some offline discussion we agreed that for 10.11 we should just update 
the current topic to make it correct for SQL-92. However, I will file another 
issue to bring the documentation up to date and cover our compliance with the 
most current SQL standard, probably 2011. That will be post-2011.

> "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)

Reply via email to