《ISO-9075-13-2003.pdf》由会员分享，可在线阅读，更多相关《ISO-9075-13-2003.pdf（220页珍藏版）》请在三一文库上搜索。
1、ICS 35.060 Ref. No. ISO/IEC 9075-13:2003/Cor.1:2005(E) ISO/IEC 2005 All rights reserved Published in Switzerland INTERNATIONAL STANDARD ISO/IEC 9075-13:2003 TECHNICAL CORRIGENDUM 1 Published 2005-11-15 INTERNATIONAL ORGANIZATION FOR STANDARDIZATION ORGANISATION INTERNATIONALE DE NORMALISATION INTERN
2、ATIONAL ELECTROTECHNICAL COMMISSION COMMISSION LECTROTECHNIQUE INTERNATIONALE Information technology Database languages SQL Part 13: SQL Routines and Types Using the JavaTM Programming Language (SQL/JRT) TECHNICAL CORRIGENDUM 1 Technologies de linformation Langages de base de donnes SQL Partie 13: R
3、outines et types utilisant le langage de programmation JavaTM (SQL/JRT) RECTIFICATIF TECHNIQUE 1 Technical Corrigendum 1 to ISO/IEC 9075-13:2003 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange. Statement of purpose
4、for rationale A statement indicating the rationale for each change to ISO/IEC 9075-13:2003 is included. This is to inform the users of ISO/IEC 9075-13:2003 why it was judged necessary to change the original wording. In many cases, the reason is editorial or to clarify the wording; in some cases, it
5、is to correct an error or an omission in the original wording. Notes on numbering Where this Technical Corrigendum introduces new Syntax, Access, General, and Conformance Rules, the new rules have been numbered as follows: Rules inserted between, for example, Rules 7) and 8) are numbered 7.1), 7.2),
6、 etc. or 7)a.1), 7)a.2), etc. Those inserted before Rule 1) are numbered 0.1), 0.2, etc. Where this Technical Corrigendum introduces new subclauses, the new subclauses have been numbered as follows: Subclauses inserted between, for example, 4.3.2 and 4.3.3 are numbered 4.3.2a, 4.3.2b, etc. Those ins
7、erted before, for example, 4.3.1 are numbered 4.3.0, 4.3.0a, etc. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 00:06:30 MDTNo reproduction or networking permitted withou
8、t license from IHS -,-,- ISO/IEC 9075-13:2003/Cor.1:2005(E) ii ISO/IEC 2005 All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 00:06:30 MDTNo reproduction
9、or networking permitted without license from IHS -,-,- ISO/IEC 9075-13:2003/Cor.1:2005(E) ISO/IEC 2005 All rights reserved iii ContentsPage Foreword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10、. . . . . . . . . . 1 4Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 4.3Java class name resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11、. . . . . . . . . . . . . . . . . . . . . . . . . . . 1 4.6Unhandled Java exceptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4.10Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 8Additional common elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 8.2. . . . . . . . . . . . . . . . . . . . . . . . . . .
13、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 8.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 9Schema definition and manipulation. . . . . . . . . . . . . .
14、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 9.4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 9.8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15、. . . . . . . . . . . . . . . . . . . . . . . . . . 4 10Access control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 10.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 11Built-in procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 11.1SQLJ.INSTALL_JAR procedure. . . . . . . . . . . . . . . .
17、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 11.3SQLJ.REMOVE_JAR procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 11.4SQLJ.ALTER_JAVA_PATH procedure. . . . . . . . . . . .
18、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 13Information Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 13.2JARS view. . . . . . . . . . . . . . . . . . .
19、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 14Definition Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 14.2JARS base
20、table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 15Status codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21、 . . . . . . . . . . . 9 15.1Class and subclass values for uncaught Java exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 15.2SQLSTATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22、. . . . . . . . . . . . . . . . . 9 Annex BImplementation-defined elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Annex ERoutines tutorial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23、 . . . . . . . . . . . . . . . . 10 E.21Exceptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Copyright International Organization for Standardization Provided by IHS under license with I
24、SO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 00:06:30 MDTNo reproduction or networking permitted without license from IHS -,-,- Tables TablePage 2SQLSTATE class and subclass values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25、. . . . . . . . . . . . . . . . . . . 9 ISO/IEC 9075-13:2003/Cor.1:2005(E) iv ISO/IEC 2005 All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 00:06:30 MDTN
26、o reproduction or networking permitted without license from IHS -,-,- ISO/IEC 9075-13:2003/Cor.1:2005(E) ISO/IEC 2005 All rights reserved 1 TECHNICAL CORRIGENDUM 1 Foreword 1.Rationale:Remove incorrect reference to obsolete part. In the 7th paragraph, delete the 5th bullet. 4Concepts 4.3Java class n
27、ame resolution 1.Rationale:Describe a JARs SQL-Java path and its relationship to a JAR manifests Class-Path attributes. Replace the 2nd paragraph with: When JARs appear in the CLASSPATH, an ability exists for further effective extension of that CLASS- PATH. Additional JARs will be included in the cl
28、ass resolution process when a JAR in the CLASSPATH has a manifest specifying one or more Class-Path attributes. A Class-Path attribute provides relative URLs of additional JARs. These Class-Path attribute URLs are relative to the source, for example the directory containing the JAR whose manifest is
29、 then being processed. A full URL, for example a file:/ or http:/ format URL, is not allowed in a Class-Path attribute. The JARs enumerated by Class- Path attributes extend the CLASSPATH. When a JVM is transitioned to being effectively within an SQL-environment, the problem of managing the JVMs clas
30、s name resolution continues to exist, but with a change in emphasis. One important change is that an installed JAR manifests Class-Path attributes cannot be honored. No relative URL has meaning when the source of the current JAR is given by a , , and . To allow the creators of Java applications a gr
31、eater degree of control over class name resolution, and the added security associated with that control, a Class-Path attribute-like mechanism is defined to be a property of the JARs containing the Java applications, rather than as an environmental variable of the current session (such as, for examp
32、le, CURRENT_PATH for dynamic statements). This mechanism, referred to as a JARs SQL-Java path, provides a means for owners of installed JARs to control the class resolution process that the CLASSPATH and Class-Path attributes give users and creators of JARs outside an SQL-environment. But, note that
33、 these two mechanisms are only similar, they are not identical. If, while an external Java routine is being executed, a previously unseen class reference is encountered, that class is searched for in the JAR containing the definition of the currently executing class, and, if it is not found, the cla
34、ss will be sought in the manner specified by the SQL-Java path associated with that JAR (if any). Information technology Database languages SQL Part 13: SQL Routines and Types Using the JavaTM Programming Language (SQL/JRT) Copyright International Organization for Standardization Provided by IHS und
35、er license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 00:06:30 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 9075-13:2003/Cor.1:2005(E) 2 ISO/IEC 2005 All rights reserved 4.6Unhandled Java exceptions 1.Rationale:Remove
36、 the requirement that an SQLSTATE must be of class “38”, external routine exception. Replace the 2nd paragraph with: The message text may be specified in the Java exception specified in the Java throw statement. If the Java exception is an instance of java.sql.SQLException, or a subtype of that type
37、, then it may also specify an SQLSTATE value. If the Java exception is not an instance of java.sql.SQLException, or if that exception does not specify an SQLSTATE value, then the default SQL exception condition for an uncaught Java exception is raised. See Subclause 15.1, “Class and subclass values
38、for uncaught Java exceptions”. 4.10Privileges 1.Rationale:Cannot have a privilege on a trigger, and there is no such thing as an SQL-invoked routine module. Replace 2nd paragraph, 1st bullet The identification of the base table, view, column, domain, character set, collation, transliteration, user-d
39、efined type, table/method pair, SQL-invoked routine, sequence generator, or JAR that the descriptor describes. 8Additional common elements 8.2 1.Rationale:Make reference to a JARs descriptor, and clarify the relevance of a JAR manifests Class-Path attributes. Replace General Rule 1) with: 1)When a J
40、ava class CJ in a JAR J is executed in an SQL-implementation, let P be the SQL-Java path from Js JAR descriptor. NOTE 8.1 A JAR descriptors SQL-Java path is set by an invocation of the SQLJ.ALTER_JAVA_PATH procedure. Copyright International Organization for Standardization Provided by IHS under lice
41、nse with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/03/2007 00:06:30 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 9075-13:2003/Cor.1:2005(E) ISO/IEC 2005 All rights reserved 3 2)No Class-Path attribute in Js manifest affects class
42、 resolution. Every static or dynamic reference in CJ to a class with the name CN that is not a system class and is not contained in J is resolved as follows. For each PE (if any) in P, in the order in which they were specified: 8.3 1.Rationale:Clarify the invocation of the Syntax Rules of Subclause
43、8.6, “Java routine signature determination”. Replace Syntax Rule 1) b) with: 1). b)If validation of the has been implementation-defined to be performed by , then the Syntax Rules of Subclause 8.6, “Java routine signature determination”, are applied with as the syntactic element, 0 (zero) as the meth
44、od specification index, and SR as the subject routine. 2.Rationale:Clarify the invocation of Subclause 9.2, “Store assignment”. Replace General Rule 7) c) i) 4) with: 7). c). i). 4)Let RESULT be an arbitrary site of declared type ERT. The rules of Subclause 9.2, “Store assignment”, in ISO/IEC 9075-2
45、 are applied with SSFV as SOURCE and RESULT as TARGET. The result of the is the value of RESULT. No further General Rules of this Subclause are applied. 9Schema definition and manipulation 9.4 1.Rationale:Clarify the invocation of the Syntax Rules of Subclause 8.6, “Java routine signature determinat
46、ion”. 2.Rationale:Make reference to a JARs descriptor, and clarify the relevance of a JAR manifests Class-Path attributes. Replace the lead text of General Rule 2) with: Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001,
47、 User=Wing, Bernie Not for Resale, 04/03/2007 00:06:30 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 9075-13:2003/Cor.1:2005(E) 4 ISO/IEC 2005 All rights reserved 14)Insert after SR 9)b)xv) If UDT is an external Java data type and validation of the has been implem
48、entation-defined to be performed by , then the Syntax Rules of Subclause 8.6, “Java routine signature determination” are applied with as the syntactic element, i as the method specification index, and no subject routine. 9.8 1.Rationale:Clarify the invocation of the Syntax Rules of Subclause 8.6, “Java routine signature determination”. Replace Syntax Rule 16) with: 16)Insert after SR 21) If R is an external Jav