[
https://issues.apache.org/jira/browse/DERBY-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007359#comment-14007359
]
Rick Hillegas commented on DERBY-6580:
--------------------------------------
Hi Dag,
That's an interesting question. The SYSCS_UTIL.SYSCS_PEEK_AT_IDENTITY function
is the new, concurrent way to get the information which customers used to get
by querying SYS.SYSCOLUMNS.AUTOINCREMENTVALUE, just as
SYSCS_UTIL.SYSCS_PEEK_AT_SEQUENCE is the concurrent way to get the information
bounded by querying SYS.SYSSEQUENCES.CURRENTVALUE. Since you can get a fuzzy
approximation of this information by querying the system tables directly (and
we don't want people to do that), I don't see a great deal of value in
restricting the execute privilege on these functions.
Derby and JDBC treat metadata as world-readable. Maybe Derby and JDBC are wrong
here and we should explore whether we could tighten up the access controls on
metadata in general.
Thanks,
-Rick
> 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: 10.11.0.0
> 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:
> BIGINT SYSCS_UTIL.SYSCS_PEEK_AT_IDENTITY
> ( IN SCHEMANAME VARCHAR(128), IN TABLENAME VARCHAR(128) )
> All users have permission to run this function.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
