db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6571) Document deferrable constraints
Date Thu, 22 May 2014 14:03:03 GMT

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

Dag H. Wanvik commented on DERBY-6571:
--------------------------------------

Probably at the end of section http://db.apache.org/derby/docs/10.10/devguide/cdevconcepts838850.html
would be a good place to mention that any outstanding violations of deferred constraints will
be checked at commit time, so the Connection#commit may throw an error (SQL state "23506"
for unique/primary key, "23514" for check , or "23516" for foreign key).


> Document deferrable constraints
> -------------------------------
>
>                 Key: DERBY-6571
>                 URL: https://issues.apache.org/jira/browse/DERBY-6571
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>             Fix For: 10.11.0.0
>
>         Attachments: DERBY-6571-2.diff, DERBY-6571-2.stat, DERBY-6571-2.zip, DERBY-6571.diff,
DERBY-6571.stat, DERBY-6571.zip
>
>
> The contents of functional specification attached to DERBY-532 should be included in
the documentation.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message