[
https://issues.apache.org/jira/browse/DERBY-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469544
]
Daniel John Debrunner commented on DERBY-2252:
----------------------------------------------
Thanks for putting up with all my comments Rick.
> 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.
I look forward to seeing that, I don't see how the definition of an entry point
is related to the jar specific class path, but I haven't thought a lot about
how to implement it.
> 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.
