[
https://issues.apache.org/jira/browse/DERBY-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469517
]
Rick Hillegas commented on DERBY-2252:
--------------------------------------
Thanks for the feedback, Dan. I have incorporated your improvements in the next
revs of this spec and the companion spec for phase 3 (DERBY-2253). I will wait
a bit to collect more feedback before posting the new revs.
1) I added signatures to the syntax of the EXTERNAL NAMEs as you suggested.
2) I clarified class/method resolution rules.
3) The System Tables section now explains my reasons for tracking jar IDs in a
new SYSALIASES.FILEID column. The issue here was not dependency tracking but
rather the construction of the jar-specific classpath. That is addressed in the
phase 3 spec but I can see that some explanation is needed in this spec too. I
agree that we could reconstruct this information from the dependency system.
But I think that modelling the jar ID in SYSALIASES will make it more
straightforward to construct the jar-specific classpath and it will make it
easier for tech support to figure out that classpath from the catalogs.
4) I have improved the REVOKE USAGE explanation as you suggested.
> Add Jar IDs to the EXTERNAL names in routine declarations
> ---------------------------------------------------------
>
> Key: DERBY-2252
> URL: https://issues.apache.org/jira/browse/DERBY-2252
> Project: Derby
> Issue Type: New Feature
> Components: Security, SQL
> Reporter: Rick Hillegas
> Attachments: jarIDs.html
>
>
> This is phase (2) of the work described in the master JIRA DERBY-2206,
> motivated by the wiki page http://wiki.apache.org/db-derby/JavaRoutineSecurity
> This task involves adding Jar IDs to the external names in CREATE PROCEDURE
> and CREATE FUNCTION statements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
