db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4442) Evaluation of default value and identity in an INSERT result set evaluated too early.
Date Mon, 30 Nov 2009 13:45:20 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-4442:
--------------------------------------

     Issue & fix info:   (was: [Patch Available])
    Affects Version/s: 10.5.3.0
        Fix Version/s: 10.6.0.0

Thanks Dag. I've committed the patch to trunk with revision 885421, since it looks like DERBY-4426
is more or less ready for commit too.

I'll leave this issue open until I've investigated if we can back out the fixes for some of
the other issues linked to this one now. I think at least there were some asserts that were
loosened to accept untyped nulls (placeholders for the identity values) at odd places in the
code, and these could now be made stricter again to potentially catch other errors.

> Evaluation of default value and identity in an INSERT result set evaluated too early.
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-4442
>                 URL: https://issues.apache.org/jira/browse/DERBY-4442
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.3.0
>            Reporter: Dag H. Wanvik
>            Assignee: Knut Anders Hatlen
>             Fix For: 10.6.0.0
>
>         Attachments: always_prn.diff, d4442-1a.diff, d4442-1a.stat, d4442-1b.diff, insert.diff
>
>
> In contrast to generated column, which are evaluated when the next row from the result
set to be inserted, currently default values and identity columns are generated "early", that
is as part of avaluating the subquery (SELECT or VALUES as the case may be). 
> This does not currently cause a user visible bug in Derby, but it lies behind DERBY-3
and the effect Bryan observed in DERBY-4.
> Additionally, "early" computation has given rise to much special handling and ensuing
bugs, cf. DERBY-1644, DERBY-4413, DERBY-4419, DERBY-4425 and others.
> DERBY-4397 requires this fix for correct behaviour with INSERT.
> See also
> https://issues.apache.org/jira/browse/DERBY-4413?focusedCommentId=12769532&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12769532

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


Mime
View raw message