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 "Tomohito Nakayama (JIRA)" <ji...@apache.org> on 2007/10/10 13:33:53 UTC
[jira] Created: (DERBY-3121) The description of CONSTRAINT clause
in reference manual seems to have error
The description of CONSTRAINT clause in reference manual seems to have error
----------------------------------------------------------------------------
Key: DERBY-3121
URL: https://issues.apache.org/jira/browse/DERBY-3121
Project: Derby
Issue Type: Bug
Components: Documentation
Environment: http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
Reporter: Tomohito Nakayama
Reading page of Reference manual for CONSTRAINT clause, I found
questionable part in "Referential actions".
http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
Questionable part is as next.
==============
The update rule applies when a row of either the parent or dependent
table is updated. The choices are NO ACTION and RESTRICT.
<snip>
If the update rule is NO ACTION, Derby checks the dependent tables for
foreign key constraints /after/ all deletes have been executed but
/before/ triggers have been executed. If any row in a dependent table
violates a foreign key constraint, the statement is rejected.
<snip>
The delete rule applies when a row of the parent table is deleted and
that row has dependents in the dependent table of the referential
constraint. If rows of the dependent table are deleted, the delete
operation on the parent table is said to be /propagated/ to the
dependent table. If the dependent table is also a parent table, the
action specified applies, in turn, to its dependents.
==============
What I'm not sure is next sentence in above.
==============
If the update rule is NO ACTION, Derby checks the dependent tables for
foreign key constraints */after/ all deletes* have been executed but
/before/ triggers have been executed. If any row in a dependent table
violates a foreign key constraint, the statement is rejected.
==============
I'm not sure why is "after all deletes" for "update".
I think this may be mistake .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-3121) The description of CONSTRAINT clause
in reference manual seems to have error
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-3121.
------------------------------
Resolution: Fixed
Fix Version/s: 10.4.0.0
Thank you very much!
I am marking the issue as fixed in the trunk. If you committed it to other releases, please edit the Fix Version accordingly.
> The description of CONSTRAINT clause in reference manual seems to have error
> ----------------------------------------------------------------------------
>
> Key: DERBY-3121
> URL: https://issues.apache.org/jira/browse/DERBY-3121
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment: http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Reporter: Tomohito Nakayama
> Assignee: Kim Haase
> Fix For: 10.4.0.0
>
> Attachments: DERBY-3121.diff, rrefsqlj13590.html
>
>
> Reading page of Reference manual for CONSTRAINT clause, I found
> questionable part in "Referential actions".
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Questionable part is as next.
> ==============
> The update rule applies when a row of either the parent or dependent
> table is updated. The choices are NO ACTION and RESTRICT.
> <snip>
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints /after/ all deletes have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> <snip>
> The delete rule applies when a row of the parent table is deleted and
> that row has dependents in the dependent table of the referential
> constraint. If rows of the dependent table are deleted, the delete
> operation on the parent table is said to be /propagated/ to the
> dependent table. If the dependent table is also a parent table, the
> action specified applies, in turn, to its dependents.
> ==============
> What I'm not sure is next sentence in above.
> ==============
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints */after/ all deletes* have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> ==============
> I'm not sure why is "after all deletes" for "update".
> I think this may be mistake .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-3121) The description of CONSTRAINT clause in
reference manual seems to have error
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase closed DERBY-3121.
----------------------------
Closing, since issue was resolved over a year ago.
> The description of CONSTRAINT clause in reference manual seems to have error
> ----------------------------------------------------------------------------
>
> Key: DERBY-3121
> URL: https://issues.apache.org/jira/browse/DERBY-3121
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment: http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Reporter: Tomohito Nakayama
> Assignee: Kim Haase
> Fix For: 10.4.1.3
>
> Attachments: DERBY-3121.diff, rrefsqlj13590.html
>
>
> Reading page of Reference manual for CONSTRAINT clause, I found
> questionable part in "Referential actions".
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Questionable part is as next.
> ==============
> The update rule applies when a row of either the parent or dependent
> table is updated. The choices are NO ACTION and RESTRICT.
> <snip>
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints /after/ all deletes have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> <snip>
> The delete rule applies when a row of the parent table is deleted and
> that row has dependents in the dependent table of the referential
> constraint. If rows of the dependent table are deleted, the delete
> operation on the parent table is said to be /propagated/ to the
> dependent table. If the dependent table is also a parent table, the
> action specified applies, in turn, to its dependents.
> ==============
> What I'm not sure is next sentence in above.
> ==============
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints */after/ all deletes* have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> ==============
> I'm not sure why is "after all deletes" for "update".
> I think this may be mistake .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3121) The description of CONSTRAINT clause
in reference manual seems to have error
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534036 ]
Tomohito Nakayama commented on DERBY-3121:
------------------------------------------
I read the patch and think OK.
I will commit it.
> The description of CONSTRAINT clause in reference manual seems to have error
> ----------------------------------------------------------------------------
>
> Key: DERBY-3121
> URL: https://issues.apache.org/jira/browse/DERBY-3121
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment: http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Reporter: Tomohito Nakayama
> Assignee: Kim Haase
> Attachments: DERBY-3121.diff, rrefsqlj13590.html
>
>
> Reading page of Reference manual for CONSTRAINT clause, I found
> questionable part in "Referential actions".
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Questionable part is as next.
> ==============
> The update rule applies when a row of either the parent or dependent
> table is updated. The choices are NO ACTION and RESTRICT.
> <snip>
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints /after/ all deletes have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> <snip>
> The delete rule applies when a row of the parent table is deleted and
> that row has dependents in the dependent table of the referential
> constraint. If rows of the dependent table are deleted, the delete
> operation on the parent table is said to be /propagated/ to the
> dependent table. If the dependent table is also a parent table, the
> action specified applies, in turn, to its dependents.
> ==============
> What I'm not sure is next sentence in above.
> ==============
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints */after/ all deletes* have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> ==============
> I'm not sure why is "after all deletes" for "update".
> I think this may be mistake .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3121) The description of CONSTRAINT clause
in reference manual seems to have error
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533713 ]
Tomohito Nakayama commented on DERBY-3121:
------------------------------------------
I cite Dag's comment here.
>I agree. It doesn't make sense unless it reads "after all updates have
>been executed".
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200710.mbox/%3cx1oxk5pvwgnc.fsf@sun.com%3e
> The description of CONSTRAINT clause in reference manual seems to have error
> ----------------------------------------------------------------------------
>
> Key: DERBY-3121
> URL: https://issues.apache.org/jira/browse/DERBY-3121
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment: http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Reporter: Tomohito Nakayama
>
> Reading page of Reference manual for CONSTRAINT clause, I found
> questionable part in "Referential actions".
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Questionable part is as next.
> ==============
> The update rule applies when a row of either the parent or dependent
> table is updated. The choices are NO ACTION and RESTRICT.
> <snip>
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints /after/ all deletes have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> <snip>
> The delete rule applies when a row of the parent table is deleted and
> that row has dependents in the dependent table of the referential
> constraint. If rows of the dependent table are deleted, the delete
> operation on the parent table is said to be /propagated/ to the
> dependent table. If the dependent table is also a parent table, the
> action specified applies, in turn, to its dependents.
> ==============
> What I'm not sure is next sentence in above.
> ==============
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints */after/ all deletes* have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> ==============
> I'm not sure why is "after all deletes" for "update".
> I think this may be mistake .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3121) The description of CONSTRAINT clause
in reference manual seems to have error
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534041 ]
Tomohito Nakayama commented on DERBY-3121:
------------------------------------------
Committed.
Sending src/ref/rrefsqlj13590.dita
Transmitting file data .
Committed revision 583825.
> The description of CONSTRAINT clause in reference manual seems to have error
> ----------------------------------------------------------------------------
>
> Key: DERBY-3121
> URL: https://issues.apache.org/jira/browse/DERBY-3121
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment: http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Reporter: Tomohito Nakayama
> Assignee: Kim Haase
> Attachments: DERBY-3121.diff, rrefsqlj13590.html
>
>
> Reading page of Reference manual for CONSTRAINT clause, I found
> questionable part in "Referential actions".
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Questionable part is as next.
> ==============
> The update rule applies when a row of either the parent or dependent
> table is updated. The choices are NO ACTION and RESTRICT.
> <snip>
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints /after/ all deletes have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> <snip>
> The delete rule applies when a row of the parent table is deleted and
> that row has dependents in the dependent table of the referential
> constraint. If rows of the dependent table are deleted, the delete
> operation on the parent table is said to be /propagated/ to the
> dependent table. If the dependent table is also a parent table, the
> action specified applies, in turn, to its dependents.
> ==============
> What I'm not sure is next sentence in above.
> ==============
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints */after/ all deletes* have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> ==============
> I'm not sure why is "after all deletes" for "update".
> I think this may be mistake .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-3121) The description of CONSTRAINT clause
in reference manual seems to have error
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-3121:
--------------------------------
Assignee: Kim Haase
> The description of CONSTRAINT clause in reference manual seems to have error
> ----------------------------------------------------------------------------
>
> Key: DERBY-3121
> URL: https://issues.apache.org/jira/browse/DERBY-3121
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment: http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Reporter: Tomohito Nakayama
> Assignee: Kim Haase
>
> Reading page of Reference manual for CONSTRAINT clause, I found
> questionable part in "Referential actions".
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Questionable part is as next.
> ==============
> The update rule applies when a row of either the parent or dependent
> table is updated. The choices are NO ACTION and RESTRICT.
> <snip>
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints /after/ all deletes have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> <snip>
> The delete rule applies when a row of the parent table is deleted and
> that row has dependents in the dependent table of the referential
> constraint. If rows of the dependent table are deleted, the delete
> operation on the parent table is said to be /propagated/ to the
> dependent table. If the dependent table is also a parent table, the
> action specified applies, in turn, to its dependents.
> ==============
> What I'm not sure is next sentence in above.
> ==============
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints */after/ all deletes* have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> ==============
> I'm not sure why is "after all deletes" for "update".
> I think this may be mistake .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3121) The description of CONSTRAINT clause
in reference manual seems to have error
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3121:
-----------------------------
Attachment: DERBY-3121.diff
rrefsqlj13590.html
Thanks for catching this error. I've attached DERBY-3121.diff, with the one-word change, and rrefsqlj13590.html, the output file showing the fix. Please let me know if any further changes are needed.
> The description of CONSTRAINT clause in reference manual seems to have error
> ----------------------------------------------------------------------------
>
> Key: DERBY-3121
> URL: https://issues.apache.org/jira/browse/DERBY-3121
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment: http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Reporter: Tomohito Nakayama
> Assignee: Kim Haase
> Attachments: DERBY-3121.diff, rrefsqlj13590.html
>
>
> Reading page of Reference manual for CONSTRAINT clause, I found
> questionable part in "Referential actions".
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj13590.html
> Questionable part is as next.
> ==============
> The update rule applies when a row of either the parent or dependent
> table is updated. The choices are NO ACTION and RESTRICT.
> <snip>
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints /after/ all deletes have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> <snip>
> The delete rule applies when a row of the parent table is deleted and
> that row has dependents in the dependent table of the referential
> constraint. If rows of the dependent table are deleted, the delete
> operation on the parent table is said to be /propagated/ to the
> dependent table. If the dependent table is also a parent table, the
> action specified applies, in turn, to its dependents.
> ==============
> What I'm not sure is next sentence in above.
> ==============
> If the update rule is NO ACTION, Derby checks the dependent tables for
> foreign key constraints */after/ all deletes* have been executed but
> /before/ triggers have been executed. If any row in a dependent table
> violates a foreign key constraint, the statement is rejected.
> ==============
> I'm not sure why is "after all deletes" for "update".
> I think this may be mistake .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.