You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2008/11/24 18:55:44 UTC
[jira] Created: (DERBY-3962) Foreign keys: ON DELETE SET DEFAULT
possibility not mentioned in docs
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.
[jira] Assigned: (DERBY-3962) Foreign keys: ON DELETE SET DEFAULT
possibility not mentioned in docs
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-3962:
--------------------------------
Assignee: Kim Haase
> 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
> Assignee: Kim Haase
> 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.
[jira] Commented: (DERBY-3962) Foreign keys: ON DELETE SET DEFAULT
possibility not mentioned in docs
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650584#action_12650584 ]
Kim Haase commented on DERBY-3962:
----------------------------------
Thanks very much, Dag! I'll work on this while I work on the generated columns documentation (DERBY-3959).
> 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
> Assignee: Kim Haase
> 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.
[jira] Updated: (DERBY-3962) Foreign keys: ON DELETE SET DEFAULT
possibility not mentioned in docs
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3962:
-----------------------------
Assignee: (was: Kim Haase)
I think this feature shouldn't be documented till it works. Unassigning myself from this issue, since it's related to DERBY-3963, which is not yet assigned.
> 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.
[jira] Commented: (DERBY-3962) Foreign keys: ON DELETE SET DEFAULT
possibility not mentioned in docs
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-3962) Foreign keys: ON DELETE SET DEFAULT
possibility not mentioned in docs
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650405#action_12650405 ]
Dag H. Wanvik commented on DERBY-3962:
--------------------------------------
Thanks for looking at this,Kim!
I think it should read:
"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, columns in those tables' foreign keys that have default values are also set to their default values.)"
As for the last list of bullets, I think one should be added:.
- If the delete rule is SET DEFAULT, a dependent table's rows can be updated when a
row of the parent table is the object of a delete or propagated delete operation.
Mods for generated columns (check with Rick, please):
If any of the referencing columns is generated, SET DEFAULT or SET NULL is not allowed.
If a column in the referencing table modified by the SET NULL or SET DEFAULT referential
actions are part of the expression of (another) generated in the impacted row, that column
will get updated too.
> 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.