[
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.
