[ https://issues.apache.org/jira/browse/DERBY-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555043#comment-13555043 ]
Kristian Waagan commented on DERBY-6022: ---------------------------------------- Looks like code from this issue causes/triggers a test failure on some platforms. See http://download.java.net/javadesktop/derby/javadb-5571080-report/javadb-5571080-3575124-details.html . Low-level cause reported as: Caused by: java.lang.NullPointerException at org.apache.derby.impl.sql.compile.AggregateNode.resolveAggregate(AggregateNode.java:457) at org.apache.derby.impl.sql.compile.StaticMethodCallNode.resolveRoutine(StaticMethodCallNode.java:664) at org.apache.derby.impl.sql.compile.StaticMethodCallNode.bindExpression(StaticMethodCallNode.java:210) at org.apache.derby.impl.sql.compile.JavaToSQLValueNode.bindExpression(JavaToSQLValueNode.java:237) at org.apache.derby.impl.sql.compile.ResultColumn.bindExpression(ResultColumn.java:737) at org.apache.derby.impl.sql.compile.ResultColumnList.bindExpressions(ResultColumnList.java:831) at org.apache.derby.impl.sql.compile.RowResultSetNode.bindExpressions(RowResultSetNode.java:261) at org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(DMLStatementNode.java:227) at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(DMLStatementNode.java:140) at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(CursorNode.java:267) at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java:400) at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.java:99) at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(GenericLanguageConnectionContext.java:1103) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(EmbedPreparedStatement.java:134) > Add a system procedure for (un)registering optional packages of Derby tools. > ---------------------------------------------------------------------------- > > Key: DERBY-6022 > URL: https://issues.apache.org/jira/browse/DERBY-6022 > Project: Derby > Issue Type: Improvement > Components: SQL, Tools > Affects Versions: 10.10.0.0 > Reporter: Rick Hillegas > Attachments: derby-6022-01-aa-registerToolProc.diff, > derby-6022-02-aa-dbmdWrapper.diff, derby-6022-03-aa-foreignDBviews.diff, > derby-6022-04-aa-customTool.diff > > > Now that vararg routines have been added to Derby (see DERBY-3069), I would > like to add a new vararg system procedure for registering and unregistering > optional packages of Derby tools. For starters, these would be tools which > aren't checked into the Derby codeline but are just attached to various > JIRAs. These tools are: > o DBMDWrapper (DERBY-3973 and DERBY-5967) - This tool creates functions and > table functions for all of the DatabaseMetaData methods so that you can write > complicated queries which join and filter JDBC metadata. > o ForeignTableVTI (DERBY-4962) - This tool creates views against foreign > databases so that you can bulk-import foreign data into Derby without > indirecting through csv files. > It also may be possible to use this approach to expose the log and data file > reading tools attached to DERBY-5195 and DERBY-5201. > The new system procedure would look like this: > create procedure syscs_util.syscs_register_tool > ( > toolName varchar( 32672 ), > boolean register, > optionalArgs varchar( 32672 ) ... > ) > language java parameter style derby modifies sql data > external name 'willFigureOutWhereToPutThis'; > The arguments would have these meanings: > o toolName - A name specific to the tool. > o register - True means "register the tool" and false means "unregister the > tool". > o optionalArgs - Each tool could have its own variable set of additional > configuration parameters. > By default, only the DBO could run this procedure. The DBO could grant > execute permission to other users. > The known tool names and their optional parameters would be documented in the > Derby Reference Manual in the section on syscs_util.syscs_register_tool. > I am thinking that we should put the optional tools themselves in > derbytools.jar. We might want to document all of the optional tools in the > Tools Guide, although I can see arguments for documenting some tools in the > Admin Guide. > I would appreciate other people's thoughts about this proposal. > Thanks, > -Rick -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira