[jira] Updated: (DERBY-3945) Generation clauses which mention user-coded functions may produce different resuls depending on who performs the triggering INSERT/UPDATE

["Rick Hillegas (JIRA)" <ji...@apache.org>]

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

Rick Hillegas updated DERBY-3945:
---------------------------------

    Attachment: derby-3945-02-aa-javadoc.diff

Thanks for the review, Dag. Attaching derby-3945-02-aa-javadoc.diff, which address the javadoc issue. Committed at subversion revision 722177.

> Generation clauses which mention user-coded functions may produce different resuls depending on who performs the triggering INSERT/UPDATE
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3945
>                 URL: https://issues.apache.org/jira/browse/DERBY-3945
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-3945-01-aa-functionSchema.diff, derby-3945-02-aa-javadoc.diff, zz.sql
>
>
> This is similar to DERBY-3944. The compiler uses the current schema in order to resolve unqualifed function names when preparing INSERT/UPDATE statement. This means that a generation clause may evaluate differently depending on who invokes the triggering INSERT/UPDATE statement. This violates the requirement that generation clause should be deterministic (see part 2 of the ANSI/ISO standard, section 4.16.
> Hopefully, the same patch will fix both DERBY-3944 and this issue.

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