db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3962) Foreign keys: ON DELETE SET DEFAULT possibility not mentioned in docs
Date Mon, 24 Nov 2008 21:15:44 GMT

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

Kim Haase commented on DERBY-3962:

Should the language about SET DEFAULT be similar to the language about SET NULL?

"SET DEFAULT, each column of the dependent table's foreign key is set to its default value,
if it has one. (Again, if the dependent table also has dependent tables, nullable columns
in those tables' foreign keys are also set to the default values.)" 

Should a bullet item be added at the end of this section also? What should it say?

I am guessing that nothing needs to be said explicitly in this topic about generated columns,
since the CONSTRAINT clause is not mentioned under "Documentation" in the generated columns
spec (DERBY-481).

> Foreign keys: ON DELETE SET DEFAULT possibility not mentioned in docs
> ---------------------------------------------------------------------
>                 Key: DERBY-3962
>                 URL: https://issues.apache.org/jira/browse/DERBY-3962
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Priority: Minor
> Cf. http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> The docs mention the ON DELETE alternatives NO ACTION, RESTRICT, CASCADE, SET NULL only.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message