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-6580) Document the new SYSCS_UTIL.SYSCS_PEEK_AT_IDENTITY function
Date Fri, 23 May 2014 18:13:03 GMT

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

Dag H. Wanvik commented on DERBY-6580:

A priori I would expect Derby to limit access to system tables to object for which the user
has read and/or execute privileges. But probably that would entail different visibility for
different rows of some system tables, behooving us to make wrappers instead of allowing direct
access to the system tables. I wonder how the visibility/access is defined for the information
schema in the standard...

> Document the new SYSCS_UTIL.SYSCS_PEEK_AT_IDENTITY function
> -----------------------------------------------------------
>                 Key: DERBY-6580
>                 URL: https://issues.apache.org/jira/browse/DERBY-6580
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
> The work on DERBY-6542 has introduced a new system function. This function is used to
check the next value which will be issued for an identity column. It is similar to the existing
SYSCS_UTIL.SYSCS_PEEK_AT_SEQUENCE function for sequences. We need to document this new function:
> All users have permission to run this function.

This message was sent by Atlassian JIRA

View raw message