You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Stan Bradbury (JIRA)" <de...@db.apache.org> on 2006/08/30 00:24:22 UTC
[jira] Created: (DERBY-1779) Move class loading utilities into
SYSCS_UTIL with the other system procedures and remove the SQLJ schema.
Move class loading utilities into SYSCS_UTIL with the other system procedures and remove the SQLJ schema.
-----------------------------------------------------------------------------------------------------------
Key: DERBY-1779
URL: http://issues.apache.org/jira/browse/DERBY-1779
Project: Derby
Issue Type: Improvement
Affects Versions: 10.1.3.1, 10.1.2.1, 10.0.2.1
Reporter: Stan Bradbury
Priority: Minor
The system procedures install_jarfile, replace_jar and remove_jar are all methods in the systemProcedures class and like the other methods of that class implemented as build-in system procedures should be implemented in the schema SYSCS_UTIL. They currently exist in the schema SQLJ and this name causes confusion about support of the SQLJ language defined by the ISO and ANSI standard. Best not to use SQL J as an identifier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1779) Move class loading utilities into
SYSCS_UTIL with the other system procedures and remove the SQLJ schema.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1779?page=comments#action_12431394 ]
Daniel John Debrunner commented on DERBY-1779:
----------------------------------------------
These are the SQL standard defined names for the procedures including the SQLJ schema name.
> Move class loading utilities into SYSCS_UTIL with the other system procedures and remove the SQLJ schema.
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1779
> URL: http://issues.apache.org/jira/browse/DERBY-1779
> Project: Derby
> Issue Type: Improvement
> Affects Versions: 10.0.2.1, 10.1.2.1, 10.1.3.1
> Reporter: Stan Bradbury
> Priority: Minor
>
> The system procedures install_jarfile, replace_jar and remove_jar are all methods in the systemProcedures class and like the other methods of that class implemented as build-in system procedures should be implemented in the schema SYSCS_UTIL. They currently exist in the schema SQLJ and this name causes confusion about support of the SQLJ language defined by the ISO and ANSI standard. Best not to use SQL J as an identifier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1779) Move class loading utilities into
SYSCS_UTIL with the other system procedures and remove the SQLJ schema.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1779?page=all ]
Daniel John Debrunner resolved DERBY-1779.
------------------------------------------
Resolution: Invalid
Section 11 from
— SQL — Part 13: SQL Routines
and Types Using the Java™ Programming Language (SQL/JRT)
defines these procedures and the SQLJ schema
> Move class loading utilities into SYSCS_UTIL with the other system procedures and remove the SQLJ schema.
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1779
> URL: http://issues.apache.org/jira/browse/DERBY-1779
> Project: Derby
> Issue Type: Improvement
> Affects Versions: 10.0.2.1, 10.1.2.1, 10.1.3.1
> Reporter: Stan Bradbury
> Priority: Minor
>
> The system procedures install_jarfile, replace_jar and remove_jar are all methods in the systemProcedures class and like the other methods of that class implemented as build-in system procedures should be implemented in the schema SYSCS_UTIL. They currently exist in the schema SQLJ and this name causes confusion about support of the SQLJ language defined by the ISO and ANSI standard. Best not to use SQL J as an identifier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira