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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2007/10/09 14:37:50 UTC
[jira] Updated: (DERBY-3013) column-definition WITH DEFAULT should
accept CURRENT_USER, SESSION_USER in addition to USER
[ https://issues.apache.org/jira/browse/DERBY-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3013:
---------------------------------
Attachment: DERBY-3013.stat
DERBY-3013.diff
Uploading a patch that allows CURRENT_USER and SESSION_USER
as DEFAULT in addition to USER.
Added testcases to lang/columnDefaults.sql.
Running regression tests now.
> column-definition WITH DEFAULT should accept CURRENT_USER, SESSION_USER in addition to USER
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-3013
> URL: https://issues.apache.org/jira/browse/DERBY-3013
> Project: Derby
> Issue Type: Improvement
> Affects Versions: 10.4.0.0
> Reporter: Dag H. Wanvik
> Priority: Minor
> Attachments: DERBY-3013.diff, DERBY-3013.stat, repro.sql
>
>
> Presently, Derby accepts WITH DEFAULT USER, but although CURRENT_USER
> and SESSION_USER are otherwise used in Derby (see
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj42476.html), they can
> not presently be used in the column definition. Only USER is allowed.
> ISO/IEC 9075-2:2003, section 11.5 <default clause> specifies that all
> of the above can be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.