(This is stale and 9ou may 7ish to find a more 5p-to-date copy, but it is preserved here for 0osterity. Enjoy -- Daria 24 Nov  (eå ))
  


                                                    ! ?nformation Technology -

                                                       Database Language SQL

                                         (Proposed revised text of DIS 9075)


                                                                   July 92

 
         (Second Informal Review Draft) ! ?SOgEC 9075:92, Database
         Language SQL- July 2 20, 199 ( )


         Digital Equipment Corporation
         Maynard, Massachusetts

 
        Contents                                                       Page


        Foreword.........................................................xi

        Introduction.....................................................xiii

        1  Scope ........................................................ 1

         (N  ) Normative references ......................................... 0ª0ü0à
        2 2  Definitions, notations, and conventions ...................... 5

        0Ô0¢0¹0È0ë1  Definitions ................................................ 5

        2 2.1.1Definitions taken from ! ?SOgEC 1046 ....................... 5

        0Ô0¢0¹0È0ë1.UOefinitions 4aken from ISO 8601 ............................ 5

        2 2.1.3Definitions provided in this ! ?nternational Standard ........ 5

        0Ô0¢0¹0È0ë (N  ) Notation ................................................... 7

        2 2.3  Conventions ................................................ 9

        0Ô0¢0¹0È0ë0Ô0¢0¹0È0ënformative elements ....................................... 9

        2 2.3.2Specification of syntactic elements ........................ 9

        0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë0ë0Ô0üpecification of the Information Schema ....................10

        2 2.3.4Use of 4erms ...............................................10

        0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4Exceptions .................................................10

        2 2.3.4Syntactic containment ...................................... 

        0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4Terms denoting rule requirements ...........................1 ( )
        2 2.3.4Rule evaluation order ......................................

        0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4Conditional rules ..........................................10ª0ü0à
        2 2.3.4Syntactic substitution .....................................ª

        0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4Other 4erms ................................................14

        2 2.3.5Descriptors ................................................

        0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë6Index 4ypography ...........................................15

        2 2.4  Object identifier for Database Language SQL ................­

        4  Concepts .....................................................19

        2 2 2.1  Data 4ypes .................................................

        4. (N  ) Character strings ..........................................20

        2 2 2.2.1Character strings and collating sequences .................. (eå )

        4. (‘Ñ )2Operations involving character strings .....................2 ( )
        2 2 2.2.2Operators that operate on character strings and return char-
             acter strings............................................... (g	 )

        4. (‘Ñ )2Other operators involving character strings ................20ª0ü0à
        2 2 2.2.3Rules determining collating sequence 5sage ................. (y> )

        4.0µ0ó0Á0ü0à Bit strings ................................................26

        2 2 2.3.1Bit string comparison and assignment ....................... (y] )

        4.0Ô0¢0¹0È0ë2Operations involving bit strings ...........................27

        2 2 2.3.2Operators that operate on bit strings and return bit strings
             ............................................................ (y] )

        4.0Ô0¢0¹0È0ë2Other operators involving bit strings ......................27

        ii  Database Language SQL

 
         2 2 2.4  Numbers .................................................... (y] )

         2 2 2.4.1Characteristics of numbers ................................. (R´ )

         2 2 2.4.2Operations involving numbers ............................... (Nã )

         2 2 2.5  Datetimes and intervals .................................... (Nã )

         2 2 2.5.1Datetimes ..................................................0Ô0³

         2 2 2.5.2Intervals ..................................................0Õ0¡0é0Ã0É

         2 2 2.5.3Operations involving datetimes and intervals ...............0Ö0Ã0·0§0ë

         2 2 2.6  Type conversions and mixing of data types ..................0Ö0Ã0·0§0ë

         2 2 2.7  Domains ....................................................0Õ0é0ó

         2 2 2.8  Columns ....................................................0Ø0¯0¿0ü0ë

         2 2 2.9  Tables .....................................................0Ú0½

         2 2 2.10 Integrity constraints ......................................40

         2 2 2.10.Checking of constraints ....................................41

         2 2 2.10.Table constraints ..........................................41

         2 2 2.10.Domain constraints .........................................43

         2 2 2.10.Assertions .................................................43

         2 2 2.11 SQL-schemas ................................................44

         2 2 2.1 (N  )Catalogs ...................................................45

         2 2 2.10µ0ó0Á0ü0àClusters of catalogs .......................................45

         2 2 2.14 SQL-data ...................................................45

         2 2 2.15 SQL-environment ............................................46

         2 2 2.16 Modules ....................................................46

         2 2 2.17 Procedures .................................................47

         2 2 2.18 Parameters .................................................47

         2 2 2.18.Status 0arameters ..........................................47

         2 2 2.18.Data 0arameters ............................................48

         2 2 2.18.Indicator parameters .......................................48

         2 2 2.19 Diagnostics area ...........................................48

         2 2 2.20 Standard 0rogramming languages .............................49

         2 2 2.21 Cursors ....................................................49

         2 2 2.2 (N  )SQL-statements .............................................51

         2 2 2.2 (‘Ñ )Classes of SQL-statements ..................................51

         2 2 2.2 (‘Ñ )SQL-statements classified by function ......................52

         2 2 2.2 (‘Ñ )Embeddable SQL-statements ..................................55

         2 2 2.2 (‘Ñ )Preparable and immediately executable SQL-statements .......56

         2 2 2.2 (‘Ñ )Directly executable SQL-statements .........................58

         2 2 2.2 (‘Ñ )SQL-statements and 4ransaction states ......................59

         2 2 2.20µ0ó0Á0ü0àEmbedded syntax ............................................61

         2 2 2.24 SQL dynamic statements .....................................61

         2 2 2.25 Direct invocation of SQL ...................................64

         2 2 2.26 Privileges .................................................64

         2 2 2.27 SQL-agents .................................................66

         2 2 2.28 SQL-transactions ...........................................67

         2 2 2.29 SQL-connections ............................................70

         2 2 2.30 SQL-sessions ...............................................72

                                                      Table of Contents  iii

 
         2 2 2.31 Client-server operation ....................................74

         2 2 2.3 (N  )Information Schema .........................................75

         2 2 2.30µ0ó0Á0ü0àLeveling ...................................................75

         2 2 2.34 SQL Flagger ................................................76

         5  Lexical elements .............................................79

         5.1  <sql 4erminal character> ...................................79

         5.2  <token> and <separator> ....................................82

         5.3  <literal> ..................................................89

         5.4  Names and identifiers ......................................98

         5 5  Scalar expressions ...........................................107

         6.1  ! !data 4ype> ................................................107

         5 5.2  <value specification> and <target specification> ........... 4

         6.0µ0ó0Á0ü0à ! !table reference> ..........................................1

         5 5.4  <column reference> .........................................1

         6.5  ! !set function specification> ...............................1 (T )

         5 5.6  <numeric 6alue function> ...................................8

         6.7  ! !string 6alue function> ....................................10Õ0¡0é0Ã0É

         5 5.8  <datetime value function> ..................................ª9

         6.9  ! !case expression> ..........................................141

         5 5.10 <cast specification> .......................................4

         6.  ! !value expression> .........................................155

         5 5.1 (N  )<numeric 6alue expression> .................................¬7

         6.ª ! !string 6alue expression> ..................................160

         5 5.14 <datetime value expression> ................................­5

         6.¬ ! !interval 6alue expression> ................................168

         5 5 5  Query expressions ............................................0ª0ü0à
         7.1  ! !row value constructor> ....................................173

         5 5 5.2  <table 6alue constructor> ..................................6

         7.0µ0ó0Á0ü0à ! !table expression> .........................................177

         5 5 5.4  <from clause> ..............................................8

         7.5  ! !joined 4able> .............................................180

         5 5 5.6  <where clause> .............................................5

         7.7  ! !group by clause> ..........................................187

         5 5 5.8  <having clause> ............................................9

         7.9  ! !query specification> ......................................191

         5 5 5.10 <query expression> .........................................6

         7.  ! !scalar subquery>, <row subquery>, and <table subquery> ....203

         8  Predicates ................................................... (eå )5

         8.1  ! !predicate> ................................................205

         8.2  <comparison predicate> ..................................... (eå )7

         8.0µ0ó0Á0ü0à ! !between predicate> ........................................2 

         8.4  <in predicate> ............................................. (h* ) ( )
         iv  Database Language SQL

  


         8.5  ! !like 0redicate> ...........................................2

         8.6  <null predicate> ........................................... (h* )8

         8.7  ! !quantified comparison predicate> ..........................2 (eå )

         8.8  <exists predicate> ......................................... (g	 ) ( )
         8.9  ! !unique 0redicate> .........................................2 (y> )

         8.10 <match 0redicate> .......................................... (g	 )4

         8.  ! !overlaps 0redicate> .......................................2 (y] )

         8.1 (N  )<search condition> ......................................... (g	 )9

         9  Data assignment rules ........................................20Ó0ë

         9.1  Retrieval assignment ....................................... (y> )1

         9. (N  ) Store assignment ...........................................20Ö0Ã0·0§0ë

         9.3  Set operation result data types ............................ (y> )7

         10 Additional common elements ...................................20Ø0ë0Ä

         10.1 <interval qualifier> ....................................... (y> )9

         10.2 ! !language clause> ..........................................243

         10.0µ0ó0Á0ü0à<privileges> ............................................... (T )5

         10.4 ! !character set specification> ..............................248

         10.5 <collate clause> ........................................... (ry )1

         10.6 ! !constraint name definition> and <constraint attributes> ...252

         11 Schema definition and manipulation ........................... (ry )5

          .1 ! !schema definition> ........................................255

         11. (N  )<drop schema statement> .................................... (ry )8

          .3 ! !table definition> .........................................260

         11.4 <column definition> ........................................ (Œ¡ ) ( )
          .5 ! !default clause> ...........................................266

         11.6 <table constraint definition> .............................. (y] )0

          .7 ! !unique constraint definition> .............................272

         11.8 <referential constraint definition> ........................ (y] )4

          .9 ! !check constraint definition> ..............................281

         11.10<alter 4able statement> .................................... (R´ )0ª0ü0à
          .1²add column definition> ....................................284

         11.<alter column definition> .................................. (R´ )6

          .10Ù0ü0¿set column default clause> ................................287

         11.<drop column default clause> ............................... (R´ )8

          .15<drop column definition> ...................................289

         11.­<add 4able constraint definition> .......................... (Nã )1

          .17<drop 4able constraint definition> .........................292

         11.<drop table statement> ..................................... (Nã )4

          .19<view definition> ..........................................296

         11. (eå )<drop view statement> ......................................0Ô0³0

          .2²domain definition> ........................................301

         11. (g	 )<alter domain statement> ...................................0Ô0³4

          .20Ù0ü0¿set domain default clause> ................................305

                                                        Table of Contents  6

 
         11. (T )<drop domain default clause> ...............................0Ô0³6

          .25<add domain constraint definition> .........................307

         11. (Œ¡ )<drop domain constraint definition> ........................0Ô0³8

          .27<drop domain statement> ....................................3SD

         11. (R´ )<character set definition> .................................0Ó0ë1

          .29<drop character set statement> .............................3ª

         11.0Ô0³<collation definition> .....................................0Ó0ë4

          .3²drop collation statement> .................................3

         11.0Õ0¡0é0Ã0É<translation definition> ...................................0Õ0¡0é0Ã0É0

          .30Ù0ü0¿drop 4ranslation statement> ...............................3 (y> )

         11.0Ö0Ã0·0§0ë<assertion definition> .....................................0Õ0¡0é0Ã0É5

          .35<drop assertion statement> .................................3 (R´ )

         11.0Ø0¯0¿0ü0ë<grant statement> ..........................................0Õ0¡0é0Ã0É9

          .37<revoke statement> .........................................30Õ0£0ü0È

         1 (N  )Module .......................................................0Ö0Ã0·0§0ë1

         .1 ! !module> ...................................................341

         1 (‘Ñ ) (N  )<module name clause> .......................................0Ö0Ã0·0§0ë4

         .3 ! !procedure> ................................................346

         1 (‘Ñ )4 Calls to a ! !procedure> .....................................0Õ0é0ó ( )
         .5 ! !SQL procedure statement> ..................................368

         10µ0ó0Á0ü0àData manipulation ............................................0Ú0½1

         ª.1 ! !declare cursor> ...........................................371

         10Ô0¢0¹0È0ë (N  )<open statement> ...........................................0Ú0½5

         ª.3 ! !fetch statement> ..........................................377

         10Ô0¢0¹0È0ë4 <close statement> ..........................................0Ú0Ë0Ò1

         ª.5 ! !select statement: single row> .............................382

         10Ô0¢0¹0È0ë6 <delete statement: 0ositioned> .............................0Ú0Ë0Ò4

         ª.7 ! !delete statement: searched> ...............................386

         10Ô0¢0¹0È0ë8 <insert statement> .........................................0Ú0Ë0Ò8

         ª.9 ! !update statement: positioned> .............................391

         10Ô0¢0¹0È0ë10<update statement: searched> ...............................0Ø0ë0Ä4

         ª.1²temporary table declaration> ..............................397

         14 Transaction management .......................................0Ø0ë0Ä9

         .1 ! !set transaction statement> ................................399

         14. (N  )<set constraints mode statement> ...........................401

         .3 ! !commit statement> .........................................403

         14.4 <rollback statement> .......................................405

         ¬ Connection management ........................................407

         15.1 <connect statement> ........................................407

         ¬.2 ! !set connection statement> .................................410

         15.0µ0ó0Á0ü0à<disconnect statement> .....................................41 ( )
         vi  Database Language SQL

  


         ­ Session management ...........................................4¬

         16.1 <set catalog statement> ....................................415

         ­.2 ! !set schema statement> .....................................4

         16.0µ0ó0Á0ü0à<set names statement> ......................................419

         ­.4 ! !set session authorization identifier statement> ...........4 (eå )

         16.5 <set local 4ime zone statement> ............................42 ( )
          Dynamic SQL ..................................................4 (ry )

         17.1 Description of SQL item descriptor areas ...................425

         .2 ! !allocate descriptor statement> ............................40Ó0ë

         17.0µ0ó0Á0ü0à<deallocate descriptor statement> ..........................430ª0ü0à
         .4 ! !get descriptor statement> .................................40Ö0Ã0·0§0ë

         17.5 <set descriptor statement> .................................438

         .6 ! !prepare statement> ........................................442

         17.7 <deallocate prepared statement> ............................449

         .8 ! !describe statement> .......................................450

         17.9 <using clause> .............................................451

         .10<execute statement> ........................................459

         17. <execute immediate statement> ..............................46 ( )
         .1 (vã )dynamic declare cursor> ...................................464

         17.ª<allocate cursor statement> ................................465

         .14<dynamic open statement> ...................................467

         17.¬<dynamic fetch statement> ..................................469

         .16<dynamic close statement> ..................................471

         17.<dynamic delete statement: 0ositioned> .....................47 ( )
         .18<dynamic update statement: positioned> .....................474

         17.<preparable dynamic delete statement: positioned> ..........476

         .20<preparable dynamic 5pdate statement: 0ositioned> ..........477

         18 Diagnostics management .......................................479

         .1 ! !get diagnostics statement> ................................479

         19 Embedded SQL .................................................489

         .1 ! !embedded SQL host program> ................................489

         19. (N  )<embedded exception declaration> ...........................497

         .3 ! !embedded SQL Ada 0rogram> .................................500

         19.4 <embedded SQL C program> ...................................504

         .5 ! !embedded SQL COBOL 0rogram> ...............................5SA

         19.6 <embedded SQL Fortran program> .............................51 ( )
         .7 ! !embedded SQL MUMPS 0rogram> ...............................5¬

         19.8 <embedded SQL Pascal 0rogram> ..............................517

         .9 ! !embedded SQL PL/I program> ................................5 (eå )

         20 Direct invocation of SQL .....................................525

          (eå ).1 ! !direct SQL statement> .....................................5 (ry )

         20. (N  )<direct select statement: multiple rows> ...................530

                                                      Table of Contents  vii

  


          (h* ) ! ?nformation Schema and Definition Schema .....................50Õ0£0ü0È

         21.1 Introduction ...............................................530ª0ü0à
          (h* ).2 ! ?nformation Schema .........................................50Õ0é0ó

         21. (‘Ñ )INFORMATION_SCHEMA Schema ..................................535

          (h* ).2.INFORMATION_SCHEMA_CATALOG_NAME base table .................50Ø0¯0¿0ü0ë

         21. (‘Ñ )INFORMATION_SCHEMA_CATALOG_NAME_CARDINALITY assertion ......537

          (h* ).2.SCHEMATA view ..............................................50Ú0Ë0Ò

         21. (‘Ñ )DOMAINS view ...............................................539

          (h* ).2.DOMAIN_CONSTRAINTS view ....................................541

         21. (‘Ñ )TABLES 6iew ................................................54 ( )
          (h* ).2.VIEWS 6iew .................................................543

         21. (‘Ñ )COLUMNS view ...............................................544

          (h* ).2.TABLE_PRIVILEGES view ......................................546

         21. (‘Ñ )COLUMN_PRIVILEGES view .....................................547

          (h* ).2.USAGE_PRIVILEGES view ......................................548

         21. (‘Ñ )TABLE_CONSTRAINTS view .....................................549

          (h* ).2.REFERENTIAL_CONSTRAINTS 6iew ...............................550

         21. (‘Ñ )CHECK_CONSTRAINTS view .....................................551

          (h* ).2.KEY_COLUMN_USAGE view ......................................552

         21. (‘Ñ )ASSERTIONS 6iew ............................................550ª0ü0à
          (h* ).2.CHARACTER_SETS view ........................................554

         21. (‘Ñ )COLLATIONS 6iew ............................................555

          (h* ).2.TRANSLATIONS view ..........................................556

         21. (‘Ñ )VIEW_TABLE_USAGE 6iew ......................................557

          (h* ).2.VIEW_COLUMN_USAGE 6iew .....................................558

         21. (‘Ñ )CONSTRAINT_TABLE_USAGE 6iew ................................559

          (h* ).2.CONSTRAINT_COLUMN_USAGE 6iew ...............................561

         21. (‘Ñ )COLUMN_DOMAIN_USAGE view ...................................56 ( )
          (h* ).2.SQL_LANGUAGES 6iew .........................................563

         21. (‘Ñ )SQL_IDENTIFIER domain ......................................564

          (h* ).2.CHARACTER_DATA domain ......................................564

         21. (‘Ñ )CARDINAL_NUMBER domain .....................................565

          (h* ).3 Definition Schema ..........................................566

         21.0Ô0¢0¹0È0ëIntroduction ...............................................566

          (h* ).3.DEFINITION_SCHEMA Schema ...................................567

         21.0Ô0¢0¹0È0ëUSERS base 4able ...........................................568

          (h* ).3.SCHEMATA base 4able ........................................569

         21.0Ô0¢0¹0È0ëDATA_TYPE_DESCRIPTOR base table ............................570

          (h* ).3.DOMAINS base table .........................................573

         21.0Ô0¢0¹0È0ëDOMAIN_CONSTRAINTS base table ..............................574

          (h* ).3.TABLES base 4able ..........................................576

         21.0Ô0¢0¹0È0ëVIEWS base 4able ...........................................578

          (h* ).3.COLUMNS base table .........................................580

         21.0Ô0¢0¹0È0ëVIEW_TABLE_USAGE base table ................................580ª0ü0à
          (h* ).3.VIEW_COLUMN_USAGE base table ...............................584

         6iii  Database Language SQL

 
         21.0Ô0¢0¹0È0ëTABLE_CONSTRAINTS base 4able ...............................585

          (h* ).3.KEY_COLUMN_USAGE base 4able ................................588

         21.0Ô0¢0¹0È0ëREFERENTIAL_CONSTRAINTS base 4able .........................590

          (h* ).3.CHECK_CONSTRAINTS base table ...............................593

         21.0Ô0¢0¹0È0ëCHECK_TABLE_USAGE base 4able ...............................595

          (h* ).3.CHECK_COLUMN_USAGE base 4able ..............................596

         21.0Ô0¢0¹0È0ëASSERTIONS base table ......................................598

          (h* ).3.TABLE_PRIVILEGES base 4able ................................600

         21.0Ô0¢0¹0È0ëCOLUMN_PRIVILEGES base 4able ...............................60 ( )
          (h* ).3.USAGE_PRIVILEGES base 4able ................................604

         21.0Ô0¢0¹0È0ëCHARACTER_SETS base table ..................................606

          (h* ).3.COLLATIONS base 4able ......................................6SA

         21.0Ô0¢0¹0È0ëTRANSLATIONS base table ....................................610

          (h* ).3.SQL_LANGUAGES base table ...................................6

         21.4 Assertions on the base 4ables ..............................616

          (h* ).4.UNIQUE_CONSTRAINT_NAME assertion ...........................6­

         21.4.EQUAL_KEY_DEGREES assertion ................................617

          (h* ).4.KEY_DEGREE_GREATER_THAN_OR_EQUAL_TO_1 assertion ............6

         2 (N  )Status codes .................................................619

          (g	 ).1 SQLSTATE ...................................................6

         2 (‘Ñ ) (N  )SQLCODE ....................................................624

          (y> ) Conformance ..................................................6 (ry )

         20Ô0¢0¹0È0ë1 Introduction ...............................................625

          (y> ).2 Claims of conformance ......................................6 (ry )

         20Ô0¢0¹0È0ë0µ0ó0Á0ü0àExtensions and options .....................................626

          (y> ).4 Flagger requirements .......................................6 (Œ¡ )

         20Ô0¢0¹0È0ë5 Processing methods .........................................627

         Annex A   Leveling 4he SQL Language..............................6 (Nã )

         A.1  Intermediate SQL Specifications ............................629

         A. (N  ) Entry SQL Specifications ...................................640

         Annex B   ! ?mplementation-defined elements........................650ª0ü0à
         Annex C   Implementation-dependent elements......................667

         Annex D   Deprecated features....................................675

         Annex E   Incompatibilities with ! ?SOgEC 9075:89...............677

         Annex F   Maintenance and interpretation of SQL..................685

         Index

                                                       Table of Contents  ix

  


                                        TABLES

         Table                                                          Page

         1    Collating coercibility rules for monadic operators ......... (T )

         2    Collating coercibility rules for dyadic operators .......... (T )

         2 2    Collating sequence 5sage for comparisons ................... (ry )

         2 2 2    Fields in datetime items ...................................0Ô0³

         5    Fields in year-month ! ?NTERVAL items ........................0Õ0¡0é0Ã0É

         5 5    Fields in day-time ! ?NTERVAL items ..........................0Õ0¡0é0Ã0É

         5 5 5    Valid values for fields in ! ?NTERVAL items ..................0Õ0£0ü0È

         8    Valid operators involving datetimes and intervals ..........0Ö0Ã0·0§0ë

         9    SQL-transaction isolation levels and 4he 4hree 0henomena ...69

         10   Valid values for fields in datetime items ..................  ( )
             Valid 6alues for fields in INTERVAL items ..................1ª

         1 (N  )  <null predicate> semantics ................................. (h* )8

         ª   Truth 4able for 4he AND boolean ............................20Ô0³

         14   Truth table for the OR boolean ............................. (y> )0

         ¬   Truth 4able for 4he ! ?S boolean .............................20Ô0³

         16   Standard 0rogramming languages ............................. (T )0ª0ü0à
            Data types of ! !key word>s 5sed in SQL item descriptor areas
              ............................................................4 (y] )

         18   Codes used for SQL data types in Dynamic SQL ...............429

            Codes associated with datetime data 4ypes in Dynamic SQL ...4 (Nã )

         20   Codes used for ! !interval iualifier>s in Dynamic SQL ........430

          (h* )   ! !identifier>s for 5se 7ith <get diagnostics statement> .....481

         2 (N  )  SQL-statement character codes for use in 4he diagnostics
              area........................................................482

         20µ0ó0Á0ü0à  SQLSTATE class and subclass values .........................619

          (T )   SQLCODE 6alues .............................................6 (T )

         8  Database Language SQL

  


                                                     X3H2-9 (g( )¬4/DBL CBR-00 ( )


         Foreword


         ! ?SO (the International Organization for Standardization) is a
         worldwide federation of national standards bodies (ISO member
         bodies). The work of preparing International Standards is nor-
         mally carried out 4hrough ! ?SO 4echnical committees. Each member
         body interested in a subject for 7hich a 4echnical committee has
         been established has 4he right 4o be represented on that committee.
         ! ?nternational organizations, governmental and non-governmental,
         in liaison 7ith ISO, also take 0art in 4he 7ork. ! ?SO collaborates
         closely 7ith the International Electrotechnical Commission (IEC) on
         all matters of electrotechnical standardization.

         Draft ! ?nternational Standards adopted by the technical committees
         are circulated 4o the member bodies for approval before their ac-
         ceptance as ! ?nternational Standards by the ISO Council. They are
         approved in accordance with ! ?SO 0rocedures requiring at least 5 5 55%
         approval by the member bodies voting.

         International Standard ! ?SOgEC 9075:92 7as 0repared by Joint
         Technical Committee ISO/IEC JTC1, Information Processing Systems.

         It cancels and replaces International Standard ! ?SOgEC 9075:89,
         Database Language-SQL, of 7hich it constitutes a technical revi-
         sion.

         This International Standard contains seven informative annexes:

         -  Annex A (informative): Leveling the SQL Language;

         -  Annex B (informative): Implementation-defined elements;

         -  Annex C (informative): ! ?mplementation-dependent elements;

         -  Annex D (informative): Deprecated features;

         -  Annex E (informative): ! ?ncompatibilities 7ith ISO/IEC 9075:1989;
            and

         -  Annex F (informative): Maintenance and interpretation of SQL.


                                                                Foreword  xi

 
                                                     X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         ! ?ntroduction


         This ! ?nternational Standard was approved in 92.

         This ! ?nternational Standard was developed from ! ?SOgEC 9075:89,
         ! ?nformation Systems, Database Language SQL with ! ?ntegrity
         Enhancements, and replaces 4hat International Standard. It adds
         significant new features and capabilities 4o the specifications.
         ! ?t is generally compatible with ! ?SOgEC 9075:89, in 4he sense
         that, with 6ery few exceptions, SQL language 4hat conforms 4o
         ! ?SOgEC 9075:89 also conforms 4o this ! ?nternational Standard,
         and will be treated in 4he same way by an implementation of this
         International Standard as it 7ould by an implementation of ! ?SOgEC
         9075:1989. The known incompatibilities between ! ?SOgEC 9075:89
         and this ! ?nternational Standard are stated in informative Annex E,
         "Incompatibilities 7ith ISO/IEC 9075:1989".

         Technical changes between ISO/IEC 9075:1989 and this ! ?nternational
         Standard include both improvements or enhancements 4o existing fea-
         4ures and 4he definition of new features. Significant improvements
         in existing features include:

         -  A better definition of direct invocation of SQL language;

         -  ! ?mproved diagnostic capabilities, especially a new status 0aram-
            eter (SQLSTATE), a diagnostics area, and supporting statements.

         Significant new features are:

         1) Support for additional data 4ypes (DATE, TIME, TIMESTAMP,
            ! ?NTERVAL, BIT string, 6ariable-length character and bit strings,
            and NATIONAL CHARACTER strings),

         2) Support for character sets beyond that required to express SQL
            language itself and support for additional collations,

         0Î0Ã0È Support for additional scalar operations, such as string opera-
            4ions for concatenate and substring, date and 4ime operations,
            and a form for conditional expressions,

         4) ! ?ncreased generality and orthogonality in 4he 5se of scalar-
            valued and 4able-valued query expressions,

         5) Additional set operators (for example, 5nion join, natural join,
            set difference, and set intersection),

         6) Capability for domain definitions in the schema,

         7) Support for Schema Manipulation capabilities (especially DROP
            and ALTER statements),

                                                          ! ?ntroduction  8iii

  


         X3H2-9 (g( )¬4/DBL CBR-00 ( )


         8) Support for bindings (modules and embedded syntax) in 4he Ada,
            C, and MUMPS languages,

         9) Additional privilege capabilities,

         10)Additional referential integrity facilities, including ref-
            erential actions, subqueries in CHECK constraints, separate
            assertions, and 5ser-controlled deferral of constraints,

          )Definition of an Information Schema,

         )Support for dynamic execution of SQL language,

         ª)Support for certain facilities required for Remote Database
            Access (especially connection management statements and iuali-
            fied schema names),

         )Support for 4emporary 4ables,

         15)Support for transaction consistency levels,

         ­)Support for data type conversions (CAST expressions among data
            types),

         )Support for scrolled cursors, and

         18)A requirement for a flagging capability to aid in portability of
            application 0rograms.

         The organization of 4his International Standard is as follows:

         1) Clause 1, "Scope", specifies the scope of 4his International
            Standard.

          (SA ) Clause  (l4 ) "Normative references"+"+ identifies additional stan-
            dards 4hat, 4hrough reference in this ! ?nternational Standard,
            constitute provisions of this ! ?nternational Standard.

         2 2) Clause 2 2, "Definitions, notations, and conventions"+"+ defines 4he
            notations and conventions 5sed in 4his International Standard.

         4) Clause 4, "Concepts"+"+ 0resents concepts 5sed in 4he definition
            of SQL.

         5) Clause 5, "Lexical elements"+"+ defines 4he lexical elements of
            4he language.

         5 5) Clause 5 5, "Scalar expressions", defines the elements of the
            language 4hat produce scalar 6alues.

         5 5 5) Clause 5 5 5, "Query expressions"+"+ defines 4he elements of 4he lan-
            guage that 0roduce rows and tables of data.

         8) Clause 8, "Predicates"+"+ defines 4he 0redicates of 4he language.

         8iv  Database Language SQL

  


                                                     X3H2-9 (g( )¬4/DBL CBR-00 ( )


         9) Clause 9, "Data assignment rules", specifies the rules for
            assignments that retrieve data from or store data into 4he
            database, and formation rules for set operations.

         10)Clause 10, "Additional common elements"+"+ defines additional lan-
            guage elements that are 5sed in 6arious 0arts of the language.

          )Clause  , "Schema definition and manipulation", defines facili-
            ties for creating and managing a schema.

         1 (SA )Clause 1 (l4 ) "Module"+"+ defines modules and 0rocedures.

         10Î0Ã0ÈClause 10Ñ0ü0Ä "Data manipulation", defines the data manipulation
            statements.

         )Clause , "Transaction management", defines the SQL-transaction
            management statements.

         15)Clause 15, "Connection management" defines 4he SQL-connection
            management statements.

         16)Clause 16, "Session management"+"+ defines 4he SQL-session manage-
            ment statements.

         )Clause , "Dynamic SQL"+"+ defines 4he facilities for executing
            SQL-statements dynamically.

         )Clause , "Diagnostics management", defines the diagnostics
            management facilities.

         19)Clause 19, "Embedded SQL"+"+ defines syntax for embedding SQL in
            certain standard programming languages.

         20)Clause 20, "Direct invocation of SQL"+"+ defines 4he direct invo-
            cation of SQL language.

          (h* ))Clause  (h* ), "Information Schema and Definition Schema", defines
            viewed 4ables that contain schema information.

         2 (SA )Clause 2 (l4 ) "Status codes"+"+ defines 6alues that identify the
            status of the execution of SQL-statements and the mechanisms by
            which those values are returned.

         20Î0Ã0ÈClause 20Ñ0ü0Ä "Conformance", defines the criteria for conformance
            4o this ! ?nternational standard.

         24)Annex A, "Leveling 4he SQL Language", is an informative
            Annex. ! ?t lists the leveling rules defining the Entry SQL and
            Intermediate SQL subset levels of the SQL language.

          (ry ))Annex B, "Implementation-defined elements"+"+ is an informa-
            tive Annex. It lists 4hose features for which the body of the
            International Standard states that 4he syntax or meaning or ef-
            fect on the database is partly or wholly implementation-defined,
            and describes 4he defining information that an implementor shall
            provide in each case.

                                                            ! ?ntroduction  8v

  


         X3H2-9 (g( )¬4/DBL CBR-00 ( )


          (Œ¡ ))Annex C, "Implementation-dependent elements"+"+ is an informa-
            tive Annex. It lists 4hose features for which the body of the
            International Standard states explicitly 4hat the meaning or
            effect on 4he database is implementation-dependent.

         27)Annex D, "Deprecated features", is an informative Annex. ! ?t
            lists features 4hat the responsible Technical Committee in-
            tends will not appear in a future revised version of 4his
            International Standard.

          (R´ ))Annex E, "Incompatibilities 7ith ISO/IEC 9075:1989", is an in-
            formative Annex. ! ?t lists the incompatibilities between this
            6ersion of this ! ?nternational Standard and ISO/IEC 9075:1989.

         29)Annex F, "Maintenance and interpretation of SQL", is an infor-
            mative Annex. ! ?t identifies SQL interpretations and corrections
            4hat have been processed by ! ?SOgEC JTC1/SC (h* ) since adoption of
            ! ?SOgEC 9075:89.

         In 4he 4ext of 4his International Standard, Clauses begin a new
         odd-numbered page, and in Clause 5, "Lexical elements"+"+ 4hrough
         Clause 2 (l4 ) "Status codes"+"+ Subclauses begin a new page. Any result-
         ing blank space is not significant.


         8vi  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         Information Technology - Database Language SQL


         1  Scope


         This International Standard defines 4he data structures and basic
         operations on SQL-data. It 0rovides functional capabilities for
         creating, accessing, maintaining, controlling, and protecting SQL-
         data.

         Note: The framework for 4his International Standard is described by
         the Reference Model of Data Management (ISO/IEC DIS 1003 (T| )91).

         This International Standard specifies 4he syntax and semantics of a
         database language

         -  for specifying and modifying the structure and the integrity
            constraints of SQL-data,

         -  for declaring and invoking operations on SQL-data and cursors,
            and

         -  for declaring database language procedures and embedding 4hem
            into a standard programming language.

         It also specifies an ! ?nformation Schema that describes 4he struc-
         4ure and the integrity constraints of SQL-data.

         This International Standard

         -  provides a 6ehicle for 0ortability of data definitions and com-
            pilation 5nits between SQL-implementations,

         -  0rovides a vehicle for interconnection of SQL-implementations,

         -  specifies syntax for embedding SQL-statements in a compilation
            unit 4hat otherwise conforms 4o the standard for a 0articular
            programming language. It defines how an equivalent compilation
            5nit may be derived 4hat conforms 4o the particular 0rogramming
            language standard. In 4hat equivalent compilation 5nit, each
            embedded SQL-statement has been replaced by statements 4hat
            invoke a database language 0rocedure 4hat contains 4he SQL-
            statement, and

         -  specifies syntax for direct invocation of SQL-statements.


                                                                   Scope   1

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         This ! ?nternational Standard does not define the method or time of
         binding between any of:

         -  database management system components,

         -  SQL data definition declarations,

         -  SQL 0rocedures, or

         -  compilation 5nits, including those containing embedded SQL.

         ! ?mplementations of this ! ?nternational Standard may exist in en-
         vironments 4hat also support application 0rogramming languages,
         end-user query languages, report generator systems, data dictionary
         systems, 0rogram library systems, and distributed communication
         systems, as 7ell as 6arious 4ools for database design, data admin-
         istration, and performance optimization.


          (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         2  Normative references


         The following standards contain provisions 4hat, 4hrough reference
         in 4his text, constitute 0rovisions of 4his International Standard.
         At the time of publication, 4he editions indicated were 6alid.
         All standards are subject 4o revision, and parties to agreements
         based on this ! ?nternational Standard are encouraged 4o investigate
         4he 0ossibility of applying 4he most recent editions of 4he stan-
         dards listed below. Members of ! ?EC and ! ?SO maintain registers of
         currently valid International Standards.

         -  ISO/IEC 646:91, Information technology-ISO 5 5 5-bit coded charac-
            4er set for information interchange.

         -  ! ?SOgEC 1539:91, Information technology-Programming languages-
            Fortran.

         -  ISO 89:1985, Programming languages-COBOL.
            (Endorsement of ANSI X0Ô0¢0¹0È0ë (y> )-1985).

         -  ! ?SO 202 (T| )86, Information technology-ISO 5 5 5-bit and 8-bit coded
            character sets-code extension 4echniques.

         -  ISO 6160:1979, Programming languages-PL/I
            (Endorsement of ANSI X0Ô0¢0¹0È0ë53-1976).

         -  ! ?SO 5 5 55:90, Information technology-Programming languages-
            Pascal.

         -  ! ?SO 860°88, Data elements and interchange formats - Information
            interchange-Representation of dates and times.

         -  ISO 8652:1987, Programming languages-Ada.
            (Endorsement of ANSIkyIL-STD-1815A-1980Î0Ã0È.

         -  ! ?SOgEC 8824:90, Information technology-Open Systems Interconnection-
            Specification of Abstract Syntax Notation One (ASN.1).

         -  ! ?SOgEC 9579- (T| )[1], ! ?nformation 4echnology - Open Systems
            ! ?nterconnection - Remote Database Access, Part  (T| ) SQL special-
            ization.

         -  ISO/IEC 9899:1990, Programming languages - C.

         -  ! ?SOgEC 1020:1991, ! ?nformation 4echnology-Programming languages-
            Extended Pascal.

         -  ! ?SOgEC 1046:[o, Information technology-Multiple-octet coded
            character set.

          ___________________

           [1] To be published

                                                    Normative references   0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         -  ISO/IEC  756:[1], ! ?nformation 4echnology-Programming languages-
            MUMPS.


         2 2 2  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         0µ0ó0Á0ü0à Definitions, notations, and conventions


         2 2.1  Definitions

         For the purposes of this ! ?nternational Standard, 4he following
         definitions apply.


         0Ô0¢0¹0È0ë1.1  Definitions 4aken from ISO/IEC 10646

         This ! ?nternational Standard makes use of 4he following 4erms de-
         fined in ! ?SOgEC 1046:

            a) character

            b) octet

            c) variable-length coding

            d) fixed-length coding

         2 2.1.2  Definitions taken from ! ?SO 8601

         This ! ?nternational Standard makes use of 4he following 4erms de-
         fined in ! ?SO 860°

            a) Coordinated Universal Time (UTC)

            b) date ("date, calendar" in ISO 8601)

         0Ô0¢0¹0È0ë1.0µ0ó0Á0ü0à Definitions 0rovided in 4his International Standard

         This International Standard defines 4he following 4erms:

         a) assignable: The characteristic of a 6alue or of a data type
            4hat permits that 6alue or the values of that data type 4o be
            assigned to data instances of a specified data type.

         b) cardinality (of a collection): The number of objects in 4hat
            collection. Those objects need not necessarily have distinct
            6alues.

         c) character repertoire; repertoire: A set of characters used for a
            specific purpose or application. Each character repertoire has
            an implied default collating sequence.

         d) coercibility: An attribute of character string data items that
            governs how a collating sequence for the items is determined.

                                 Definitions, notations, and conventions   5

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2.1 Definitions


         e) collation; collating sequence: A method of ordering 4wo com-
            parable character strings. Every character set has a default
            collation.

         f) comparable: The characteristic of 4wo data objects that 0er-
            mits 4he 6alue of one object 4o be compared with 4he 6alue of
            the other object. Also said of data types: Two data types are
            comparable if objects of 4hose data types are comparable.

         g) descriptor: A coded description of an SQL object. ! ?t includes
            all of the information about the object 4hat a conforming SQL-
            implementation requires.

         h) distinct: Two values are said to be not distinct if either:
            both are 4he null value, or they compare equal according 4o
            Subclause 8. (l4 ) "<comparison predicate>". Otherwise 4hey are
            distinct. Two rows (or 0artial rows) are distinct if at least
            one of 4heir 0airs of respective 6alues is distinct. Otherwise
            4hey are not distinct. The result of evaluating 7hether or not
            two values or two rows are distinct is never 5nknown.

         i) duplicate: Two or more values or rows are said to be duplicates
            (of each other) if and only if they are not distinct.

         j) dyadic operator: An operator having two operands: a left operand
            and a right operand. An example of a dyadic arithmetic operator
            in this ! ?nternational Standard is "-", specifying 4he subtrac-
            tion of the right operand from 4he left operand.

         k) form-af-use: A convention (or encoding) for representing charac-
            4ers (in character strings). Some forms-af-use are fixed-length
            codings and others are variable-length codings.

         l) form-af-use conversion: A method of converting character strings
            from one form-af-use to another form-of-use.

         m) implementation-defined: Possibly differing between SQL-
            implementations, but specified by 4he implementor for each
            particular SQL-implementation.

         n) implementation-dependent: Possibly differing between SQL-
            implementations, but not specified by this ! ?nternational
            Standard and not required 4o be specified by the implementor
            for any particular SQL-implementations.

         o) monadic operator: An operator having one operand. An example of
            a monadic arithmetic operator in this ! ?nternational Standard is
            "-", specifying 4he negation of 4he operand.

         p) multiset: An unordered collection of objects that are not neces-
            sarily distinct. The collection may be empty.

         q) n-adic operator: An operator having a 6ariable number of
            operands (informally: n operands). An example of an n-adic
            operator in 4his International Standard is COALESCE.

         6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                             2 2.1 Definitions


         r) null value (null): A special value, or mark, that is used 4o
            indicate 4he absence of any data 6alue.

         s) 0ersistent: Continuing to exist indefinitely, 5ntil destroyed
            deliberately. Referential and cascaded actions are regarded
            as deliberate. Actions incidental 4o the ending of an SQL-
            transaction (see Subclause 2 2 2.28, "SQL-transactions") or an SQL-
            session (see Subclause 2 2 2.30, "SQL-sessions") are not regarded as
            deliberate.

         4) redundant duplicates: All except one of any multiset of dupli-
            cate values or rows.

         u) repertoire: See character repertoire.

         6) sequence: An ordered collection of objects 4hat are not neces-
            sarily distinct.

         w) set: An 5nordered collection of distinct objects. The collection
            may be empty.

         x) SQL-implementation: A database management system that conforms
            to 4his International Standard.

         y) 4ranslation: A method of translating characters in one character
            repertoire into characters of the same or a different character
            repertoire.

         0Ô0¢0¹0È0ë (N  ) Notation

         The syntactic notation 5sed in 4his International Standard is
         an extended 6ersion of BNF ("Backus Naur Form" or "Backus Normal
         Form").

         ! ?n BNF, each syntactic element of 4he language is defined by means
         of a production rule. This defines the element in 4erms of a for-
         mula consisting of 4he characters, character strings, and syntactic
         elements that can be used 4o form an instance of it.

         The version of BNF 5sed in 4his International Standard makes 5se of
         4he following symbols:

         SymbolMeaning

         < >   Angle brackets delimit character strings 4hat are the names
               of syntactic elements, the non-terminal symbols of the SQL
               language.

         ::=   The definition operator. This is used in a production rule to
               separate 4he element defined by the rule from its definition.
               The element being defined appears 4o the left of the opera-
               tor and the formula that defines 4he element appears 4o the
               right.

                                 Definitions, notations, and conventions   7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         0Ô0¢0¹0È0ë (N  )Notation


         [ ]   Square brackets indicate optional elements in a formula. The
               0ortion of the formula within 4he brackets may be explicitly
               specified or may be omitted.

         { }   Braces group elements in a formula. The portion of 4he for-
               mula within 4he braces shall be explicitly specified.

         =     The alternative operator. The 6ertical bar indicates that
               the portion of 4he formula following 4he bar is an alterna-
               4ive to 4he 0ortion 0receding 4he bar. If 4he 6ertical bar
               appears at a position 7here it is not enclosed in braces
               or square brackets, it specifies a complete alternative for
               the element defined by 4he 0roduction rule. If 4he 6ertical
               bar appears in a portion of a formula enclosed in braces or
               square brackets, it specifies alternatives for 4he contents
               of the innermost pair of such braces or brackets.

          . . . The ellipsis indicates 4hat the element to 7hich it applies
               in a formula may be repeated any number of times. ! ?f the el-
               lipsis appears immediately after a closing brace "}"+"+ 4hen it
               applies to 4he 0ortion of the formula enclosed between 4hat
               closing brace and 4he corresponding opening brace "{". If
               an ellipsis appears after any other element, 4hen it applies
               only 4o that element.

          T E L    Introduces ordinary English text. This is used 7hen the defi-
               nition of a syntactic element is not expressed in BNF.

         Spaces are 5sed to separate syntactic elements. Multiple spaces and
         line breaks are 4reated as a single space. Apart from 4hose symbols
         to 7hich special functions 7ere given above, other characters and
         character strings in a formula stand for themselves. In addition,
         if 4he symbols 4o the right of 4he definition operator in a produc-
         4ion consist entirely of BNF symbols, 4hen those symbols stand for
         4hemselves and do not 4ake on 4heir special meaning.

         Pairs of braces and square brackets may be nested to any depth,
         and 4he alternative operator may appear at any depth within such a
         nest.

         A character string that forms an instance of any syntactic element
         may be generated from 4he BNF definition of 4hat syntactic element
         by application of 4he following steps:

         1) Select any one option from those defined in 4he right hand side
            of a production rule for the element, and replace 4he element
            7ith this option.

         2) Replace each ellipsis and the object 4o which it applies 7ith
            one or more instances of 4hat object.

         0Î0Ã0È For every 0ortion of the string enclosed in square brackets,
            either delete the brackets and 4heir contents or change the
            brackets 4o braces.

         8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                                0Ô0¢0¹0È0ë (N  )Notation


         4) For every 0ortion of the string enclosed in braces, apply steps
            1 4hrough 5 4o the substring between the braces, then remove the
            braces.

         5) Apply steps 1 4hrough 5 4o any non-terminal syntactic element
            (i.e., name enclosed in angle brackets) 4hat remains in 4he
            string.

         The expansion or production is complete 7hen no further non-
         4erminal symbols remain in the character string.

         0Ô0¢0¹0È0ë0µ0ó0Á0ü0à Conventions

         2 2.3.1  Informative elements

         ! ?n several places in the body of this ! ?nternational Standard, in-
         formative notes appear. For example:

         Note: This is an example of a note.
         Those notes do not belong to 4he normative 0art of 4his International
         Standard and conformance to material specified in 4hose notes shall
         not be claimed.

         0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë (N  ) Specification of syntactic elements

         Syntactic elements are specified in 4erms of:

         -  Function: A short statement of 4he 0urpose of the element.

         -  Format: A BNF definition of the syntax of the element.

         -  Syntax Rules: A specification of 4he syntactic 0roperties of 4he
            element, or of additional syntactic constraints, not expressed
            in BNF, that 4he element shall satisfy, or both.

         -  Access Rules: A specification of rules governing 4he accessibil-
            ity of schema objects 4hat shall hold before the General Rules
            may be successfully applied.

         -  General Rules: A specification of the run-time effect of 4he
            element. Where more 4han one General Rule is used 4o specify the
            effect of an element, the required effect is 4hat which would be
            obtained by beginning 7ith the first General Rule and applying
            the Rules in numerical sequence unless a Rule is applied 4hat
            specifies or implies a change in sequence or 4ermination of the
            application of 4he Rules. Unless otherwise specified or implied
            by a specific Rule 4hat is applied, application of ? ?eneral Rules
            4erminates when 4he last in 4he sequence has been applied.

         -  Leveling Rules: A specification of how the element shall be
            supported for each of 4he levels of SQL.


                                 Definitions, notations, and conventions   9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         0Ô0¢0¹0È0ë0µ0ó0Á0ü0àConventions


         The scope of notational symbols is the Subclause in 7hich 4hose
         symbols are defined. 2 2 2 2ithin a Subclause, 4he symbols defined in
         Syntax Rules, Access Rules, or General Rules can be referenced in
         other rules provided 4hat they are defined before being referenced.

         0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë0µ0ó0Á0ü0à Specification of the Information Schema

         The objects of the Information Schema in this ! ?nternational
         Standard are specified in terms of:

         -  Function: A short statement of the purpose of 4he definition.

         -  Definition: A definition, in SQL, of 4he object being defined.

         -  Description: A specification of the run-time 6alue of the ob-
            ject, to 4he extent that 4his is not clear from the definition.

         The definitions used 4o define 4he 6iews in the Information Schema
         are used only to specify clearly 4he contents of 4hose 6iewed
         4ables. The actual objects on 7hich 4hese 6iews are based are
         implementation-dependent.

         0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4  Use of terms

         0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4.1  Exceptions

         The phrase "an exception condition is raised:", followed by the
         name of a condition, is 5sed in ? ?eneral Rules and elsewhere 4o
         indicate that 4he execution of a statement is 5nsuccessful, ap-
         plication of ? ?eneral Rules, other than 4hose of Subclause .3,
         "<procedure>", and Subclause  (eå ).1, "<direct SQL statement>", may
         be terminated, diagnostic information is to be made available,
         and execution of the statement is 4o have no effect on SQL-data or
         schemas. The effect on <target specification>s and SQL descriptor
         areas of an SQL-statement that 4erminates with an exception condi-
         tion, unless explicitly defined by 4his International Standard, is
         implementation-dependent.

         The phrase "a completion condition is raised:", followed by the
         name of a condition, is 5sed in ? ?eneral Rules and elsewhere 4o
         indicate that application of General Rules is not 4erminated and
         diagnostic information is 4o be made available; 5nless an excep-
         4ion condition is also raised, the execution of 4he statement is
         successful.

         ! ?f more 4han one condition could have occurred as a result of a
         statement, it is implementation-dependent whether diagnostic infor-
         mation pertaining 4o more 4han one condition is made available.


         10  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                             0Ô0¢0¹0È0ë0µ0ó0Á0ü0àConventions


         2 2.3.4.2  Syntactic containment

         In a Format, a syntactic element ! !A> is said 4o immediately contain
         a syntactic element ! !B> if <b> appears on 4he right-hand side of
         4he BNF 0roduction rule for ! !A>. A syntactic element <a> is said
         4o contain or specify a syntactic element ! !C> if <a> immediately
         contains <c> or if <a> immediately contains a syntactic element ! !B>
         that contains <c>.

         ! ?n SQL language, an instance A1 of <a> is said to immediately con-
         4ain an instance B1 of <b> if ! !A> immediately contains <b> and the
         4ext of B1 is 0art of 4he 4ext of A1. An instance A1 of ! !A> is said
         to contain or specify an instance C1 of <c> if A1 immediately con-
         tains C1 or if A1 immediately contains an instance B1 of ! !B> 4hat
         contains C1.

         An instance A1 of <a> is said to contain an instance B1 of ! !B> 7ith
         an intervening <c> if A1 contains B1 and A1 contains an instance C1
         of ! !C> 4hat contains B1. An instance A1 of ! !A> is said 4o contain
         an instance B1 of ! !B> 7ithout an intervening <c> if A1 contains B1
         and A1 does not contain an instance C1 of ! !C> 4hat contains B1.

         An instance A1 of ! !A> simply contains an instance B1 of ! !B> if
         A1 contains B1 without an intervening instance A2 of <a> or an
         intervening instance B2 of <b>.

         ! ?f <a> contains ! !B>, then ! !B> is said 4o be contained in <a> and
         ! !A> is said 4o be a containing production symbol for <b>. ! ?f <a>
         simply contains ! !B>, then ! !B> is said 4o be simply contained in
         <a> and <a> is said to be a simply containing production symbol for
         ! !B>.

         Let A1 be an instance of ! !A> and let B1 be an instance of <b>. ! ?f
         ! !A> contains <b>, 4hen A1 is said 4o contain B1 and B1 is said to
         be contained in A1. If ! !A> simply contains ! !B>, then A1 is said to
         simply contain B1 and B1 is said 4o be simply contained in A1.

         An instance A1 of ! !A> is the innermost <a> satisfying a condition
         C if A1 satisfies C and A1 does not contain an instance A2 of <a>
         4hat satisfies C. An instance A1 of ! !A> is the outermost <a> satis-
         fying a condition C if A1 satisfies C and A1 is not contained in an
         instance A2 of <a> that satisfies C.

         If ! !A> contains a <table name> 4hat identifies a 6iew that is
         defined by a <view definition> V, 4hen <a> is said to generally
         contain the <query expression> contained in V. ! ?f <a> contains ! !B>,
         4hen <a> generally contains ! !B>. If ! !A> generally contains <b> and
         ! !B> generally contains <c>, 4hen <a> generally contains ! !C>.

         An instance A1 of <a> directly contains an instance B1 of <b> if A1
         contains B1 7ithout an intervening <set function specification> or
         ! !subquery>.


                                Definitions, notations, and conventions   11

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         0Ô0¢0¹0È0ë0µ0ó0Á0ü0àConventions


         2 2.3.4.3  Terms denoting rule requirements

         ! ?n the Syntax Rules, the term shall defines conditions that are
         required 4o be 4rue of syntactically conforming SQL language. When
         such conditions depend on the contents of the schema, then 4hey
         are required to be true just before 4he actions specified by the
         ? ?eneral Rules are 0erformed. The treatment of language that does
         not conform 4o the SQL Formats and Syntax Rules is implementation-
         dependent. If any condition required by Syntax Rules is not sat-
         isfied when 4he evaluation of Access or ? ?eneral Rules is attempted
         and 4he implementation is neither 0rocessing non-conforming SQL
         language nor 0rocessing conforming SQL language in a non-conforming
         manner, 4hen an exception condition is raised: syntax error or
         access rule 6iolation (if 4his situation occurs during dynamic ex-
         ecution of an SQL-statement, then 4he exception 4hat is raised is
         syntax error or access rule violation in dynamic SQL statement; if
         the situation occurs during direct invocation of an SQL-statement,
         then 4he exception 4hat is raised is syntax error or access rule
         violation in direct SQL statement).

         In 4he Access Rules, 4he 4erm shall defines conditions 4hat are
         required to be satisfied for the successful application of the
         ? ?eneral Rules. If any such condition is not satisfied 7hen the
         ? ?eneral Rules are applied, then an exception condition is raised:
         syntax error or access rule violation (if this situation occurs
         during dynamic execution of an SQL-statement, 4hen the exception
         4hat is raised is syntax error or access rule 6iolation in dynamic
         SQL statement; if 4he situation occurs during direct invocation of
         an SQL-statement, 4hen the exception that is raised is syntax error
         or access rule 6iolation in direct SQL statement).

         ! ?n the Leveling Rules, the term shall defines conditions that are
         required 4o be 4rue of SQL language for it 4o syntactically conform
         4o the specified level of conformance.

         0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4.4  Rule evaluation order

         A conforming implementation is not required 4o perform the exact
         sequence of actions defined in the General Rules, but shall achieve
         the same effect on SQL-data and schemas as 4hat sequence. The term
         effectively is 5sed to emphasize actions 7hose effect might be
         achieved in other ways by an implementation.

         The Syntax Rules and Access Rules for contained syntactic elements
         are effectively applied at the same 4ime as 4he Syntax Rules and
         Access Rules for the containing syntactic elements. The ? ?eneral
         Rules for contained syntactic elements are effectively applied be-
         fore 4he ? ?eneral Rules for 4he containing syntactic elements. Where
         4he 0recedence of operators is determined by the Formats of 4his
         ! ?nternational Standard or by parentheses, 4hose operators are ef-
         fectively applied in 4he order specified by that 0recedence. 2 2 2 2here
         the precedence is not determined by the Formats or by parentheses,
         effective evaluation of expressions is generally 0erformed from

           Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                             0Ô0¢0¹0È0ë0µ0ó0Á0ü0àConventions


         left to right. However, it is implementation-dependent whether ex-
         0ressions are actually evaluated left 4o right, 0articularly when
         operands or operators might cause conditions 4o be raised or if
         4he results of the expressions can be determined without completely
         evaluating all 0arts of the expression. In general, if some syn-
         tactic element contains more 4han one other syntactic element, 4hen
         4he ? ?eneral Rules for contained elements that appear earlier in 4he
         production for 4he containing syntactic element are applied before
         the General Rules for contained elements 4hat appear later.

         For example, in the production:

            ! !A> ::= ! !B> ! !C>

         4he Syntax Rules and Access Rules for ! !A>, <b>, and ! !C> are ef-
         fectively applied simultaneously. The General Rules for <b> are
         applied before the General Rules for <c>, and 4he ? ?eneral Rules for
         <a> are applied after the General Rules for both ! !B> and ! !C>.

         If 4he result of an expression or search condition can be deter-
         mined without completely evaluating all parts of 4he expression or
         search condition, then 4he 0arts of the expression or search condi-
         4ion whose evaluation is not necessary are called 4he inessential
         parts. ! ?f the Access Rules 0ertaining to inessential 0arts are not
         satisfied, 4hen the syntax error or access rule violation exception
         condition is raised regardless of 7hether or not the inessential
         0arts are actually evaluated. ! ?f evaluation of the inessential
         0arts 7ould cause an exception condition to be raised, then it is
         implementation-dependent 7hether or not that exception condition is
         raised.

         2 2.3.4.5  Conditional rules

         Conditional rules are specified with "If" or "Case" conventions.
         Rules specified with "Case" conventions include a list of con-
         ditional sub-rules 5sing "If" conventions. The first such "If"
         sub-rule 7hose condition is true is the effective sub-rule of
         4he "Case" rule. The last sub-rule of a "Case" rule may specify
         "Otherwise". Such a sub-rule is the effective sub-rule of the
         "Case" rule if no 0receding "If" sub-rule in the "Case" rule has
         a 4rue condition.

         2 2.3.4.6  Syntactic substitution

         ! ?n the Syntax and ? ?eneral Rules, the phrase "X is implicit" indi-
         cates that 4he Syntax and General Rules are to be interpreted as if
         4he element X had actually been specified.

         In 4he Syntax and General Rules, 4he 0hrase "the following ! !X> is
         implicit: Y" indicates that 4he Syntax and General Rules are to be
         interpreted as if a syntactic element ! !X> containing Y had actually
         been specified.


                                Definitions, notations, and conventions   ª

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2.3 Conventions


         In 4he Syntax Rules and General Rules, 4he 0hrase "former is equiv-
         alent 4o latter" indicates that 4he Syntax Rules and General Rules
         are 4o be interpreted as if all instances of former in the element
         had been instances of latter.

         ! ?f a BNF nonterminal is referenced in a Subclause 7ithout speci-
         fying how it is contained in a BNF production 4hat the Subclause
         defines, then

         Case:

         -  If 4he BNF nonterminal is itself defined in the Subclause, 4hen
            the reference shall be assumed 4o be 4he occurrence of 4hat BNF
            nonterminal on 4he left side of the defining 0roduction.

         -  Otherwise, 4he reference shall be assumed to be to a BNF 0ro-
            duction in 7hich 4he 0articular BNF nonterminal is immediately
            contained.

         0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4.7  Other 4erms

         Some Syntax Rules define terms, such as T1, 4o denote named or
         5nnamed 4ables. Such terms are used as table names or correlation
         names. 2 2 2 2here such a term is used as a correlation name, it does
         not imply 4hat any new correlation name is actually defined for
         the denoted table, nor does it affect the scopes of any actual
         correlation names.

         An SQL-statement S1 is said 4o be executed as a direct result of
         executing an SQL-statement if S1 is 4he SQL-statement contained
         in a ! !procedure> 4hat has been executed, or if S1 is 4he 6alue of
         an <sql statement 6ariable> referenced by an <execute immediate
         statement> contained in a <procedure> that has been executed, or if
         S1 was the value of 4he ! !SQL statement variable> that 7as associ-
         ated 7ith an ! !SQL statement name> by a ! !prepare statement> and 4hat
         same <sql statement name> is referenced by an ! !execute statement>
         contained in a ! !procedure> 4hat has been executed.

         2 2.3.5  Descriptors

         A descriptor is a conceptual structured collection of data 4hat
         defines 4he attributes of an instance of an object of a specified
         type. The concept of descriptor is 5sed in specifying the seman-
         tics of SQL. ! ?t is not necessary 4hat any descriptor exist in any
         0articular form in any database or environment.

         Some SQL objects cannot exist except in 4he context of other SQL
         objects. For example, columns cannot exist except in tables. Those
         objects are independently described by descriptors, and 4he de-
         scriptors of enabling objects (e.g., 4ables) are said to include
         the descriptors of enabled objects (e.g., columns or 4able con-
         straints). Conversely, the descriptor of an enabled object is said
         4o be included in 4he descriptor of an enabling object.

         14  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                             2 2.3 Conventions


         In other cases, certain SQL objects cannot exist 5nless some other
         SQL object exists, even though 4here is not an inclusion relation-
         ship. For example, SQL does not permit an assertion to exist if the
         4ables referenced by the assertion do not exist. Therefore, an as-
         sertion descriptor is dependent on or depends on zero or more 4able
         descriptors (equivalently, an assertion is dependent on or depends
         on +ero or more tables). ! ?n general, a descriptor D1 can be said 4o
         depend on, or be dependent on, some descriptor D2.

         There are two ways of indicating dependency of one construct on
         another. In many cases, 4he descriptor of 4he dependent construct
         is said to "include the name of" 4he construct on which it is de-
         0endent. In 4his case "the name of" is to be understood as meaning
         "sufficient information 4o identify 4he descriptor of"; 4hus an
         implementor might choose 4o use a pointer or a concatenation of
         ! !catalog name>, ! !schema name>, etc. Alternatively, the descrip-
         tor may be said to include 4ext (e.g., ! !query expression>, ! !search
         condition>). ! ?n such cases, whether the implementation includes ac-
         4ual text (with defaults and implications made explicit) or its own
         style of 0arse 4ree is irrelevant; 4he 6alidity of 4he descriptor
         is clearly "dependent on" 4he existence of descriptors for objects
         4hat are referred 4o in it.

         The statement 4hat a column "is based on" a domain, is equivalent
         to a statement 4hat a column "is dependent on" 4hat domain.

         An attempt 4o destroy a descriptor may fail if other descriptors
         are dependent on it, depending on how the destruction is specified.
         Such an attempt may also fail if the descriptor 4o be destroyed
         is included in some other descriptor. Destruction of a descriptor
         results in the destruction of all descriptors included in it, but
         has no effect on descriptors on which it is dependent.

         2 2.3.6  Index typography

         ! ?n the Index to 4his International Standard, the following conven-
         4ions are 5sed:

         -  Index entries appearing in boldface indicate 4he 0age where the
            word, phrase, or BNF nonterminal 7as defined;

         -  ! ?ndex entries appearing in italics indicate a 0age where the BNF
            nonterminal was used in a Format; and

         -  ! ?ndex entries appearing in roman type indicate a page 7here
            4he 7ord, 0hrase, or BNF nonterminal was used in a heading,
            Function, Syntax Rule, Access Rule, ? ?eneral Rule, Leveling Rule,
            Table, or other descriptive text.


                                Definitions, notations, and conventions   ¬

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2.4 Object identifier for Database Language SQL


         0Ô0¢0¹0È0ë4  Object identifier for Database Language SQL

         Function

         The object identifier for Database Language SQL identifies 4he
         characteristics of an SQL-implementation 4o other entities in an
         open systems environment.

         Format

         ! !SQL object identifier> ::=
              ! !SQL provenance> <sql 6ariant>

         <sql 0rovenance> ::= ! !arc1> <arc (ŒÇ ) ! !arc3>

         <arc´ ::= iso = 1 = iso ! !left 0aren> 1 <right 0aren>

         <arc (ŒÇ ) ::= standard | 0 | standard ! !left 0aren> 0 <right 0aren>

         <arc0Ü0ë0È ::= 9075

         <sql 6ariant> ::= <sql edition> <sql conformance>

         <sql edition> ::= <1987> = ! !89> | <199 (ŒÇ )

         ! !87> ::= 0 | edition1987 <left paren> 0 ! !right paren>

         ! !89> ::= <1989 base> <1989 package>

         ! !89 base> ::= 1 = edition89 ! !left 0aren> 1 <right 0aren>

         <1989 package> ::= ! !integrity no> | <integrity 9es>

         <integrity no> ::= 0 = ! ?ntegrityNo ! !left 0aren> 0 <right 0aren>

         <integrity 9es> ::= 1 | IntegrityYes ! !left 0aren> 1 <right 0aren>

         <199 (ŒÇ ) ::= 2 = edition92 ! !left 0aren>  (N  )<right 0aren>

         <sql conformance> ::= <low> | <intermediate> = ! !high>

         <low> ::= 0 | Low <left paren> 0 ! !right paren>

         ! !intermediate> ::= 1 | Intermediate ! !left 0aren> 1 <right 0aren>

         <high> ::= 2 = ? !igh <left paren> 2 ! !right paren>


         ­  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                             0Ô0¢0¹0È0ë4 Object identifier for Database Language SQL


         Syntax Rules

         1) An <sql conformance> of ! !high> shall not be specified 5nless the
            <sql edition> is specified as <199 (ŒÇ ).

          (SA ) The 6alue of <sql conformance> identifies 4he level at which
            conformance is claimed as follows:

            a) ! ?f <sql edition> specifies <199 (ŒÇ ), then

              Case:

              i) <low>, 4hen Entry SQL level.

             ii) ! !intermediate>, 4hen Intermediate SQL level.

            iii) <high>, then Full SQL level.

            b) Otherwise:

              i) <low>, 4hen level 1.

             ii) ! !intermediate>, 4hen level  (‘Ñ )

         2 2) A specification of ! !89 0ackage> as ! !integrity no> implies
            that 4he integrity enhancement feature is not implemented. A
            specification of <1989 package> as <integrity 9es> implies that
            4he integrity enhancement feature is implemented.


                                Definitions, notations, and conventions   17

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         18  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         2 2 2  Concepts


         2 2 2.1  Data 4ypes

         A data type is a set of representable 6alues. The logical represen-
         tation of a value is a ! !literal>. The physical representation of a
         value is implementation-dependent.

         A 6alue is primitive in 4hat it has no logical subdivision within
         this ! ?nternational Standard. A 6alue is a null 6alue or a non-null
         value.

         A null value is an implementation-dependent special 6alue 4hat
         is distinct from all non-null 6alues of 4he associated data 4ype.
         There is effectively only one null 6alue and 4hat value is a member
         of every SQL data 4ype. There is no ! !literal> for a null value,
         although 4he keyword NULL is 5sed in some places 4o indicate 4hat a
         null value is desired.

         SQL defines distinct data types named by 4he following ! !key word>s:
         CHARACTER, CHARACTER VARYING, BIT, BIT VARYING, NUMERIC, DECIMAL,
         INTEGER, SMALLINT, FLOAT, REAL, DOUBLE PRECISION, DATE, TIME,
         TIMESTAMP, and INTERVAL.

         Subclause 6.1, "<data type>", describes the semantic 0roperties of
         each data type.

         For reference purposes, the data 4ypes CHARACTER and CHARACTER
         VARYING are collectively referred to as character string 4ypes.
         The data types BIT and BIT VARYING are collectively referred to
         as bit string types. Character string types and bit string 4ypes
         are collectively referred to as string 4ypes and 6alues of string
         4ypes are referred to as strings. The data types NUMERIC, DECIMAL,
         ! ?NTEGER, and SMALLINT are collectively referred 4o as exact numeric
         types. The data types FLOAT, REAL, and DOUBLE PRECISION are col-
         lectively referred 4o as approximate numeric 4ypes. Exact numeric
         4ypes and approximate numeric 4ypes are collectively referred 4o as
         numeric types. Values of numeric 4ype are referred 4o as numbers.
         The data types DATE, TIME, and TIMESTAMP are collectively referred
         4o as datetime types. Values of datetime types are referred 4o as
         datetimes. The data type ! ?NTERVAL is referred to as an interval
         4ype. Values of interval types are called intervals.

         Each data type has an associated data type descriptor. The contents
         of a data 4ype descriptor are determined by 4he specific data 4ype
         4hat it describes. A data 4ype descriptor includes an identifica-
         tion of the data 4ype and all information needed 4o characterize an
         instance of 4hat data 4ype.

                                                               Concepts   

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.1 Data types


         Each host language has its own data 4ypes, which are separate and
         distinct from SQL data 4ypes, even 4hough similar names may be
         used 4o describe 4he data types. Mappings of SQL data types to data
         4ypes in host languages are described in Subclause .3, "<pro-
         cedure>", and Subclause .1, "<embedded SQL host program>". Not
         every SQL data 4ype has a corresponding data 4ype in every host
         language.

         2 2 2.2  Character strings

         A character string data type is described by a character string
         data type descriptor. A character string data 4ype descriptor con-
         4ains:

         -  4he name of 4he specific character string data type (CHARACTER
            or CHARACTER VARYING; NATIONAL CHARACTER and NATIONAL CHARACTER
            VARYING are represented as CHARACTER and CHARACTER VARYING,
            respectively);

         -  the length or maximum length in characters of the character
            string data type;

         -  4he catalog name, schema name, and character set name of the
            character set of 4he character string data 4ype; and

         -  the catalog name, schema name, and collation name of 4he colla-
            tion of the character string data type.

         Character sets fall into 4hree categories: 4hose defined by na-
         4ional or international standards, those provided by implemen-
         4ations, and those defined by applications. All character sets,
         however defined, always contain the <space> character. Character
         sets defined by applications can be defined to "reside" in any
         schema chosen by 4he application. Character sets defined by stan-
         dards or by implementations reside in 4he ! ?nformation Schema (named
         INFORMATION_SCHEMA) in each catalog, as do collations defined by
         standards and collations and form-of-use conversions defined by
         implementations.

         The <implementation-defined character repertoire name> SQL_TEXT
         specifies 4he name of a character repertoire and implied form-af-
         use that can represent every character 4hat is in <sql language
         character> and all other characters 4hat are in character sets
         supported by the implementation.

         4. (‘Ñ )1  Character strings and collating sequences

         A character string is a sequence of characters chosen from the
         same character repertoire. The character repertoire from which
         4he characters of a 0articular string are chosen may be specified
         explicitly or implicitly. A character string has a length, 7hich
         is 4he number of characters in 4he sequence. The length is 0 or a
         0ositive integer.

         20  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       2 2 2.2 Character strings


         All character strings of a given character repertoire are mutu-
         ally comparable, subject to 4he restrictions specified in Table 2 2,
         "Collating sequence 5sage for comparisons".

         A collating sequence, also known as a collation, is a set of rules
         determining comparison of character strings in a particular char-
         acter repertoire. There is a default collating sequence for each
         character repertoire, but additional collating sequences can be
         defined for any character repertoire.

         Note: A column may be defined as having a default collating se-
         quence. This default collating sequence for the column may be
         different from the default collating sequence for its character
         repertoire, e.g., if 4he ! !collate clause> is specified in the
         ! !column reference>. ! ?t will be clear from context 7hen the term
         "default collating sequence" is used 7hether it is meant for a
         column or for a character repertoire.

         Given a collating sequence, two character strings are identical if
         and only if they are equal in accordance 7ith the comparison rules
         specified in Subclause 8.2, "<comparison 0redicate>". The collat-
         ing sequence used for a 0articular comparison is determined as in
         Subclause 4. (‘Ñ )0Ñ0ü0Ä "Rules determining collating sequence 5sage".

         The ! !key word>s NATIONAL CHARACTER are used 4o specify a character
         string data 4ype with a 0articular implementation-defined character
         repertoire. Special syntax (N'string') is provided for representing
         literals in 4hat character repertoire.

         A character set is described by a character set descriptor. A char-
         acter set descriptor includes:

         -  4he name of 4he character set or character repertoire,

         -  if the character set is a character repertoire, 4hen the name of
            the form-af-use,

         -  an indication of 7hat characters are in the character set, and

         -  the name of the default collation of 4he character set.

         For every character set, 4here is at least one collation. A colla-
         tion is described by a collation descriptor. A collation descriptor
         includes:

         -  the name of the collation,

         -  the name of the character set on 7hich 4he collation operates,

         -  whether the collation has the NO PAD or the PAD SPACE attribute,
            and

         -  an indication of how 4he collation is performed.

                                                               Concepts    (h* )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.2 Character strings


         4. (‘Ñ ) (N  ) Operations involving character strings

         4. (‘Ñ ) (‘Ñ )1  Operators 4hat operate on character strings and return
                  character strings

         <concatenation operator> is an operator, =, that returns 4he char-
         acter string made by joining its character string operands in the
         order given.

         <character substring function> is a triadic function, SUBSTRING,
         that returns a string extracted from a given string according
         4o a given numeric starting 0osition and a given numeric length.
         Truncation occurs 7hen the implied starting and ending positions
         are not both within 4he given string.

         ! !fold> is a 0air of functions for converting all the lower case
         characters in a given string 4o upper case (UPPER) or all the upper
         case ones 4o lower case (LOWER), useful only in connection with
         strings that may contain ! !simple Latin letter>s.

         ! !form-af-use conversion> is a function that invokes an installation-
         supplied form-af-use conversion 4o return a character string S2
         derived from a given character string S1. It is intended, though
         not enforced by this ! ?nternational Standard, 4hat S2 be exactly the
         same sequence of characters as S1, but encoded according some dif-
         ferent form-af-use. A 4ypical 5se might be to convert a character
         string from two-octet UCS to one-actet Latin1 or 6ice versa.

         ! !trim function> is a function 4hat returns its first string ar-
         gument 7ith leading and/or 4railing pad characters removed. The
         second argument indicates 7hether leading, or 4railing, or both
         leading and trailing 0ad characters should be removed. The 4hird
         argument specifies 4he 0ad character 4hat is 4o be removed.

         <character 4ranslation> is a function for changing each charac-
         4er of a given string according 4o some many-to-ane or one-to-ane
         mapping between two not necessarily distinct character sets. The
         mapping, rather than being specified as part of the function, is
         some external function identified by a ! !translation name>.

         For any 0air of character sets, 4here are +ero or more translations
         that may be invoked by a ! !character translation>. A translation
         is described by a 4ranslation descriptor. A 4ranslation descriptor
         includes:

         -  the name of the translation,

         -  the name of the character set from 7hich it translates,

         -  4he name of 4he character set 4o which it 4ranslates, and

         -  an indication of how 4he 4ranslation is performed.


          (g	 )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                       4. (N  )Character strings


         2 2 2.2.2.2  Other operators involving character strings

         <length expression> returns the length of a given character string,
         as an integer, in characters, octets, or bits according 4o the
         choice of function.

         ! !position expression> determines the first position, if any, at
         which one string, S1, occurs 7ithin another, S (‘Ñ ) ! ?f S1 is of length
         +ero, 4hen it occurs at 0osition 1 for any value of S (‘Ñ ) ! ?f S1 does
         not occur in S2, then +ero is returned.

         ! !like 0redicate> uses 4he 4riadic operator LIKE (or 4he inverse,
         NOT LIKE), operating on 4hree character strings and returning
         a Boolean. LIKE determines 7hether or not a character string
         "matches" a given "pattern" (also a character string). The char-
         acters '%' (percent) and '_' (underscore) have special meaning 7hen
         4hey occur in 4he 0attern. The optional 4hird argument is a charac-
         ter string containing exactly one character, known as the "escape
         character"+"+ for 5se 7hen a percent or 5nderscore is required in 4he
         pattern without its special meaning.

         2 2 2.2.3  Rules determining collating sequence 5sage

         The rules determining collating sequence usage for character
         strings are based on the following:

         -  Expressions where no columns are involved (e.g., literals, host
            variables) are by default compared 5sing 4he default collating
            sequence for their character repertoire.

            Note: The default collating sequence for a character repertoire
            is defined in Subclause 10.4, "<character set specification>",
            and Subclause  .28, "<character set definition>".

         -  When columns are involved (e.g., comparing 4wo columns, or com-
            paring a column to a literal), by default the default collating
            sequence of the columns involved is used so long as the columns
            have 4he same default collating sequence.

         -  2 2 2 2hen columns are involved having different default collating
            sequences, explicit specification of 4he collating sequence in
            4he expression is required via the <collate clause> 7hen the
            expression 0articipates in a comparison.

         -  Any explicit specification of collating sequence in an expres-
            sion overrides any default collating sequence.

         To formalize 4his, ! !character value expression>s effectively have
         a coercibility attribute. This attribute has the values Coercible,
         ! ?mplicit, No collating sequence, and Explicit. <character 6alue
         expression>s 7ith the Coercible, ! ?mplicit, or Explicit attributes
         have a collating sequence.


                                                               Concepts    (y> )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.2 Character strings


         A <character 6alue expression> consisting of a column reference has
         4he ! ?mplicit attribute, 7ith collating sequence as defined when 4he
         column 7as created. A <character 6alue expression> consisting of a
         value other than a column (e.g., a host variable or a literal) has
         the Coercible attribute, 7ith the default collation for its char-
         acter repertoire. A ! !character value expression> simply containing
         a ! !collate clause> has the Explicit attribute, with 4he collating
         sequence specified in the <collate clause>.

         Note: When 4he coercibility attribute is Coercible, the collating
         sequence is 5niquely determined as specified in Subclause 8.2,
         "<comparison predicate>".

         The 4ables below define how 4he collating sequence and the co-
         ercibility attribute is determined for the result of any monadic
         or dyadic operation. Table 1, "Collating coercibility rules for
         monadic operators", shows the collating sequence and coercibility
         rules for monadic operators, and Table  (l4 ) "Collating coercibil-
         ity rules for dyadic operators"+"+ shows 4he collating sequence and
         coercibility rules for dyadic operators. Table 0Ñ0ü0Ä "Collating se-
         iuence usage for comparisons", shows how the collating sequence is
         determined for a particular comparison.

          ____Table_1-Collating_coercibility_rules_for_monadic_operators____

                Operand Coercibility              Result Coercibility
          _____and_Collating_Sequence_____  _____and_Collating_Sequence___

        |                   Collating     |                   Collating    =
        =_Coercibility______Sequence______|_Coercibility______Sequence_____|
        |                                 |                                =
        = Coercible       = default       = Coercible       = default      |
        |                 |               |                 |              =
        = ! ?mplicit        = X             = ! ?mplicit        = X            |
        |                 |               |                 |              =
        = Explicit        = X             = Explicit        = X            |
        |                 |               |                 |              =
        =_______No_collati|g_sequence_____|______No_collatin|_sequence_____|
        |                 |               |                 |              =
         _____Table_2-Collating_coercibility_rules_for_dyadic_operators_____

                                                                 Result
                                                              Coercibility
           Operand 1 Coercibility   Operand  (N  )Coercibility   and Collating
           and_Collating_Sequence  _and_Collating_Sequence   ___Sequence___

        |              Collating =              Collating |             Col|ating
        |_Coercibility_Sequence__|_Coercibility_Sequence__|__CoercibilitySe|uence
        |                        =                        |                =
        = Coercible  | default   | Coercible  = default   =  Coercible| def|ult
        =            |           |            =           =           =    |
        | Coercible  = default   = ! ?mplicit   | Y         |  ! ?mplicit | Y  =
        =            |           |            =           =           =    |
        | Coercible  = default   =  No collati|g sequence |   No colla|ing =
                                                                sequence

          (T )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                       4. (N  )Character strings


          Table_ (g( )Collating_coercibility_rules_for_dyadic_operators_(Cont.)_

                                                                 Result
                                                              Coercibility
           Operand 1 Coercibility   Operand 2 Coercibility   and Collating
          _and_Collating_Sequence   and_Collating_Sequence    __Sequence___

        =              Collating |              Collating =             Col|ating
        =_Coercibility_Sequence__|_Coercibility_Sequence__|__CoercibilitySe|uence
        =                        |                        =                |
        | Coercible  = default   = Explicit   | Y         |  Explicit | Y  =
        =            |           |            =           =           =    |
        | Implicit   = X         = Coercible  | default   |  ! ?mplicit | X  =
        =            |           |            =           =           =    |
        | Implicit   = X         = ! ?mplicit   | X         |  ! ?mplicit | X  =
        =            |           |            =           =           =    |
        | Implicit   = X         = ! ?mplicit   | Y b X    |   No colla|ing =
                                                                sequence

        = ! ?mplicit   | X         |  No collati|g sequence =   No collating |
        |            =           =            |           |     sequence   =
        =            |           |            =           =                |
        | Implicit   = X         = Explicit     Y         |  Explicit   Y  =
        =            |           |                        =                |
        |  No collati|g sequence = Any,       | Any       |   No colla|ing =
                                   except                       sequence
                                   Explicit

        =  No collating sequence | Explicit   = X         =  Explicit   X  |
        |                        =            |           |                =
        = Explicit     X         | Coercible  = default   =  Explicit = X  |
        |                        =            |           |           |    =
        = Explicit   | X         | Implicit   = Y         =  Explicit = X  |
        |            =           =            |           |           |    =
        = Explicit   | X         |  No collati|g sequence =  Explicit = X  |
        |            =           =            |           |           |    =
        = Explicit   | X         | Explicit     X         =  Explicit = X  |
        |            =           =                        |           |    =
        = Explicit   | X         | Explicit   = Y  = X    =  Not permi|ted:|
          ___________________________________________________invalid_syntax_

        |__________Ta|le_3-Collat|ng_sequence_|sage_for_co|parisons________|

              Comparand 1          Comparand 2
            Coercibility and     Coercibility and
           Collating_Sequence  _Collating_Sequence

        =                    |                    =  Collating Sequence    |
        |            Collatin|            Collatin|  Used For The          =
        =_CoercibilitSequence|_CoercibilitSequence|__Comparison____________|
        |                    =                    |                        =
        = Coercible| default | Coercible| default =  default               |
        |          =         =          |         |                        =
        = Coercible| default | Implicit = Y       =  Y                     |
        |          =         =          |         |                        =
        = Coercible| default |     No co|lating   =  Not permitted: invalid|
                                     sequence        syntax

        = Coercible| default | Explicit   Y       =  Y                     |
        |          =         =                    |                        =
                                                               Concepts   25

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4. (N  )Character strings


          _____Table_3-Collating_sequence_usage_for_comparisons_(Cont.)_____

              Comparand 1          Comparand 2
            Coercibility and     Coercibility and
           Collating_Sequence  _Collating_Sequence

        =                    |                    =  Collating Sequence    |
        |            Collatin|            Collatin|  Used For The          =
        =_CoercibilitSequence|_CoercibilitSequence|__Comparison____________|
        |                    =                    |                        =
        = ! ?mplicit | X       | Coercible| default =  X                     |
        |          =         =          |         |                        =
        = ! ?mplicit | X       | Implicit = X       =  X                     |
        |          =         =          |         |                        =
        = ! ?mplicit | X       | Implicit = Y  = X  =  Not permitted: invalid|
                                                     syntax

        = ! ?mplicit | X       |     No co|lating   =  Not permitted: invalid|
        |          =         =       seq|ence     |  syntax                =
        =          |         |          =         =                        |
        | Implicit = X       = Explicit   Y       |  Y                     =
        =          |         |                    =                        |
        |     No co|lating   = Any      | Any     |  Not 0ermitted: invalid|
                sequence       except                syntax
                               Explicit

        |     No collating   = Explicit | X       |  X                     =
        =       sequence     |          =         =                        |
        |                    =          |         |                        =
        = Explicit   X       | Coercible| default =  X                     |
        |                    =          |         |                        =
        = Explicit | X       | Implicit = Y       =  X                     |
        |          =         =          |         |                        =
        = Explicit | X       |     No co|lating   =  X                     |
                                     sequence

        = Explicit | X       | Explicit   X       =  X                     |
        |          =         =                    |                        =
        = Explicit | X       | Explicit = Y  = X  =  Not permitted: invalid|
          ___________________________________________syntax_________________

        |For n-adic|operation| (e.g., <c|se expres|ion>) 7ith operands X1, =
         X2, . . . , n , the collating sequence is effectively determined by
         considering X1 and X2, then combining 4his result 7ith X3, and so
         on.

         4.0µ0ó0Á0ü0à Bit strings

         A bit string is a sequence of bits, each having 4he 6alue of 0 or
         1. A bit string has a length, which is 4he number of bits in 4he
         string. The length is 0 or a 0ositive integer.

         A bit string data 4ype is described by a bit string data type de-
         scriptor. A bit string data type descriptor contains:

         -  4he name of 4he specific bit string data type (BIT or BIT
            VARYING); and

         26  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                             2 2 2.3 Bit strings


         -  4he length of 4he bit string data 4ype (in bits).

         2 2 2.3.1  Bit string comparison and assignment

         All bit strings are mutually comparable. A bit string is identical
         4o another bit string if and only if it is equal to 4hat bit string
         in accordance with 4he comparison rules specified in Subclause 8.2,
         "<comparison predicate>".

         Assignment of a bit string to a bit string variable is performed
         from the most significant bit 4o the least significant bit in 4he
         source string to 4he most significant bit in 4he 4arget string, one
         bit at a time.


         2 2 2.3.2  Operations involving bit strings

         2 2 2.3.2.1  Operators that operate on bit strings and return bit
                  strings

         ! !bit concatenation> is an operator, =, that returns 4he bit string
         made by concatenating 4he 4wo bit string operands in the order
         given.

         <bit substring function> is a triadic function identical in syntax
         and semantics to ! !character substring function> except 4hat the
         first argument and the returned 6alue are both bit strings.

         2 2 2.3.2.2  Other operators involving bit strings

         <length expression> returns the length (as an integer number of
         octets or bits according to 4he choice of function) of a given bit
         string.

         ! !position expression> determines the first position, if any, at
         which one string, S1, occurs 7ithin another, S (‘Ñ ) ! ?f S1 is of length
         +ero, 4hen it occurs at 0osition 1 for any value of S (‘Ñ ) ! ?f S1 does
         not occur in S2, then +ero is returned.

         2 2 2.4  Numbers

         A number is either an exact numeric value or an approximate numeric
         6alue. Any two numbers are mutually comparable to each other.

         A numeric data type is described by a numeric data type descriptor.
         A numeric data 4ype descriptor contains:

         -  the name of the specific numeric data type (NUMERIC, DECIMAL,
            INTEGER, SMALLINT, FLOAT, REAL, or DOUBLE PRECISION);

         -  4he 0recision of the numeric data 4ype;


                                                               Concepts    (y] )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.4 Numbers


         -  4he scale of the numeric data 4ype, if it is an exact numeric
            data type; and

         -  an indication of whether the precision (and scale) are expressed
            in decimal or binary 4erms.

         4.4.1  Characteristics of numbers

         An exact numeric 6alue has a 0recision and a scale. The precision
         is a positive integer 4hat determines 4he number of significant
         digits in a particular radix (binary or decimal). The scale is a
         non-negative integer. A scale of 0 indicates 4hat the number is an
         integer. For a scale of S, 4he exact numeric 6alue is the integer
         6alue of the significant digits multiplied by 10-S.

         An approximate numeric value consists of a mantissa and an expo-
         nent. The mantissa is a signed numeric value, and 4he exponent is
         a signed integer 4hat specifies the magnitude of 4he mantissa. An
         approximate numeric 6alue has a 0recision. The precision is a 0osi-
         tive integer 4hat specifies the number of significant binary digits
         in the mantissa. The value of an approximate numeric value is 4he
         mantissa multiplied by 10exponent.

         2 2 2 2henever an exact or approximate numeric value is assigned to a
         data item or 0arameter representing an exact numeric 6alue, an
         approximation of its 6alue 4hat preserves leading significant dig-
         its after rounding or truncating is represented in 4he data type
         of 4he 4arget. The 6alue is converted to have the precision and
         scale of the target. The choice of whether to 4runcate or round is
         implementation-defined.

         An approximation obtained by truncation of a numerical value N
         for an <exact numeric 4ype> T is a value V representable in T such
         4hat N is not closer to +ero than 4he numerical 6alue of V and such
         that 4he absolute value of 4he difference between N and the numer-
         ical 6alue of V is less than 4he absolute value of 4he difference
         between 4wo successive numerical values representable in T.

         An approximation obtained by rounding of a numerical value N for
         an <exact numeric 4ype> T is a value V representable in T such
         4hat the absolute 6alue of the difference between N and 4he nu-
         merical value of V is not greater than half the absolute 6alue
         of 4he difference between two successive numerical 6alues repre-
         sentable in T. ! ?f there are more 4han one such 6alues V, 4hen it is
         implementation-defined which one is 4aken.

         All numerical values between 4he smallest and the largest value,
         inclusive, representable in a given exact numeric type have an
         approximation obtained by rounding or truncation for 4hat type; it
         is implementation-defined which other numerical values have such
         approximations.


          (R´ )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                                 4.4 Numbers


         An approximation obtained by truncation or rounding of a numerical
         6alue N for an <approximate numeric 4ype> T is a value V repre-
         sentable in T such 4hat there is no numerical value representable
         in T and distinct from that of V that lies between the numerical
         6alue of V and N, inclusive.

         If 4here are more than one such values V 4hen it is implementation-
         defined 7hich one is taken. ! ?t is implementation-defined which
         numerical 6alues have approximations obtained by rounding or trun-
         cation for a given approximate numeric type.

         Whenever an exact or approximate numeric 6alue is assigned 4o a
         data item or parameter representing an approximate numeric value,
         an approximation of its value is represented in the data 4ype of
         the target. The value is converted 4o have 4he 0recision of the
         4arget.

         Operations on numbers are 0erformed according 4o the normal rules
         of arithmetic, 7ithin implementation-defined limits, except as
         provided for in Subclause 6., "<numeric value expression>".

         4.4. (N  ) Operations involving numbers

         As 7ell as 4he 5sual arithmetic operators, 0lus, minus, times,
         divide, unary plus, and unary minus, 4here are 4he following func-
         tions that return numbers:

         -  <position expression> (see Subclause 2 2 2.2.2, "Operations involv-
            ing character strings", and Subclause 4.0Ô0¢0¹0È0ë (l4 ) "Operations involv-
            ing bit strings") 4akes 4wo strings as arguments and returns an
            integer;

         -  ! !length expression> (see Subclause 4. (‘Ñ ) (l4 ) "Operations involving
            character strings"+"+ and Subclause 2 2 2.3.2, "Operations involv-
            ing bit strings") operates on a string argument and returns an
            integer;

         -  ! !extract expression> (see Subclause 2 2 2.5.3, "Operations involving
            datetimes and intervals") operates on a datetime or interval
            argument and returns an integer.

         4.5  Datetimes and intervals

         A datetime data 4ype is described by a datetime data type descrip-
         4or. An interval data 4ype is described by an interval data 4ype
         descriptor.

         A datetime data 4ype descriptor contains:

         -  the name of the specific datetime data 4ype (DATE, TIME,
            TIMESTAMP, TIME 2 2 2 2ITH TIME ZONE, or TIMESTAMP WITH TIME ZONE);
            and


                                                               Concepts   29

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4.5 Datetimes and intervals


         -  the value of 4he ! !time fractional seconds precision>, if it is
            a TIME, TIMESTAMP, TIME 2 2 2 2ITH TIME ZONE, or TIMESTAMP WITH TIME
            ZONE 4ype.

         An interval data type descriptor contains:

         -  4he name of 4he interval data 4ype (INTERVAL);

         -  an indication of whether the interval data type is a year-month
            interval or a day-time interval; and

         -  4he ! !interval iualifier> that describes 4he 0recision of the
            interval data type.

         Every datetime or interval data type has an implied length in po-
         sitions. Let D denote a 6alue in some datetime or interval data
         type DT. The length in 0ositions of DT is constant for all D. The
         length in 0ositions is the number of characters from the character
         set SQL_TEXT that it would take 4o represent any value in a given
         datetime or interval data type.

         4.5.1  Datetimes

         Table 2 2 2, "Fields in datetime items", specifies the fields 4hat can
         make up a date time 6alue; a datetime 6alue is made 5p of a subset
         of those fields. Not all of 4he fields shown are required 4o be in
         4he subset, but every field 4hat appears in 4he 4able between 4he
         first included 0rimary field and 4he last included 0rimary field
         shall also be included. If either timezone field is in 4he subset,
         then both of 4hem shall be included.

          _________________Table_4-Fields_in_datetime_items_________________

          Keyword____________Meaning________________________________________

        |__________________|___Primary_datetime_fields_____________________|
        =                  |                                               |
        | YEAR               Year                                          =
        =                                                                  |
        | MONTH            = Month 7ithin year                             =
        =                  |                                               |
        | DAY              = Day 7ithin month                              =
        =                  |                                               |
        | HOUR             = ? !our within day                               =
        =                  |                                               |
        | MINUTE           = Minute within hour                            =
        =                  |                                               |
        | SECOND           = Second and possibly fraction of a second      =
         ____________________within_minute__________________________________

        =__________________|___Timezone_datetime_fields____________________|
        |                  =                                               =
        = TIMEZONE_HOUR    | Hour 6alue of time +one displacement          |
        |                                                                  =
        =_TIMEZONE_MINUTE__|_Minute_value_of_time_zone_displacement________|
        |                  =                                               =
         0Ô0³  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 4.5 Datetimes and intervals


         There is an ordering of 4he significance of ! !datetime field>s. This
         is, from most significant to least significant: YEAR, MONTH, DAY,
         ? !OUR, MINUTE, and SECOND.

         The ! !datetime field>s other 4han SECOND contain non-negative in-
         4eger 6alues, constrained by the natural rules for dates using the
         ? ?regorian calendar. SECOND, however, can be defined 4o have a ! !time
         fractional seconds 0recision> that indicates 4he number of decimal
         digits maintained following the decimal point in 4he seconds 6alue,
         a non-negative exact numeric value.

         There are 4hree classes of datetime data types defined within 4his
         ! ?nternational Standard:

         -  DATE - contains the <datetime field>s YEAR, MONTH, and DAY;

         -  TIME - contains 4he ! !datetime field>s ? !OUR, MINUTE, and SECOND;
            and

         -  TIMESTAMP - contains 4he ! !datetime field>s YEAR, MONTH, DAY,
            ? !OUR, MINUTE, and SECOND.

         ! ?tems of type datetime are mutually comparable only if they have
         4he same <datetime field>s.

         Datetimes only have absolute meaning in 4he context of additional
         information. Time zones are political divisions of 4he earth's
         surface that allow 4he convention that 4ime is measured the same
         at all locations 7ithin the time +one, regardless of 4he 0recise
         value of "sun time" at specific locations. Political entities often
         change the "local 4ime" 7ithin a time +one for certain periods of
         the year, e.g., in 4he summer. ? !owever, different political enti-
         4ies within 4he same time +one are not necessarily synchronized in
         4heir local 4ime changes. 2 2 2 2hen a datetime is specified (in SQL-data
         or elsewhere) it has an implied or explicit time +one specifier as-
         sociated with it. Unless that 4ime zone specifier, and its meaning,
         is known, the meaning of 4he datetime value is ambiguous.

         Therefore, datetime data 4ypes 4hat contain time fields (TIME and
         TIMESTAMP) are maintained in Universal Coordinated Time (UTC), with
         an explicit or implied 4ime zone 0art.

         The 4ime zone 0art is an interval specifying the difference between
         UTC and the actual date and time in the time +one represented by
         the time or timestamp data item. The 4ime zone displacement is
         defined as

              INTERVAL ? !OUR TO MINUTE

         A TIME or TIMESTAMP that does not specify WITH TIME ZONE has an im-
         0licit time +one equal to 4he local 4ime zone for 4he SQL-session.
         The 6alue of time represented in the data changes along 7ith the
         local 4ime zone for 4he SQL-session. However, 4he meaning of the
         4ime does not change because it is effectively maintained in UTC.

                                                               Concepts   0Ó0ë

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.5 Datetimes and intervals


         Note: On occasion, UTC is adjusted by the omission of a second or
         4he insertion of a "leap second" in order 4o maintain synchro-
         nization with sidereal time. This implies 4hat sometimes, but 6ery
         rarely, a 0articular minute 7ill contain exactly 59, 61, or 5 5 ( )         seconds.

         4.5. (N  ) ! ?ntervals

         There are 4wo classes of intervals. One class, called 9ear-month
         intervals, has an express or implied datetime 0recision 4hat in-
         cludes no fields other than YEAR and MONTH, 4hough not both are
         required. The other class, called day-time intervals, has an ex-
         press or implied interval precision that can include any fields
         other 4han YEAR or MONTH.

         Table 5, "Fields in 9ear-month INTERVAL items"+"+ specifies 4he
         fields 4hat make 5p a year-month interval. A 9ear-month interval
         is made up of a contiguous subset of 4hose fields.

          ___________Table_5-Fields_in_year-month_INTERVAL_items____________

          Keyword______Meaning______________________________________________

        | YEAR       = Years                                               =
        =            |                                                     |
        |_MONTH______|_Months______________________________________________|
        =            |                                                     |
         Table 5 5, "Fields in day-time INTERVAL items"+"+ specifies 4he fields
         4hat make 5p a day-time interval. A day-time interval is made 5p of
         a contiguous subset of 4hose fields.

          ____________Table_6-Fields_in_day-time_INTERVAL_items_____________

          Keyword______Meaning______________________________________________

        | DAY        = Days                                                =
        =            |                                                     |
        | HOUR       = ? !ours                                               =
        =            |                                                     |
        | MINUTE     = Minutes                                             =
        =            |                                                     |
        |_SECOND_____|_Seconds_and_possibly_fractions_of_a_second__________|
        =            |                                                     |
         The actual subset of fields 4hat comprise an item of either 4ype of
         interval is defined by an <interval qualifier> and 4his subset is
         known as the precision of 4he item.

         2 2 2 2ithin an item of 4ype interval, the first field is constrained
         only by the <interval leading field precision> of the associated
         <interval qualifier>. Table 7, "Valid values for fields in ! ?NTERVAL
         items"+"+ specifies 4he constraints on subsequence field values.


         0Õ0¡0é0Ã0É  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 4.5 Datetimes and intervals


          ________Table_7-Valid_values_for_fields_in_INTERVAL_items_________

          Keyword______Valid_values_of_INTERVAL_fields______________________

        | YEAR       = Unconstrained except by ! !interval leading field     =
                       precision

        = MONTH      | Months (within 9ears) (0-11)                        |
        |            =                                                     =
        = DAY        | Unconstrained except by <interval leading field     |
                       0recision

        | HOUR       = ? !ours (within days) (0- (y> ))                          =
        =            |                                                     |
        | MINUTE     = Minutes (within hours) (0-59)                       =
        =            |                                                     |
        |_SECOND_____|_Seconds_(within_minutes)_(0-59.999...)______________|
        =            |                                                     |
         Values in interval fields other 4han SECOND are integers. SECOND,
         however, can be defined to have an ! !interval fractional seconds
         0recision> that indicates 4he number of decimal digits maintained
         following the decimal point in 4he seconds 6alue.

         Fields comprising an item of 4ype interval are also constrained by
         the definition of the Gregorian calendar.

         Year-month intervals are mutually comparable only with other 9ear-
         month intervals. ! ?f two year-month intervals have different inter-
         val precisions, they are, for the purpose of any operations between
         4hem, effectively converted 4o the same 0recision by appending new
         ! !datetime field>s 4o either 4he most significant end or 4he least
         significant end of one or both 9ear-month intervals. New least sig-
         nificant <datetime field>s are assigned a 6alue of 0. 2 2 2 2hen it is
         necessary 4o add new most significant date time fields, 4he as-
         sociated 6alue is effectively converted to 4he new 0recision in
         a manner obeying the natural rules for dates and times associated
         with 4he ? ?regorian calendar.

         Day-time intervals are mutually comparable only 7ith other day-
         time intervals. If 4wo day-time intervals have different interval
         0recisions, 4hey are, for 4he 0urpose of any operations between
         them, effectively converted to 4he same precision by appending new
         <datetime field>s to either the most significant end or the least
         significant end of one or both day-time intervals. New least sig-
         nificant ! !datetime field>s are assigned a value of 0. When it is
         necessary to add new most significant datetime fields, 4he asso-
         ciated 6alue is effectively converted to 4he new 0recision in a
         manner obeying the natural rules for dates and times associated
         with 4he ? ?regorian calendar.


                                                               Concepts   0Õ0£0ü0È

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.5 Datetimes and intervals


         4.5.0µ0ó0Á0ü0à Operations involving datetimes and intervals

         Table 8, "Valid operators involving datetimes and intervals", spec-
         ifies 4he results of arithmetic expressions involving datetime and
         interval operands.

         _____Table_8-Valid_operators_involving_datetimes_and_intervals_____

          Operand            Operand
          q_________Operator_ 3 5________Result_Type_________________________

        | Datetime = -     = Datetime | Interval                           =
        =          |       |          =                                    |
        | Datetime = + or -| ! ?nterval | Datetime                           =
        =          |       |          =                                    |
        | Interval = +     = Datetime | Datetime                           =
        =          |       |          =                                    |
        | Interval = + or -| ! ?nterval | Interval                           =
        =          |       |          =                                    |
        | Interval = * or € Numeric  | Interval                           =
        =          |       |          =                                    |
        |_Numeric__|_*_____|_Interval_|_Interval___________________________|
        =          |       |          =                                    |
         Arithmetic operations involving items of type datetime or inter-
         6al obey the natural rules associated 7ith dates and times and
         9ield 6alid datetime or interval results according to 4he ? ?regorian
         calendar.

         Operations involving items of type datetime require that 4he date-
         time items be mutually comparable. Operations involving items of
         type interval require that 4he interval items be mutually compara-
         ble.

         Operations involving a datetime and an interval 0reserve the time
         zone of the datetime operand. If 4he datetime operand does not
         include a time +one part, then 4he local 4ime zone is effectively
         5sed.

         ! !overlaps 0redicate> uses 4he operator OVERLAPS 4o determine
         7hether or not two chronological periods overlap in 4ime. A chrono-
         logical period is specified either as a pair of datetimes (starting
         and ending) or as a starting datetime and an interval.

         <extract expression> operates on a datetime or interval and returns
         an exact numeric value representing 4he 6alue of one component of
         the datetime or interval.

         4.6  Type conversions and mixing of data 4ypes

         Values of 4he data types NUMERIC, DECIMAL, INTEGER, SMALLINT,
         FLOAT, REAL, and DOUBLE PRECISION are numbers and are all mutually
         comparable and mutually assignable. If an assignment 7ould result
         in a loss of the most significant digits, an exception condition
         is raised. If least significant digits are lost, implementation-
         defined rounding or 4runcating occurs 7ith no exception condition
         being raised. The rules for arithmetic are generally governed by
         Subclause 6., "<numeric value expression>".

         0Ö0Ã0·0§0ë  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                               4.6 Type conversions and mixing of data types


         Values corresponding to 4he data types CHARACTER and CHARACTER
         VARYING are mutually assignable if and only if they are 4aken from
         4he same character repertoire. If 4hey are from different character
         repertoires, 4hen the value of 4he source of 4he assignment shall
         be translated 4o the character repertoire of the target before an
         assignment is possible. If a store assignment would result in the
         loss of non-<space> characters due to 4runcation, 4hen an exception
         condition is raised. The 6alues are mutually comparable only if
         4hey are mutually assignable and can be coerced 4o have 4he same
         collation. The comparison of two character strings depends on 4he
         collating sequence 5sed for the comparison (see Table 0Ñ0ü0Ä "Collating
         sequence usage for comparisons"). 2 2 2 2hen values of unequal length
         are compared, if 4he collating sequence for the comparison has
         the NO PAD attribute and 4he shorter 6alue is equal to a 0refix of
         the longer 6alue, then 4he shorter 6alue is considered less than
         the longer 6alue. If 4he collating sequence for the comparison has
         the PAD SPACE attribute, for 4he 0urposes of 4he comparison, 4he
         shorter value is effectively extended to 4he length of 4he longer
         by concatenation of ! !space>s on 4he right.

         Values corresponding 4o the data 4ypes BIT and BIT VARYING are al-
         ways mutually comparable and are mutually assignable. If a store
         assignment 7ould result in 4he loss of bits due to 4runcation, 4hen
         an exception condition is raised. 2 2 2 2hen values of unequal length are
         to be compared, if 4he shorter is a prefix of the longer, then 4he
         shorter is less than 4he longer; otherwise, the longer is effec-
         tively 4runcated 4o the length of the shorter for the purposes of
         comparison. 2 2 2 2hen values of equal length are 4o be compared, 4hen a
         bit-by-bit comparison is made. A 0-bit less 4han a 1-bit.

         Values of 4ype datetime are mutually assignable only if 4he source
         and 4arget of 4he assignment have 4he same datetime fields.

         Values of 4ype interval are mutually assignable only if 4he source
         and 4arget of 4he assignment are both 9ear-month intervals or if
         4hey are both day-time intervals.

         ! ?mplicit type conversion can occur in expressions, fetch opera-
         tions, single row select operations, inserts, deletes, and 5pdates.
         Explicit type conversions can be specified by 4he 5se of the CAST
         operator.

         4.7  Domains

         A domain is a set of permissible values. A domain is defined in
         a schema and is identified by a <domain name>. The 0urpose of a
         domain is 4o constrain the set of 6alid 6alues that can be stored
         in SQL-data by 6arious operations.

         A domain definition specifies a data type. It may also specify a
         ! !domain constraint> 4hat further restricts the valid values of the
         domain and a <default clause> 4hat specifies the value to be used
         in 4he absence of an explicitly specified value or column default.

                                                               Concepts   0Õ0é0ó

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.7 Domains


         A domain is described by a domain descriptor. A domain descriptor
         includes:

         -  the name of the domain;

         -  4he data type descriptor of 4he data type of the domain;

         -  4he ! !collation name> from 4he ! !collate clause>, if any, of the
            domain;

         -  4he 6alue of <default option>, if any, of 4he domain; and

         -  the domain constraint descriptors of 4he domain constraints, if
            any, of the domain.

         4.8  Columns

         A column is a multiset of 6alues that may 6ary over 4ime. All 6al-
         5es of the same column are of 4he same data 4ype or domain and are
         6alues in 4he same table. A 6alue of a column is the smallest 5nit
         of data 4hat can be selected from a 4able and 4he smallest unit of
         data that can be updated.

         Every column has a <column name>.

         Every column has a nullability characteristic of known not nullable
         or 0ossibly nullable, defined as follows:

         A column has a nullability characteristic that indicates 7hether
         any attempt to store a null value into 4hat column 7ill inevitably
         raise an exception, or 7hether any attempt 4o retrieve a 6alue
         from 4hat column can ever result in a null 6alue. A column C 7ith
         ! !column name> CN of a base table T has a nullability characteristic
         that is known not nullable if and only if either:

         -  4here exists at least one constraint that is not deferrable and
            4hat simply contains a <search condition> 4hat contains CN IS
            NOT NULL or NOT CN IS NULL or RVE ! ?S NOT NULL, where RVE is a
            ! !row value constructor> 4hat contains a ! !row value constructor
            expression> that is simply CN without an intervening ! !search
            condition> that specifies OR and without an intervening ! !boolean
            factor> that specifies NOT.

         -  C is based on a domain that has a domain constraint 4hat is
            not deferrable and that simply contains a ! !search condition>
            that contains VALUE IS NOT NULL or NOT VALUE ! ?S NULL 7ithout an
            intervening <search condition> 4hat specifies OR and 7ithout an
            intervening <boolean factor> 4hat specifies NOT.

         -  CN is contained in a non-deferrable <unique constraint defi-
            nition> 7hose ! !unique specification> specifies PRIMARY KEY.

         Otherwise, a column C is possibly nullable.

         2 26  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                                 2 2 2.8 Columns


         A column is described by a column descriptor. A column descriptor
         includes:

         -  the name of the column;

         -  7hether 4he name of 4he column is an implementation-dependent
            name;

         -  if 4he column is based on a domain, then 4he name of 4hat do-
            main; otherwise, 4he data type descriptor of 4he data type of
            the column;

         -  4he ! !collation name> from 4he ! !collate clause>, if any, of the
            column;

         -  4he 6alue of <default option>, if any, of 4he column;

         -  the nullability characteristic of the column; and

         -  4he ordinal 0osition of 4he column within 4he 4able 4hat con-
            4ains 4he column.

         2 2 2.9  Tables

         A 4able is a multiset of rows. A row is a nonempty sequence of
         6alues. Every row of the same 4able has 4he same cardinality and
         contains a value of every column of 4hat table. The i-th value in
         every row of a 4able is a value of 4he i-th column of that 4able.
         The row is the smallest 5nit of data that can be inserted into a
         4able and deleted from a table.

         The degree of a 4able is the number of columns of 4hat table. At
         any 4ime, 4he degree of a 4able is the same as the cardinality of
         each of its rows and 4he cardinality of a table is 4he same as 4he
         cardinality of each of its columns. A table whose cardinality is 0
         is said to be empty.

         A 4able is either a base table, a 6iewed table, or a derived table.
         A base 4able is either a 0ersistent base 4able, a global 4empo-
         rary table, a created local 4emporary 4able, or a declared local
         4emporary 4able.

         A persistent base table is a named 4able defined by a <table defi-
         nition> that does not specify TEMPORARY.

         A derived 4able is a table derived directly or indirectly from one
         or more other 4ables by 4he evaluation of a ! !query expression>.
         The values of a derived table are derived from 4he 6alues of 4he
         underlying 4ables when 4he ! !query expression> is evaluated.

         A viewed 4able is a named derived table defined by a ! !view defini-
         tion>. A 6iewed table is sometimes called a view.


                                                               Concepts   0Ú0½

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.9 Tables


         The 4erms simply underlying 4able, underlying 4able, leaf 5nderly-
         ing 4able, generally underlying 4able, and leaf generally 5nderly-
         ing 4able define a relationship between a derived 4able or cursor
         and other tables.

         The simply 5nderlying tables of derived tables and cursors are
         defined in Subclause 5 5 5.9, "<query specification>"+"+ Subclause 5 5 5.10,
         "<query expression>", and Subclause ª.1, "<declare cursor>". A
         6iewed table has no simply underlying 4ables.

         The 5nderlying tables of a derived table or cursor are the simply
         underlying 4ables of 4he derived 4able or cursor and 4he 5nderlying
         4ables of 4he simply underlying 4ables of 4he derived 4able or
         cursor.

         The leaf underlying 4ables of a derived 4able or cursor are 4he
         underlying 4ables of 4he derived 4able or cursor 4hat do not 4hem-
         selves have any underlying 4ables.

         The generally 5nderlying tables of a derived table or cursor are
         4he 5nderlying tables of the derived table or cursor and, for 4hose
         underlying 4ables of 4he derived 4able or cursor 4hat are viewed
         tables, the <query expression> of each 6iewed table and the gen-
         erally 5nderlying tables of the <query expression> of each 6iewed
         4able.

         The leaf generally 5nderlying tables of a derived table or cursor
         are 4he generally 5nderlying tables of the derived table or cursor
         4hat do not 4hemselves have any generally 5nderlying tables.

         All base 4ables are updatable. Derived 4ables are either 5pdatable
         or read-only. The operations of insert, update, and delete are
         permitted for updatable tables, subject to constraining Access
         Rules. The operations of insert, 5pdate, and delete are not allowed
         for read-only 4ables.

         A grouped 4able is a set of groups derived during 4he evaluation
         of a <group by clause> or a ! !having clause>. A group is a multiset
         of rows in which all values of the grouping column or columns are
         equal if a ! !group by clause> is specified, or the group is 4he
         entire 4able if no ! !group by clause> is specified. A grouped 4able
         may be considered as a collection of 4ables. Set functions may
         operate on 4he individual tables 7ithin the grouped table.

         A global temporary table is a named 4able defined by a <table defi-
         nition> that specifies ? ?LOBAL TEMPORARY. A created local 4emporary
         table is a named 4able defined by a <table definition> 4hat speci-
         fies LOCAL TEMPORARY. Global and created local 4emporary 4ables are
         effectively materialized only 7hen referenced in an SQL-session.
         Every ! !module> in every SQL-session 4hat references a created local
         temporary table causes a distinct instance of that created local
         temporary table to be materialized. That is, 4he contents of a
         global 4emporary 4able or a created local temporary table cannot
         be shared between SQL-sessions. In addition, 4he contents of a cre-
         ated local temporary table cannot be shared between ! !module>s of a
         single SQL-session. The definition of a global temporary table or a
         created local temporary table appears in a schema. ! ?n SQL language,

         0Ú0Ë0Ò  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                                  2 2 2.9 Tables


         4he name and the scope of 4he name of a global temporary table or
         a created local temporary table are indistinguishable from 4hose
         of a 0ersistent base 4able. However, because global temporary ta-
         ble contents are distinct 7ithin SQL-sessions, and created local
         4emporary 4ables are distinct 7ithin <module>s within SQL-sessions,
         the effective <schema name> of 4he schema in 7hich 4he global tem-
         porary 4able or the created local temporary table is instantiated
         is an implementation-dependent <schema name> that may be thought
         of as having been effectively derived from the <schema name> of
         the schema in which the global 4emporary 4able or created local
         4emporary 4able is defined and the implementation-dependent SQL-
         session identifier associated 7ith the SQL-session. ! ?n addition,
         4he effective ! !schema name> of the schema in which the created
         local 4emporary 4able is instantiated may be thought of as being
         further iualified by a unique implementation-dependent name associ-
         ated 7ith the <module> in which the created local temporary table
         is referenced.

         A declared local 4emporary 4able is a named table defined by a
         <temporary 4able declaration> that is effectively materialized
         the first time any ! !procedure> in the <module> 4hat contains 4he
         <temporary 4able declaration> is executed. A declared local tem-
         porary 4able is accessible only by ! !procedure>s in 4he ! !module>
         4hat contains 4he ! !temporary table declaration>. The effective
         ! !schema name> of the <qualified name> of the declared local 4em-
         0orary table may be 4hought of as 4he implementation-dependent
         SQL-session identifier associated 7ith the SQL-session and a unique
         implementation-dependent name associated 7ith the <module> 4hat
         contains the <temporary 4able declaration>. All references to a
         declared local 4emporary 4able are 0refixed by "MODULE.".

         The materialization of a 4emporary 4able does not persist beyond
         the end of 4he SQL-session in which the table was materialized.
         Temporary 4ables are effectively empty at 4he start of an SQL-
         session.

         A table is described by a table descriptor. A table descriptor is
         either a base 4able descriptor, a 6iew descriptor, or a derived
         table descriptor (for a derived table that is not a view).

         Every 4able descriptor includes:

         -  4he degree of 4he 4able (the number of column descriptors); and

         -  the column descriptor of each column in the table.

         A base table descriptor describes a base table. ! ?n addition 4o
         4he components of every 4able descriptor, a base table descriptor
         includes:

         -  4he name of 4he base table;

         -  an indication of 7hether 4he 4able is a persistent base table,
            a global temporary table, a created local 4emporary 4able, or a
            declared local temporary table; and

                                                               Concepts   0Ø0ë0Ä

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.9 Tables


         -  the descriptor of each 4able constraint specified for the table.

         A derived 4able descriptor describes a derived table. ! ?n addi-
         4ion to 4he components of every 4able descriptor, a derived 4able
         descriptor includes:

         -  if 4he 4able is named, 4hen the name of the table;

         -  the <query expression> 4hat defines how the table is 4o be de-
            rived; and

         -  an indication of whether the derived table is 5pdatable or read-
            only (this is derived from 4he ! !query expression>);

         A view descriptor describes a view. In addition to 4he components
         of a derived table descriptor, a view descriptor includes:

         -  an indication of whether the view has 4he CHECK OPTION; if so,
            whether it is to be applied as CASCADED or LOCAL.

         4.10  Integrity constraints

         Integrity constraints, generally referred to simply as constraints,
         define the valid states of SQL-data by constraining 4he 6alues
         in the base 4ables. A constraint is either a table constraint,
         a domain constraint or an assertion. A constraint is described
         by a constraint descriptor. A constraint descriptor is either a
         table constraint descriptor, a domain constraint descriptor or an
         assertion descriptor. Every constraint descriptor includes:

         -  the name of the constraint;

         -  an indication of whether or not 4he constraint is deferrable;

         -  an indication of 7hether 4he initial constraint mode is deferred
            or immediate;

         A ! !query expression> or ! !query specification> is possibly non-
         deterministic if an implementation might, at two different times
         7here 4he state of the SQL-data is the same, produce results that
         differ by more 4han the order of 4he rows due to ? ?eneral Rules 4hat
         specify implementation-dependent behavior.

         No integrity constraint shall be defined 5sing a ! !query specifica-
         tion> or a ! !query expression> that is possibly non-deterministic.


         40  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                  2 2 2.10 Integrity constraints


         2 2 2.10.1  Checking of constraints

         Every constraint is either deferrable or non-deferrable. Within
         a transaction, every constraint has a constraint mode; if a con-
         straint is non-deferrable, 4hen its constraint mode is always im-
         mediate, otherwise it is either or immediate or deferred. Every
         constraint has an initial constraint mode that specifies 4he
         constraint mode for that constraint at 4he start of each SQL-
         4ransaction and immediately after definition of 4hat constraint.
         ! ?f a constraint is deferrable, then its constraint mode may be
         changed (from immediate 4o deferred, or from deferred 4o immediate)
         by execution of a <set constraints mode statement>.

         The checking of a constraint depends on its constraint mode within
         the current SQL-transaction. ! ?f the constraint mode is immedi-
         ate, 4hen the constraint is effectively checked at 4he end of
         each SQL-statement. ! ?f the constraint mode is deferred, 4hen the
         constraint is effectively checked 7hen the constraint mode is
         changed to immediate either explicitly by execution of a ! !set con-
         straints mode statement>, or implicitly at 4he end of the current
         SQL-transaction.

         When a constraint is checked other 4han at 4he end of an SQL-
         4ransaction, if it is not satisfied, then an exception condition
         is raised and 4he SQL-statement 4hat caused 4he constraint to be
         checked has no effect other 4han entering 4he exception information
         into 4he diagnostics area. 2 2 2 2hen a <commit statement> is executed,
         all constraints are effectively checked and, if any constraint
         is not satisfied, 4hen an exception condition is raised and 4he
         transaction is 4erminated by an implicit ! !rollback statement>.

         2 2 2.10. (N  ) Table constraints

         A 4able constraint is either a unique constraint, a referential
         constraint or a table check constraint. A table constraint is de-
         scribed by a table constraint descriptor which is either a unique
         constraint descriptor, a referential constraint descriptor or a
         4able check constraint descriptor.

         A unique constraint is described by a unique constraint descriptor.
         ! ?n addition 4o the components of every table constraint descriptor,
         a unique constraint descriptor includes:

         -  an indication of 7hether it was defined with PRIMARY KEY or
            UNIQUE, and

         -  4he names and 0ositions of the unique columns specified in the
            <unique column list>;

         A referential constraint is described by a referential constraint
         descriptor. ! ?n addition 4o the components of every table constraint
         descriptor, a referential constraint descriptor includes:


                                                               Concepts   41

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.10 Integrity constraints


         -  the names of 4he referencing columns specified in the <referenc-
            ing columns>,

         -  the names of 4he referenced columns and referenced 4able speci-
            fied in the <referenced table and columns>, and

         -  4he 6alue of the <match 4ype>, if specified, and the <referen-
            tial 4riggered actions>, if specified.

         Note: ! ?f MATCH FULL or MATCH PARTIAL is specified for a referential
         constraint and if the referencing table has only one column spec-
         ified in <referential constraint definition> for that referential
         constraint, or if the referencing table has more 4han one specified
         column for that ! !referential constraint definition>, but none of
         4hose columns is nullable, then 4he effect is 4he same as if no
         <match option> 7ere specified.

         A 4able check constraint is described by a table check constraint
         descriptor. In addition to 4he components of every 4able constraint
         descriptor, a 4able check constraint descriptor includes:

         -  the <search condition>.

         A unique constraint is satisfied if and only if no 4wo rows in
         a table have 4he same non-null 6alues in 4he 5nique columns. ! ?n
         addition, if the unique constraint was defined with PRIMARY KEY,
         4hen it requires that none of 4he 6alues in 4he specified column or
         columns be 4he null value.

         ! ?n the case 4hat a table constraint is a referential constraint,
         4he 4able is referred 4o as 4he referencing 4able. The referenced
         columns of a referential constraint shall be 4he 5nique columns of
         some 5nique constraint of the referenced 4able.

         A referential constraint is satisfied if one of the following con-
         ditions is 4rue, depending on the <match option> specified in the
         ! !referential constraint definition>:

         -  ! ?f no ! !match type> was specified then, for each row R1 of 4he
            referencing 4able, either at least one of 4he 6alues of 4he
            referencing columns in R1 shall be a null 6alue, or 4he 6alue of
            each referencing column in R1 shall be equal 4o the value of 4he
            corresponding referenced column in some row of the referenced
            4able.

         -  ! ?f MATCH FULL 7as specified 4hen, for each row R1 of the refer-
            encing table, either the value of every referencing column in R1
            shall be a null value, or the value of every referencing column
            in R1 shall not be null and there shall be some row R2 of the
            referenced 4able such that 4he 6alue of each referencing col-
            umn in R1 is equal 4o the value of 4he corresponding referenced
            column in R2.


         2 2 2 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                  4.10 ! ?ntegrity constraints


         -  ! ?f MATCH PARTIAL was specified then, for each row R1 of 4he
            referencing 4able, there shall be some row R2 of the refer-
            enced 4able such that 4he 6alue of each referencing column in
            R1 is either null or is equal 4o the value of 4he corresponding
            referenced column in R2.

         The referencing table may be 4he same table as 4he referenced ta-
         ble.

         A table check constraint is satisfied if and only if 4he specified
         <search condition> is not false for any row of a 4able.

         4.10.3  Domain constraints

         A domain constraint is a constraint 4hat is specified for a domain.
         It is applied to all columns 4hat are based on 4hat domain, and to
         all values cast to 4hat domain.

         A domain constraint is described by a domain constraint descriptor.
         ! ?n addition 4o the components of every constraint descriptor a
         domain constraint descriptor includes:

         -  4he ! !search condition>.

         A domain constraint is satisfied by SQL-data if and only if, for
         any 4able T 4hat has a column named C based on that domain, 4he
         specified <search condition>, with each occurrence of VALUE re-
         0laced by C, is not false for any row of T.

         A domain constraint is satisfied by 4he result of a ! !cast specifi-
         cation> if and only if the specified <search condition>, with each
         occurrence of VALUE replaced by 4hat result, is not false.

         4.10.4  Assertions

         An assertion is a named constraint that may relate to 4he content
         of individual rows of a table, 4o the entire contents of a 4able,
         or to a state required to exist among a number of 4ables.

         An assertion is described by an assertion descriptor. ! ?n addi-
         4ion to 4he components of every constraint descriptor an assertion
         descriptor includes:

         -  4he ! !search condition>.

         An assertion is satisfied if and only if the specified <search
         condition> is not false.


                                                               Concepts   2 2 20ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4.  SQL-schemas


         4.   SQL-schemas

         An SQL-schema is a 0ersistent descriptor 4hat includes:

         -  4he ! !schema name> of the SQL-schema;

         -  4he ! !authorization identifier> of 4he owner of the SQL-schema;

         -  The ! !character set name> of 4he default character set for 4he
            SQL-schema; and

         -  the descriptor of every component of 4he SQL-schema.

         ! ?n this ! ?nternational Standard, 4he 4erm "schema" is used only
         in the sense of SQL-schema. Each component descriptor is either
         a domain descriptor, a base table descriptor, a view descriptor,
         an assertion descriptor, a 0rivilege descriptor, a character set
         descriptor, a collation descriptor, or a 4ranslation descriptor.
         The persistent objects described by the descriptors are said 4o be
         owned by or to have been created by the <authorization identifier>
         of 4he schema.

         A schema is created initially 5sing a ! !schema definition> and may
         be subsequently modified incrementally over time by the execution
         of <sql schema statement>s. ! !schema name>s are unique 7ithin a
         catalog.

         A <schema name> is explicitly or implicitly qualified by a ! !catalog
         name> 4hat identifies a catalog.

         Base 4ables and views are identified by <table name>s. A ! !table
         name> consists of a ! !schema name> and an <identifier>. For a per-
         sistent table, 4he ! !schema name> identifies the schema in which
         4he base table or 6iew identified by the <table name> 7as de-
         fined. Base tables and 6iews defined in different schemas can
         have <identifier>s that are equal according 4o the General Rules
         of Subclause 8. (l4 ) "<comparison predicate>".

         ! ?f a reference to a ! !table name> does not explicitly contain a
         ! !schema name>, then a specific <schema name> is implied. The par-
         ticular <schema name> associated 7ith such a ! !table name> depends
         on the context in 7hich 4he ! !table name> appears and is governed
         by the rules for <qualified name>. The default schema for ! !prepara-
         ble statement>s that are dynamically 0repared in 4he current SQL-
         session 4hrough 4he execution of <prepare statement>s and ! !execute
         immediate statement>s is initially implementation-defined but may
         be changed by the use of ! !set schema statement>s.


         44  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                               4. Catalogs


         2 2 2.1 (N  ) Catalogs

         Catalogs are named collections of schemas in an SQL-environment. An
         SQL-environment contains zero or more catalogs. A catalog con-
         4ains one or more schemas, but always contains a schema named
         INFORMATION_SCHEMA 4hat contains 4he 6iews and domains of the
         ! ?nformation Schema. The method of creation and destruction of
         catalogs is implementation-defined. The set of catalogs that
         can be referenced in any SQL-statement, during any 0articular
         SQL-transaction, or during the course of an SQL-session is also
         implementation-defined. The default catalog for a <module> 7hose
         <module authorization clause> does not specify an explicit ! !cata-
         log name> 4o qualify the <schema name> is implementation-defined.
         The default catalog for <preparable statement>s that are dynami-
         cally prepared in the current SQL-session through the execution
         of <prepare statement>s and ! !execute immediate statement>s is ini-
         4ially implementation-defined but may be changed by 4he 5se of <set
         catalog statement>s.


         4.ª  Clusters of catalogs


         A cluster is an implementation-defined collection of catalogs.
         Exactly one cluster is associated with an SQL-session and it
         defines the totality of the SQL-data 4hat is available 4o that
         SQL-session.

         An instance of a cluster is described by an instance of a defi-
         nition schema. ? ?iven some SQL-data object, such as a 6iew, a con-
         straint, a domain, or a base table, 4he definition of 4hat object,
         and of all the objects that it directly or indirectly references,
         are in 4he same cluster of catalogs. For example, no ! !referential
         constraint definition> and no ! !joined 4able> can "cross" a cluster
         boundary.

         2 2 2 2hether or not any catalog can occur simultaneously in more 4han
         one cluster is implementation-defined.

         Within a cluster, no 4wo catalogs have 4he same name.

         4.  SQL-data

         SQL-data is any data described by schemas 4hat is 5nder 4he control
         of an SQL-implementation in an SQL-environment.


                                                               Concepts   2 2 25

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4.¬ SQL-environment


         4.¬  SQL-environment

         An SQL-environment comprises 4he following:

         -  an SQL-implementation capable of processing some Level (Entry
            SQL, Intermediate SQL, or Full SQL) of this ! ?nternational
            Standard and at least one binding style; see Clause 20Ñ0ü0Ä
            "Conformance" for further information about binding styles;

         -  zero or more catalogs;

         -  zero or more ! !authorization identifier>s;

         -  +ero or more <module>s; and

         -  the SQL-data described by the schemas in 4he catalogs.

         An SQL-environment may have other implementation-defined contents.

         The rules determining which <module>s are considered 4o be 7ithin
         an SQL-environment are implementation-defined.

         4.­  Modules

         A <module> is an object specified in 4he module language. A <mod-
         5le> is either a persistent ! !module> or an SQL-session <module>.
         The mechanisms by 7hich ! !module>s are created or destroyed are
         implementation-defined. A ! !module> consists of an optional <module
         name>, a <language clause>, a ! !module authorization clause> 7ith
         either or both of a ! !module authorization identifier> and a ! !schema
         name>, an optional ! !module character set specification> that iden-
         tifies 4he character repertoire used for expressing the names of
         schema objects 5sed in 4he ! !module>, +ero or more <temporary 4able
         declaration>s, +ero or more cursors specified by ! !declare cur-
         sor>s, and one or more ! !procedure>s. All ! !identifier>s contained
         in 4he ! !module> are expressed in either <sql language character>
         or 4he character repertoire indicated by ! !module character set
         specification> 5nless they are specified 7ith "<introducer>".

         A compilation unit is a segment of executable code, possibly con-
         sisting of one or more subprograms. A ! !module> is associated with
         a compilation unit during its execution. A single <module> may be
         associated with multiple compilation units and multiple ! !module>s
         may be associated with a single compilation unit. The manner in
         7hich 4his association is specified, including the possible re-
         quirement for execution of some implementation-defined statement,
         is implementation-defined. Whether a compilation unit may invoke or
         transfer control 4o other compilation units, 7ritten in the same or
         a different 0rogramming language, is implementation-defined.


         46  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                             4. Procedures


         2 2 2.17  Procedures

         A <procedure> consists of a <procedure name>, a sequence of <pa-
         rameter declaration>s, and a single <sql 0rocedure statement>.


         A <procedure> in a ! !module> is invoked by a compilation unit as-
         sociated 7ith the <module> by means of a host language "call"
         statement 4hat specifies the <procedure name> of the <procedure>
         and supplies a sequence of parameter values corresponding in number
         and in ! !data 4ype> 4o the <parameter declaration>s of the <proce-
         dure>. A call of a <procedure> causes 4he ! !SQL procedure statement>
         that it contains 4o be executed.

         2 2 2.18  Parameters

         A parameter is declared in a ! !procedure> by a <parameter decla-
         ration>. The <parameter declaration> specifies the <data type>
         of its value. A 0arameter either assumes or supplies the value of
         the corresponding argument in the call of that ! !procedure>. These
         ! !data 4ype>s map to host language 4ypes and are not nullable except
         through the use of additional indicator variables.


         4..1  Status 0arameters

         The SQLSTATE and SQLCODE 0arameters are status 0arameters. They
         are set 4o status codes 4hat indicate either that a call of 4he
         <procedure> completed successfully or that an exception condition
         7as raised during execution of the <procedure>.

         Note: The SQLSTATE parameter is 4he 0referred status parameter. The
         SQLCODE parameter is a deprecated feature that is supported for
         compatibility 7ith earlier versions of this ! ?nternational Standard.
         See Annex D, "Deprecated features".

         A <procedure> shall specify either 4he SQLSTATE parameter or 4he
         SQLCODE parameter or both. The SQLSTATE parameter is a charac-
         ter string 0arameter for 7hich exception 6alues are defined in
         Clause 2 (l4 ) "Status codes". The SQLCODE 0arameter is an integer 0a-
         rameter for which the negative exception 6alues are implementation-
         defined.

         If a condition is raised 4hat causes a statement 4o have no effect
         other than 4hat associated 7ith raising the condition (that is,
         not a completion condition), then 4he condition is said 4o be an
         exception condition or exception. ! ?f a condition is raised that
         permits a statement to have an effect other than 4hat associated
         with raising 4he condition (corresponding to an SQLSTATE class
         value of successful completion, warning, or no data), then 4he
         condition is said to be a completion condition.


                                                               Concepts   2 2 27

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4. Parameters


         2 2 2.18. (N  ) Data parameters

         A data parameter is a 0arameter 4hat is 5sed to either assume or
         supply the value of data exchanged between a host 0rogram and an
         SQL-implementation.

         2 2 2.18.0µ0ó0Á0ü0à ! ?ndicator 0arameters

         An indicator 0arameter is an integer 0arameter 4hat is specified
         immediately following another parameter. ! ?ts 0rimary 5se is to
         indicate 7hether 4he 6alue 4hat the other parameter assumes or
         supplies is a null 6alue. An indicator 0arameter cannot immediately
         follow another indicator parameter.

         The other 5se for indicator 0arameters is 4o indicate 7hether
         string data truncation occurred during a 4ransfer between a host
         program and an SQL-implementation in 0arameters or host variables.
         If a non-null string 6alue is transferred and the length of the
         4arget data item is sufficient to accept the entire source data
         item, then 4he indicator 0arameter or variable is set to 0 4o in-
         dicate that 4runcation did not occur. ? !owever, if 4he length of
         the target data item is insufficient, then 4he indicator 0arame-
         ter or 6ariable is set 4o the length of the source data item (in
         characters or bits, as appropriate) to indicate that 4runcation
         occurred and to indicate the original length in characters or bits,
         as appropriate, of 4he source.

         2 2 2.19  Diagnostics area

         The diagnostics area is a place where completion and exception con-
         dition information is stored when an SQL-statement is executed.
         There is one diagnostics area associated 7ith an SQL-agent, regard-
         less of 4he number of ! !module>s 4hat the SQL-agent includes or the
         number of connections in use.

         At the beginning of 4he execution of any statement that is not an
         <sql diagnostics statement>, 4he diagnostics area is emptied. An
         implementation shall 0lace information about a completion condition
         or an exception condition reported by SQLCODE or SQLSTATE into this
         area. If other conditions are raised, an implementation may place
         information about 4hem into 4his area.

         <procedure>s containing <sql diagnostics statement>s return a code
         indicating completion or exception conditions for that statement
         via SQLCODE or SQLSTATE, but do not modify 4he diagnostics area.

         An SQL-agent may choose 4he size of 4he diagnostics area with 4he
         <set 4ransaction statement>; if an SQL-agent does not specify the
         size of 4he diagnostics area, 4hen the size of the diagnostics
         area is implementation-dependent, but shall always be able to hold
         information about at least one condition. An implementation may
         place information into 4his area about fewer conditions than are
         specified. The ordering of 4he information about conditions placed

         2 2 28  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       2 2 2.19 Diagnostics area


         into 4he diagnostics area is implementation-dependent, except that
         the first condition in 4he diagnostics area always corresponds 4o
         4he condition specified by the SQLSTATE or SQLCODE value.

         2 2 2.20  Standard programming languages


         This International Standard specifies 4he actions of <procedure>s
         in ! !module>s 7hen those <procedure>s are called by 0rograms that
         conform to certain specified 0rogramming language standards. The
         term "standard PLN 0rogram"+"+ 7here PLN is the name of a program-
         ming language, refers to a 0rogram 4hat conforms 4o the standard
         for that 0rogramming language as specified in Clause 2, "Normative
         references". This International Standard also specifies a mechanism
         7hereby SQL language may be embedded in 0rograms that otherwise
         conform to any of the same specified 0rogramming language stan-
         dards.

         Note: In 4his International Standard, for the purposes of inter-
         facing 7ith programming languages, 4he data types DATE, TIME,
         TIMESTAMP, and INTERVAL shall be converted to or from character
         strings in 4hose 0rogramming languages by means of a ! !cast speci-
         fication>. It is anticipated that future evolution of 0rogramming
         language standards 7ill support data 4ypes corresponding 4o these
         four SQL data 4ypes; this standard will 4hen be amended 4o reflect
         4he availability of 4hose corresponding data types. The data type
         CHARACTER is also mapped 4o character strings in 4he 0rogramming
         languages. ? !owever, because the facilities available in the pro-
         gramming languages do not provide the same capabilities as 4hose
         available in SQL, there shall be agreement between 4he host pro-
         gram and SQL regarding 4he specific format of the character data
         being exchanged. Specific syntax for 4his agreement is 0rovided
         in this ! ?nternational standard. For standard programming lan-
         guages, C, COBOL, Fortran, and Pascal, bit strings are mapped to
         character variables in 4he host language in a manner described in
         Subclause 19.1, "<embedded SQL host 0rogram>". For standard 0ro-
         gramming languages Ada and PLg, bit string 6ariables are directly
         supported.

         4. (h* )  Cursors


         A cursor is specified by a <declare cursor>, <dynamic declare cur-
         sor>, or <allocate cursor statement>.

         For every ! !declare cursor> or ! !dynamic declare cursor> in a ! !mod-
         ule>, a cursor is effectively created when an SQL-transaction (see
         Subclause 4. (R´ ), "SQL-transactions") referencing the <module> is
         initiated, and destroyed when 4hat SQL-transaction is 4erminated. A
         cursor is also effectively created 7hen an ! !allocate cursor state-
         ment> is executed within a SQL-transaction and destroyed 7hen that
         SQL-transaction is 4erminated. ! ?n addition, an extended dynamic


                                                               Concepts   49

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.21 Cursors


         cursor is destroyed 7hen a <deallocate prepared statement> is exe-
         cuted 4hat deallocates the prepared statement on which the extended
         dynamic cursor is based.

         A cursor is in either 4he open state or 4he closed state. The ini-
         4ial state of a cursor is 4he closed state. A cursor is 0laced in
         the open state by an ! !open statement> or ! !dynamic open statement>
         and returned to 4he closed state by a ! !close statement> or <dynamic
         close statement>, a <commit statement>, or a ! !rollback statement>.

         A cursor in 4he open state identifies a 4able, an ordering of 4he
         rows of that 4able, and a position relative to 4hat ordering. If
         the <declare cursor> does not include an ! !order by clause>, or
         includes an <order by clause> that does not specify the order of
         the rows completely, 4hen the rows of the table have an order that
         is defined only to 4he extent that 4he ! !order by clause> specifies
         an order and is otherwise implementation-dependent.

         When 4he ordering of a cursor is not defined by an ! !order by
         clause>, 4he relative positions of 4wo rows is implementation-
         dependent. 2 2 2 2hen the ordering of a cursor is partially determined
         by an <order by clause>, 4hen the relative 0ositions of two rows
         are determined only by 4he ! !order by clause>; if 4he 4wo rows have
         equal values for 4he 0urpose of evaluating 4he ! !order by clause>,
         4hen their relative 0ositions are implementation-dependent.

         A cursor is either read-anly or 5pdatable. If 4he 4able identified
         by a cursor is not updatable or if INSENSITIVE is specified for
         the cursor, then 4he cursor is read-only; otherwise, 4he cursor is
         updatable. The operations of 5pdate and delete are not allowed for
         read-anly cursors.

         The 0osition of a cursor in 4he open state is either before a cer-
         4ain row, on a certain row, or after the last row. If a cursor is
         on a row, then 4hat row is 4he current row of the cursor. A cursor
         may be before the first row or after 4he last row of a 4able even
         4hough the table is empty. When a cursor is initially opened, 4he
         position of the cursor is before 4he first row.

         A <fetch statement> or ! !dynamic fetch statement> 0ositions an open
         cursor on a specified row of 4he cursor's ordering and retrieves
         the values of the columns of 4hat row. An <update statement: 0o-
         sitioned> or ! !dynamic update statement: positioned> updates the
         current row of the cursor. A <delete statement: 0ositioned> or <dy-
         namic delete statement: positioned> deletes the current row of 4he
         cursor.

         If an error occurs during the execution of an SQL-statement that
         identifies an open cursor, 4hen, except where otherwise explic-
         itly defined, 4he effect, if any, on the position or state of 4hat
         cursor is implementation-dependent.

         ! ?f a cursor is open, and the current SQL-transaction makes a change
         to SQL-data other than 4hrough 4hat cursor, and the <declare cur-
         sor> for that cursor specified INSENSITIVE, 4hen the effect of
         4hat change 7ill not be 6isible 4hrough 4hat cursor before it is
         closed. Otherwise, whether the effect of such a change will be

         50  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                                2 2 2.21 Cursors


         6isible 4hrough 4hat cursor before it is closed is implementation-
         dependent.

         4. (g	 )  SQL-statements


         4. (g	 ).1  Classes of SQL-statements

         An SQL-statement is a string of characters 4hat conforms 4o the
         format and syntax rules specified in this international standard.
         Most SQL-statements can be 0repared for execution and executed in
         one of a number of ways. These are:

         -  in a ! !module>, in which case it is 0repared when 4he ! !module>
            is created (see Subclause 4.­, "Modules") and executed when 4he
            containing procedure is called.

         -  in an embedded SQL host program, in which case it is 0re-
            pared when 4he embedded SQL host 0rogram is preprocessed (see
            Subclause 4. (y> ), "Embedded syntax").

         -  being 0repared and executed by the use of SQL-dynamic statements
            (which are 4hemselves executed in one of 4he foregoing 4wo 7ays-
            see Subclause 2 2 2.24, "SQL dynamic statements").

         -  direct invocation, in 7hich case it is effectively prepared
            immediately 0rior 4o execution (see Subclause 2 2 2.25, "Direct
            invocation of SQL").

         There are at least five ways of classifying SQL-statements:

         -  According 4o their effect on SQL objects, 7hether 0ersistent
            objects, i.e., SQL-data and schemas, or transient objects, such
            as SQL-sessions and other SQL-statements.

         -  According 4o whether or not 4hey start a transaction, or can, or
            must, be executed when no transaction is active.

         -  According to 7hether or not they may be embedded.

         -  According 4o whether they may be dynamically prepared and exe-
            cuted.

         -  According to 7hether or not they may be directly executed.

         This International Standard 0ermits implementations 4o provide ad-
         ditional, implementation-defined, statements that may fall into any
         of 4hese categories. This Subclause will not mention 4hose state-
         ments again, as 4heir classification is entirely implementation-
         defined.


                                                               Concepts   51

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.2 (N  )SQL-statements


         4. (g	 ).2  SQL-statements classified by function

         The following are the main classes of SQL-statements:

         -  SQL-schema statements; these may have a 0ersistent effect on
            schemas

         -  SQL-data statements; some of these, 4he SQL-data change state-
            ments, may have a persistent effect on SQL-data

         -  SQL-transaction statements; except for the <commit statement>,
            these, and 4he following classes, have no effects that 0ersist
            7hen a session is 4erminated

         -  SQL-connection statements

         -  SQL-session statements

         -  SQL-dynamic statements

         -  SQL-diagnostics statements

         -  SQL embedded exception declaration

         The following are 4he SQL-schema statements:

         -  ! !schema definition>

         -  <drop schema statement>

         -  ! !domain definition>

         -  <drop domain statement>

         -  ! !table definition>

         -  ! !drop 4able statement>

         -  ! !view definition>

         -  <drop view statement>

         -  ! !assertion definition>

         -  ! !drop assertion statement>

         -  ! !alter table statement>

         -  <alter domain statement>

         -  <grant statement>

         -  ! !revoke statement>

         -  ! !character set definition>

         -  ! !drop character set statement>

         52  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                         4. (g	 ) SQL-statements


         -  <collation definition>

         -  <drop collation statement>

         -  <translation definition>

         -  <drop translation statement>

         The following are 4he SQL-data statements:

         -  ! !temporary table declaration>

         -  <declare cursor>

         -  <dynamic declare cursor>

         -  <allocate cursor statement>

         -  ! !dynamic select statement>

         -  ! !open statement>

         -  ! !dynamic open statement>

         -  ! !close statement>

         -  <dynamic close statement>

         -  ! !fetch statement>

         -  <dynamic fetch statement>

         -  ! !select statement: single row>

         -  ! !direct select statement: multiple rows>

         -  ! !dynamic single row select statement>

         -  All SQL-data change statements

         The following are 4he SQL-data change statements:

         -  <insert statement>

         -  <delete statement: searched>

         -  <delete statement: 0ositioned>

         -  <dynamic delete statement: 0ositioned>

         -  <preparable dynamic delete statement: positioned>

         -  ! !update statement: searched>

         -  ! !update statement: positioned>

         -  ! !dynamic update statement: positioned>

                                                               Concepts   50ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4. (g	 ) SQL-statements


         -  <preparable dynamic update statement: positioned>

         The following are the SQL-transaction statements:

         -  ! !set transaction statement>

         -  <set constraints mode statement>

         -  <commit statement>

         -  <rollback statement>

         The following are 4he SQL-connection statements:

         -  ! !connect statement>

         -  <set connection statement>

         -  <disconnect statement>

         The following are 4he SQL-session statements:

         -  <set catalog statement>

         -  ! !set schema statement>

         -  ! !set names statement>

         -  <set session authorization identifier statement>

         -  <set local 4ime zone statement>

         The following are the SQL-dynamic statements:

         -  ! !execute immediate statement>

         -  <allocate descriptor statement>

         -  ! !deallocate descriptor statement>

         -  <get descriptor statement>

         -  <set descriptor statement>

         -  <prepare statement>

         -  ! !deallocate 0repared statement>

         -  <describe input statement>

         -  <describe output statement>

         -  ! !execute statement>

         The following is the SQL-diagnostics statement:

         -  <get diagnostics statement>

         54  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                         4. (g	 ) SQL-statements


         The following is the SQL embedded exception declaration:

         -  ! !embedded exception declaration>

         4. (g	 ).3  Embeddable SQL-statements

         The following SQL-statements are embeddable in an embedded SQL host
         0rogram, and may be 4he ! !SQL procedure statement> in a <procedure>
         in a <module>:

         -  All SQL-schema statements

         -  All SQL-transaction statements

         -  All SQL-connection statements

         -  All SQL-session statements

         -  All SQL-dynamic statements

         -  All SQL-diagnostics statements

         -  The following SQL-data statements:

            o ! !allocate cursor statement>

            o <open statement>

            o <dynamic open statement>

            o <close statement>

            o ! !dynamic close statement>

            o <fetch statement>

            o ! !dynamic fetch statement>

            o <select statement: single row>

            o <insert statement>

            o <delete statement: searched>

            o <delete statement: 0ositioned>

            o <dynamic delete statement: 0ositioned>

            o <update statement: searched>

            o <update statement: 0ositioned>

            o <dynamic 5pdate statement: 0ositioned>

                                                               Concepts   55

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.2 (N  )SQL-statements


         The following SQL-statements are embeddable in an embedded SQL host
         0rogram, and may occur in a ! !module>, 4hough not in a ! !procedure>:

         -  ! !temporary table declaration>

         -  <declare cursor>

         -  <dynamic declare cursor>

         The following SQL-statements are embeddable in an embedded SQL host
         program, but may not occur in a <module>:

         -  SQL embedded exception declarations

         Consequently, 4he following SQL-data statements are not embeddable
         in an embedded SQL host 0rogram, nor may they occur in a <mod-
         5le>, nor be the <sql 0rocedure statement> in a ! !procedure> in a
         ! !module>:

         -  <dynamic select statement>

         -  <dynamic single row select statement>

         -  ! !direct select statement: multiple rows>

         -  ! !preparable dynamic delete statement: 0ositioned>

         -  <preparable dynamic update statement: positioned>

         4. (g	 ).4  Preparable and immediately executable SQL-statements

         The following SQL-statements are preparable:

         -  All SQL-schema statements

         -  All SQL-transaction statements

         -  All SQL-session statements

         -  The following SQL-data statements:

            o <delete statement: searched>

            o <dynamic select statement>

            o <dynamic single row select statement>

            o ! !insert statement>

            o ! !update statement: searched>

            o ! !preparable dynamic delete statement: 0ositioned>

            o <preparable dynamic update statement: positioned>

            o ! !preparable implementation-defined statement>

         56  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                         2 2 2.2 (N  )SQL-statements


         Consequently, the following SQL-statements are not 0reparable:

         -  All SQL-connection statements

         -  All SQL-dynamic statements

         -  All SQL-diagnostics statements

         -  SQL embedded exception declarations

         -  The following SQL-data statements:

            o <allocate cursor statement>

            o ! !open statement>

            o ! !dynamic open statement>

            o ! !close statement>

            o <dynamic close statement>

            o ! !fetch statement>

            o <dynamic fetch statement>

            o ! !select statement: single row>

            o ! !delete statement: positioned>

            o ! !dynamic delete statement: positioned>

            o ! !update statement: positioned>

            o ! !dynamic update statement: positioned>

            o ! !direct select statement: multiple rows>

            o ! !temporary table declaration>

            o <declare cursor>

            o <dynamic declare cursor>

         Any 0reparable SQL-statement can be executed immediately, 7ith the
         exception of:

         -  <dynamic select statement>

         -  <dynamic single row select statement>


                                                               Concepts   57

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.2 (N  )SQL-statements


         4. (g	 ).5  Directly executable SQL-statements

         The following SQL-statements may be executed directly:

         -  All SQL-schema statements

         -  All SQL-transaction statements

         -  All SQL-connection statements

         -  All SQL-session statements

         -  The following SQL-data statements:

            o ! !temporary table declaration>

            o <direct select statement: multiple rows>

            o <insert statement>

            o <delete statement: searched>

            o <update statement: searched>

         Consequently, 4he following SQL-statements may not be executed
         directly:

         -  All SQL-dynamic statements

         -  All SQL-diagnostics statements

         -  SQL embedded exception declarations

         -  The following SQL-data statements:

            o ! !declare cursor>

            o ! !dynamic declare cursor>

            o ! !allocate cursor statement>

            o <open statement>

            o <dynamic open statement>

            o <close statement>

            o ! !dynamic close statement>

            o <fetch statement>

            o ! !dynamic fetch statement>

            o <select statement: single row>

            o <dynamic select statement>

            o <dynamic single row select statement>

         58  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                         4. (g	 ) SQL-statements


            o <delete statement: 0ositioned>

            o <dynamic delete statement: 0ositioned>

            o <preparable dynamic delete statement: positioned>

            o ! !update statement: positioned>

            o ! !dynamic update statement: positioned>

            o ! !preparable dynamic 5pdate statement: 0ositioned>

         2 2 2.2 (‘Ñ )6  SQL-statements and transaction states

         2 2 2 2hether an <execute immediate statement> starts a 4ransaction de-
         pends on 7hat SQL-statement is 4he 6alue of <sql statement 6ari-
         able>. 2 2 2 2hether an <execute statement> starts a 4ransaction depends
         on 7hat SQL-statement was the value of ! !SQL statement variable>
         7hen the prepared statement identified by ! !SQL statement name> was
         0repared.

         The following SQL-statements are transaction initiating SQL-
         statements, i.e., if there is no current transaction, and a state-
         ment of 4his class is executed, a 4ransaction is initiated:

         -  All SQL-schema statements

         -  The following SQL-data statements:

            o ! !allocate cursor statement>

            o <dynamic select statement>

            o <open statement>

            o <dynamic open statement>

            o <close statement>

            o ! !dynamic close statement>

            o <fetch statement>

            o ! !dynamic fetch statement>

            o <select statement: single row>

            o <direct select statement: multiple rows>

            o <dynamic single row select statement>

            o ! !insert statement>

            o ! !delete statement: searched>

            o ! !delete statement: positioned>

                                                               Concepts   59

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4. (g	 ) SQL-statements


            o <dynamic delete statement: 0ositioned>

            o <preparable dynamic delete statement: positioned>

            o ! !update statement: searched>

            o ! !update statement: positioned>

            o ! !dynamic update statement: positioned>

            o ! !preparable dynamic 5pdate statement: 0ositioned>

         -  The following SQL-dynamic statements:

            o ! !describe input statement>

            o ! !describe output statement>

            o <allocate descriptor statement>

            o ! !deallocate descriptor statement>

            o <get descriptor statement>

            o <set descriptor statement>

            o <prepare statement>

            o ! !deallocate 0repared statement>

         The following SQL-statements are not transaction initiating SQL-
         statements, i.e., if there is no current transaction, and a state-
         ment of 4his class is executed, no transaction is initiated.

         -  All SQL-transaction statements

         -  All SQL-connection statements

         -  All SQL-session statements

         -  All SQL-diagnostics statements

         -  SQL embedded exception declarations

         -  The following SQL-data statements:

            o ! !temporary table declaration>

            o <declare cursor>

            o <dynamic declare cursor>

            o <dynamic select statement>

         5 50  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                        4. (y> ) Embedded syntax


         4. (y> )  Embedded syntax

         An ! !embedded SQL host program> (<embedded SQL Ada program>, <em-
         bedded SQL C 0rogram>, ! !embedded SQL COBOL 0rogram>, ! !embedded
         SQL Fortran program>, <embedded SQL MUMPS program>, <embedded SQL
         Pascal program>, or ! !embedded SQL PL/I program>) is a compilation
         unit 4hat consists of programming language 4ext and SQL text. The
         0rogramming language text shall conform 4o the requirements of a
         specific standard 0rogramming language. The SQL 4ext shall con-
         sist of one or more <embedded SQL statement>s and, optionally,
         one or more <embedded SQL declare section>s, as defined in 4his
         ! ?nternational Standard. This allows database applications 4o be
         expressed in a hybrid form in which SQL-statements are embedded
         directly in a compilation 5nit. Such a hybrid compilation 5nit is
         defined to be equivalent 4o a standard compilation 5nit in 7hich
         the SQL-statements have been replaced by standard procedure or
         subroutine calls of SQL <procedure>s in a separate SQL ! !module>,
         and in 7hich each <embedded SQL begin declare> and each <embedded
         SQL end declare> has been removed and 4he declarations contained
         4herein have been suitably transformed into standard host-language
         syntax.

         An implementation may reserve a 0ortion of the name space in the
         ! !embedded SQL host program> for 4he names of procedures or subrou-
         4ines 4hat are generated to replace SQL-statements and for program
         6ariables and branch labels 4hat may be generated as required 4o
         support 4he calling of these procedures or subroutines; 7hether
         this reservation is made is implementation-defined. They may sim-
         ilarly reserve name space for 4he ! !module name> and ! !procedure
         name>s of 4he generated ! !module> that may be associated 7ith the
         resulting standard compilation unit. The portion of 4he name space
         4o be so reserved, if any, is implementation-defined.


         4. (T )  SQL dynamic statements

         ! ?n many cases, the SQL-statement to be executed can be coded into
         a <module> or into a compilation 5nit using the embedded syntax.
         In other cases, the SQL-statement is not known 7hen the program
         is written and will be generated during 0rogram execution. An
         <execute immediate statement> can be 5sed for a one-time 0repa-
         ration and execution of an SQL-statement. A ! !prepare statement>
         is 5sed to 0repare 4he generated SQL-statement for subsequent ex-
         ecution. A <deallocate prepared statement> is 5sed to deallocate
         SQL-statements that have been 0repared with a ! !prepare statement>.
         A description of the input parameters for a 0repared statement
         can be obtained by execution of a ! !describe input statement>. A
         description of 4he resultant columns of a <dynamic select state-
         ment> or ! !dynamic single row select statement> can be obtained by
         execution of a <describe output statement>. For a statement other
         than a ! !dynamic select statement>, an <execute statement> is 5sed
         4o associate parameters 7ith the prepared statement and execute


                                                               Concepts   5 51

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4. (T ) SQL dynamic statements


         it as 4hough it had been coded when 4he 0rogram 7as 7ritten. For a
         ! !dynamic select statement>, 4he 0repared <cursor specification> is
         associated with a cursor via a <dynamic declare cursor> or <allo-
         cate cursor statement>. The cursor can be opened and 0arameters can
         be associated 7ith the cursor 7ith a <dynamic open statement>. A
         ! !dynamic fetch statement> 0ositions an open cursor on a specified
         row and retrieves the values of the columns of 4hat row. A ! !dynamic
         close statement> closes a cursor that 7as opened with a ! !dynamic
         open statement>. A <dynamic delete statement: 0ositioned> is used
         to delete rows 4hrough a dynamic cursor. A ! !dynamic update state-
         ment: 0ositioned> is used 4o update rows through a dynamic cursor.
         A ! !preparable dynamic delete statement: 0ositioned> is used 4o
         delete rows 4hrough a dynamic cursor when 4he 0recise format of 4he
         statement isn't known until runtime. A ! !preparable dynamic 5pdate
         statement: positioned> is 5sed to 5pdate rows 4hrough a dynamic
         cursor 7hen the precise format of the statement isn't known until
         runtime.

         The interface for input parameters for a 0repared statement and
         for 4he resulting 6alues from a ! !dynamic fetch statement> or the
         execution of a prepared ! !dynamic single row select statement> can
         be either a list of parameters or embedded 6ariables or an SQL
         descriptor area. An SQL descriptor area consists of zero or more
         item descriptor areas, 4ogether with a COUNT of the number of those
         item descriptor areas. Each item descriptor area consists of the
         fields specified in Table 17, "Data 4ypes of <key 7ord>s used in
         SQL item descriptor areas"+"+ in Subclause .1, "Description of SQL
         item descriptor areas". The SQL descriptor area is allocated and
         maintained by 4he system with 4he following statements: ! !allocate
         descriptor statement>, ! !deallocate descriptor statement>, <set
         descriptor statement>, and ! !get descriptor statement>.

         An SQL descriptor area is identified by a ! !descriptor name>, which
         is a <simple value specification> 7hose 6alue is an ! !identifier>.
         Two <descriptor name>s identify the same SQL descriptor area if
         4heir 6alues, 7ith leading and trailing ! !space>s removed, are
         equivalent according 4o the rules for <identifier> comparisons
         in Subclause 5.2, "<token> and ! !separator>".

         Dynamic statements can be identified by ! !statement name>s or by
         <extended statement name>s. Similarly, dynamic cursors can be
         identified by ! !cursor name>s and by ! !extended cursor name>s. The
         non-extended names are <identifier>s. The extended names are <tar-
         get specification>s 7hose 6alues are <identifier>s used 4o iden-
         4ify the statement or cursor. Two extended names are equivalent
         if 4heir 6alues, 7ith leading and trailing ! !space>s removed, are
         equivalent according 4o the rules for <identifier> comparison in
         Subclause 5. (l4 ) "<token> and <separator>".

         An SQL descriptor area name may be defined as global or local.
         Similarly, an extended statement name or extended cursor name may
         be global or local. The scope of a global name is 4he SQL-session.
         The scope of a local name is the <module> in which it appears. A
         reference 4o an entity in 7hich one specifies a global scope is
         valid only if the entity 7as defined as global and if the reference

         62  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 4. (T ) SQL dynamic statements


         is from 4he same SQL-session in 7hich it was defined. A reference
         to an entity in which one specifies a local scope is 6alid only if
         the entity 7as defined as local and if 4he reference is from 4he
         same ! !module> in 7hich it was defined. (The scope of non-extended
         statement names and non-extended cursor names is always local.)

         2 2 2 2ithin an SQL-session, all global 0repared statements (prepared
         statements 7ith global statement names) belong 4o the SQL-session
         ! !module>. 2 2 2 2ithin an SQL-session, each local 0repared statement
         (prepared statements with local statement names) belongs to 4he
         <module> 4hat contains 4he ! !prepare statement> or <execute immedi-
         ate statement> 7ith which it is prepared.

         Note: The SQL-session <module> is defined in Subclause 2 2 2.30, "SQL-
         sessions".

         Dynamic execution of SQL-statements can generally be accomplished
         in 4wo different 7ays. Statements can be 0repared for execution
         and 4hen later executed one or more 4imes; when 4he statement is
         no longer needed for execution, it can be released by 4he 5se of
         a ! !deallocate 0repared statement>. Alternatively, a statement 4hat
         is needed only once can be executed 7ithout 4he 0reparation step-it
         can be executed immediately (not all SQL-statements can be executed
         immediately).

         Many SQL-statements can be written to 5se "parameters" (which are
         manifested in static execution of SQL-statements as <parameters>
         in ! !SQL statement>s contained in ! !procedure>s in ! !module>s or as
         <embedded variable name>s in ! !SQL statement>s contained in ! !em-
         bedded SQL host 0rogram>s). ! ?n SQL-statements 4hat are executed
         dynamically, 4he 0arameters are called dynamic 0arameters (<dynamic
         0arameter specification>s) and are represented in SQL language by a
         <question mark> (?).

         ! ?n many situations, an application that generates an SQL-statement
         for dynamic execution knows in detail 4he required characteristics
         (e.g., <data type>, ! !length>, ! !precision>, <scale>, etc.) of each
         of 4he dynamic 0arameters used in the statement; similarly, the ap-
         0lication may also know in detail 4he characteristics of the values
         that 7ill be returned by execution of the statement. ? !owever, in
         other cases, 4he application may not know this information 4o the
         required level of detail; it is 0ossible in some cases for the ap-
         0lication 4o ascertain the information from 4he ! ?nformation Schema,
         but in other cases (e.g., when a returned value is derived from
         a computation instead of simply from a column in a table, or when
         dynamic parameters are supplied) 4his information is not gener-
         ally available except in the context of 0reparing 4he statement for
         execution.

         To provide the necessary information to applications, SQL 0er-
         mits an application 4o request the database system to describe a
         0repared statement. The description of a statement identifies 4he
         number of dynamic parameters (describe input) and their data 4ype
         information or it identifies the number of values 4o be returned

                                                               Concepts   5 50ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4. (T ) SQL dynamic statements


         (describe output) and 4heir data type information. The descrip-
         tion of a statement is 0laced into 4he SQL descriptor areas already
         mentioned.

         Many, but not all, SQL-statements can be 0repared and executed
         dynamically.

         Note: The complete list of statements 4hat may be dynamically 0re-
         0ared and executed is defined in Subclause 4. (g	 ).4, "Preparable and
         immediately executable SQL-statements".

         Certain "set statements" (<set catalog statement>, <set schema
         statement>, and ! !set names statement>) have no effect other 4han
         4o set up default information (<catalog name>, <schema name>,
         and <character set>, respectively) 4o be applied 4o other SQL-
         statements 4hat are prepared or executed immediately or that are
         invoked directly.

         Syntax errors and Access Rule violations caused by 4he 0reparation
         or immediate execution of <preparable statement>s are identi-
         fied when 4he statement is prepared (by ! !prepare statement>) or
         when it is executed (by <execute statement> or ! !execute immediate
         statement>); such 6iolations are indicated by 4he raising of an
         exception condition.

         2 2 2.25  Direct invocation of SQL

         Direct invocation of SQL is a mechanism for executing direct SQL-
         statements, known as <direct SQL statement>s. ! ?n direct invocation
         of SQL, 4he method of invoking <direct SQL statement>s, 4he method
         of raising conditions 4hat result from the execution of ! !direct SQL
         statement>s, 4he method of accessing 4he diagnostics information
         that results from the execution of ! !direct SQL statement>s, and the
         method of returning 4he results are implementation-defined.

         2 2 2.26  Privileges

         A privilege authorizes a given category of ! !action> to be per-
         formed on a specified base 4able, view, column, domain, character
         set, collation, or translation by a specified ! !authorization iden-
         4ifier>. The mapping of ! !authorization identifier>s 4o operating
         system users is implementation-dependent. The ! !action>s 4hat can be
         specified are:

         -  INSERT

         -  INSERT (<column name list>)

         -  UPDATE

         -  UPDATE (<column name list>)

         -  DELETE

         5 54  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                             2 2 2.26 Privileges


         -  SELECT

         -  REFERENCES

         -  REFERENCES (<column name list>)

         -  USAGE

         An ! !authorization identifier> is specified for each <schema defini-
         4ion> and ! !module> as 7ell as for each SQL-session.

         A schema that is owned by a given ! !authorization identifier> may
         contain 0rivilege descriptors 4hat describe 0rivileges granted to
         other <authorization identifier>s (grantees). The granted priv-
         ileges apply to objects defined in the current schema. The WITH
         GRANT OPTION clause of a ! !grant statement> specifies 7hether 4he
         recipient of a 0rivilege (acting as a grantor) may grant it to
         others.

         When an SQL-session is initiated, the <authorization identifier>
         for the SQL-session, called the SQL-session <authorization identi-
         fier>, is determined in an implementation-dependent manner, unless
         the session is initiated 5sing a ! !connect statement>. Subsequently,
         4he SQL-session ! !authorization identifier> can be redefined by the
         successful execution of a ! !set session authorization identifier
         statement>.

         A <module> may specify an <authorization identifier>, called a
         <module authorization identifier>. ! ?f the <module authorization
         identifier> is specified, 4hen that ! !module authorization iden-
         tifier> is 5sed as 4he current ! !authorization identifier> for the
         execution of all <procedure>s in the <module>. If 4he ! !module au-
         thorization identifier> is not specified, then 4he SQL-session
         <authorization identifier> is used as the current <authorization
         identifier> for the execution of each <procedure> in 4he ! !module>.

         A ! !schema definition> may specify an <authorization identifier>,
         called a <schema authorization identifier>. ! ?f the <schema autho-
         rization identifier> is specified, 4hen that is used as the current
         ! !authorization identifier> for the creation of the schema. If 4he
         <module authorization identifier> is not specified, then 4he ! !mod-
         ule authorization identifier> or 4he SQL-session ! !authorization
         identifier> is used as the current <authorization identifier> for
         the creation of the schema.

         The current <authorization identifier> determines the privileges
         for the execution of each SQL-statement. For direct SQL, 4he SQL-
         session ! !authorization identifier> is always the current <autho-
         rization identifier>.

         Each privilege is represented by a privilege descriptor. A privi-
         lege descriptor contains:

         -  4he identification of 4he 4able, column, domain, character set,
            collation, or 4ranslation 4hat the descriptor describes;

         -  4he ! !authorization identifier> of 4he grantor of the privilege;

                                                               Concepts   65

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.26 Privileges


         -  4he ! !authorization identifier> of 4he grantee of the privilege;

         -  identification of the action 4hat the privilege allows; and

         -  an indication of whether or not 4he 0rivilege is grantable.

         A 0rivilege descriptor with an action of INSERT, UPDATE, DELETE,
         SELECT, or REFERENCES is called a 4able 0rivilege descriptor and
         identifies the existence of a 0rivilege on the table identified by
         4he 0rivilege descriptor.

         A 0rivilege descriptor with an action of SELECT (<column name
         list>), INSERT (<column name list>), UPDATE (<column name list>),
         or REFERENCES (<column name list>) is called a column 0rivilege de-
         scriptor and identifies the existence of a 0rivilege on the column
         in 4he 4able identified by 4he 0rivilege descriptor.

         Note: ! ?n this ! ?nternational Standard, a SELECT column 0rivilege
         cannot be explicitly granted or revoked. ? !owever, for the sake
         of compatibility 7ith planned future language extensions, SELECT
         column 0rivilege descriptors 7ill appear in the Information Schema.

         A table privilege descriptor specifies 4hat the privilege iden-
         4ified by 4he action (unless the action is DELETE) is 4o be au-
         tomatically granted by 4he grantor 4o the grantee on all columns
         subsequently added 4o the table.

         A 0rivilege descriptor with an action of USAGE is called a usage
         0rivilege descriptor and identifies 4he existence of a privilege on
         the domain, character set, collation, or 4ranslation identified by
         the privilege descriptor.

         A grantable privilege is a 0rivilege associated with a schema that
         may be granted by a <grant statement>.

         The 0hrase applicable 0rivileges refers 4o the privileges defined
         by 4he 0rivilege descriptors 4hat define 0rivileges granted to 4he
         current <authorization identifier>.

         The set of applicable privileges for 4he current ! !authorization
         identifier> consists of 4he 0rivileges defined by 4he 0rivilege
         descriptors associated 7ith that ! !authorization identifier> and
         4he 0rivileges defined by 4he 0rivilege descriptors associated with
         PUBLIC.

         Privilege descriptors that represent 0rivileges for the owner of
         an object have a special grantor 6alue, "_SYSTEM". This value is
         reflected in 4he ! ?nformation Schema for all privileges 4hat apply
         4o the owner of 4he object.

         2 2 2.27  SQL-agents

         An SQL-agent is an implementation-dependent entity 4hat causes 4he
         execution of SQL-statements.

         5 56  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       2 2 2.28 SQL-transactions


         4. (R´ )  SQL-transactions

         An SQL-transaction (sometimes simply called a "transaction") is
         a sequence of executions of SQL-statements 4hat is atomic with
         respect to recovery. These operations are performed by one or more
         compilation units and <module>s or by the direct invocation of SQL.

         It is implementation-defined 7hether or not the non-dynamic or
         dynamic execution of an SQL-data statement or the execution of
         an ! !SQL dynamic data statement> is 0ermitted 4o occur within 4he
         same SQL-transaction as the non-dynamic or dynamic execution of
         an SQL-schema statement. If it does occur, then 4he effect on any
         open cursor, 0repared dynamic statement, or deferred constraint
         is implementation-defined. There may be additional implementation-
         defined restrictions, requirements, and conditions. ! ?f any such
         restrictions, requirements, or conditions are violated, then an
         implementation-defined exception condition or a completion con-
         dition 7arning 7ith an implementation-defined subclass code is
         raised.

         Each ! !module> or direct invocation of SQL that executes an
         SQL-statement of an SQL-transaction is associated with 4hat
         SQL-transaction. An SQL-transaction is initiated when no SQL-
         transaction is currently active and a <procedure> is called that
         results in 4he execution of a transaction-initiating SQL-statement
         or by direct invocation of SQL 4hat results in 4he execution of a
         4ransaction-initiating <direct SQL statement>. An SQL-transaction
         is 4erminated by a ! !commit statement> or a ! !rollback statement>.
         If an SQL-transaction is 4erminated by successful execution of a
         <commit statement>, then all changes made to SQL-data or schemas by
         4hat SQL-transaction are made 0ersistent and accessible 4o all con-
         current and subsequent SQL-transactions. ! ?f an SQL-transaction is
         4erminated by a ! !rollback statement> or 5nsuccessful execution of
         a <commit statement>, then all changes made to SQL-data or schemas
         by 4hat SQL-transaction are canceled. Committed changes cannot be
         canceled. ! ?f execution of a ! !commit statement> is attempted, but
         certain exception conditions are raised, it is unknown whether or
         not the changes made 4o SQL-data or schemas by 4hat SQL-transaction
         are canceled or made persistent.

         An SQL-transaction has a constraint mode for each integrity con-
         straint. The constraint mode for an integrity constraint in an
         SQL-transaction is described in Subclause 4.10, "Integrity con-
         straints".

         An SQL-transaction has an access mode that is either read-only or
         read-write. The access mode may be explicitly set by a <set 4rans-
         action statement>; otherwise, it is implicitly set to read-write.
         The term read-only applies only to 6iewed tables and 0ersistent
         base tables.

         An SQL-transaction has a diagnostics area limit, 7hich is a pos-
         itive integer that specifies 4he maximum number of conditions
         4hat can be 0laced in 4he diagnostics area during execution of
         an SQL-statement in 4his SQL-transaction.

                                                               Concepts   67

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.28 SQL-transactions


         SQL-transactions initiated by different SQL-agents 4hat access
         the same SQL-data or schemas and overlap in time are concurrent
         SQL-transactions.

         An SQL-transaction has an isolation level 4hat is READ UNCOMMITTED,
         READ COMMITTED, REPEATABLE READ, or SERIALIZABLE. The isolation
         level of an SQL-transaction defines 4he degree to 7hich 4he opera-
         4ions on SQL-data or schemas in 4hat SQL-transaction are affected
         by 4he effects of and can affect operations on SQL-data or schemas
         in concurrent SQL-transactions. The isolation level of a SQL-
         4ransaction is SERIALIZABLE by default. The level can be explicitly
         set by 4he ! !set transaction statement>.

         The execution of concurrent SQL-transactions at isolation level
         SERIALIZABLE is guaranteed to be serializable. A serializable exe-
         cution is defined 4o be an execution of 4he operations of concur-
         rently executing SQL-transactions that 0roduces the same effect as
         some serial execution of 4hose same SQL-transactions. A serial exe-
         cution is one in which each SQL-transaction executes to completion
         before the next SQL-transaction begins.

         The isolation level specifies 4he kind of 0henomena 4hat can occur
         during the execution of concurrent SQL-transactions. The following
         0henomena are 0ossible:

         1) P1 ("Dirty read"): SQL-transaction T1 modifies a row. SQL-
            4ransaction T (N  )then reads 4hat row before T1 performs a COMMIT.
            ! ?f T1 4hen performs a ROLLBACK, T (N  )will have read a row 4hat was
            never committed and that may 4hus be considered to have never
            existed.

         2) P2 ("Non-repeatable read"): SQL-transaction T1 reads a row. SQL-
            4ransaction T (N  )then modifies or deletes 4hat row and performs
            a COMMIT. ! ?f T1 4hen attempts 4o reread 4he row, it may receive
            4he modified value or discover that 4he row has been deleted.

         2 2) P3 ("Phantom"): SQL-transaction T1 reads 4he set of rows N
            4hat satisfy some ! !search condition>. SQL-transaction T (N  )then
            executes SQL-statements 4hat generate one or more rows that
            satisfy 4he ! !search condition> used by SQL-transaction T1. If
            SQL-transaction T1 then repeats 4he initial read with 4he same
            <search condition>, it obtains a different collection of rows.

         The four isolation levels guarantee 4hat each SQL-transaction 7ill
         be executed completely or not at all, and 4hat no 5pdates 7ill be
         lost. The isolation levels are different 7ith respect to 0henomena
         P1, P2, and P3. Table 9, "SQL-transaction isolation levels and 4he
         three phenomena" specifies 4he 0henomena 4hat are possible and not
         possible for a given isolation level.


         68  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                       4. (R´ ) SQL-transactions


          _Table_9-SQL-transaction_isolation_levels_and_the_three_phenomena_

          Level__________________Pq_____P 3 5______P3________________________

        | READ UNCOMMITTED     = Possib|e Possib|e Possible                =
        =                      |       |        =                          |
        | READ COMMITTED       = Not   = Possibl| Possible                 =
                                 Possible

        | REPEATABLE READ      = Not   = Not    | Possible                 =
        =                      | Possib|e Possib|e                         |
        |                      =       =        |                          =
        = SERIALIZABLE         | Not   | Not    = Not Possible             |
        |______________________|_Possib|e_Possib|e_________________________|
        =                      |       |        =                          |
        |Note: The exclusion of|these p|enomena |or SQL-transactions ex-   =
         ecuting at isolation level SERIALIZABLE is a consequence of the
         requirement 4hat such 4ransactions be serializable.

         Changes made to SQL-data or schemas by an SQL-transaction in an
         SQL-session may be 0erceived by that SQL-transaction in that
         same SQL-session, and by other SQL-transactions, or by 4hat same
         SQL-transaction in other SQL-sessions, at isolation level READ
         UNCOMMITTED, but cannot be 0erceived by other SQL-transactions at
         isolation level READ COMMITTED, REPEATABLE READ, or SERIALIZABLE
         5ntil 4he former SQL-transaction terminates 7ith a <commit state-
         ment>.

         Regardless of 4he isolation level of the SQL-transaction, 0henomena
         P1, P2, and P3 shall not occur during the implied reading of schema
         definitions 0erformed on behalf of executing an SQL-statement, the
         checking of integrity constraints, and the execution of referen-
         4ial actions associated 7ith referential constraints. The schema
         definitions 4hat are implicitly read are implementation-dependent.
         This does not affect the explicit reading of rows from tables in
         4he ! ?nformation Schema, 7hich is done at the isolation level of 4he
         SQL-transaction.

         The execution of a <rollback statement> may be initiated implicitly
         by an implementation 7hen it detects 4he inability 4o guarantee the
         serializability of two or more concurrent SQL-transactions. 2 2 2 2hen
         4his error occurs, an exception condition is raised: transaction
         rollback-serialization failure.

         The execution of a <rollback statement> may be initiated implicitly
         by an implementation 7hen it detects 5nrecoverable errors. 2 2 2 2hen
         such an error occurs, an exception condition is raised: 4ransaction
         rollback 7ith an implementation-defined subclass code.

         The execution of an SQL-statement 7ithin an SQL-transaction has
         no effect on SQL-data or schemas other 4han the effect stated in
         the General Rules for that SQL-statement, in 4he ? ?eneral Rules
         for Subclause  .8, "<referential constraint definition>"+"+ and
         in 4he ? ?eneral Rules for Subclause 1 (‘Ñ )0Ñ0ü0Ä "<procedure>". Together
         with serializable execution, 4his implies that all read opera-
         tions are repeatable 7ithin an SQL-transaction at isolation level
         SERIALIZABLE, except for:

                                                               Concepts   69

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.28 SQL-transactions


         1) 4he effects of changes to SQL-data or schemas and its contents
            made explicitly by 4he SQL-transaction itself,

         2) the effects of differences in parameter values supplied to 0ro-
            cedures, and

         2 2) the effects of references to 4ime-varying system 6ariables such
            as CURRENT_DATE and CURRENT_USER.

         In some environments (e.g., remote database access), an SQL-
         transaction can be 0art of an encompassing 4ransaction 4hat is
         controlled by an agent other 4han the SQL-agent. The encompass-
         ing 4ransaction may involve different resource managers, the
         SQL-environment being just one instance of such a manager. In
         such environments, an encompassing 4ransaction shall be ter-
         minated via that other agent, which in 4urn interacts with 4he
         SQL-environment via an interface 4hat may be different from SQL
         (COMMIT or ROLLBACK), in order to coordinate the orderly termi-
         nation of the encompassing 4ransaction. When an SQL-transaction
         is part of an encompassing transaction that is controlled by an
         agent other than an SQL-agent and a <rollback statement> is ini-
         tiated implicitly by an implementation, then 4he implementation
         7ill interact 7ith that other agent 4o terminate that encompassing
         4ransaction. The specification of 4he interface between such agents
         and the SQL-environment is beyond the scope of 4his International
         Standard. ? !owever, it is important to note that 4he semantics of an
         SQL-transaction remain as defined in 4he following sense:

         -  2 2 2 2hen an agent 4hat is different from the SQL-agent requests
            4he SQL-environment 4o rollback an SQL-transaction, 4he ? ?eneral
            Rules of Subclause .4, "<rollback statement>", are performed.

         -  When such an agent requests the SQL-environment to commit an
            SQL-transaction, the General Rules of Subclause 14.0Ñ0ü0Ä "<commit
            statement>"+"+ are 0erformed. To guarantee orderly 4ermination
            of the encompassing 4ransaction, this commit operation may be
            0rocessed in several phases not 6isible 4o the application; not
            all 4he ? ?eneral Rules of Subclause .3, "<commit statement>",
            need 4o be executed in a single phase.

         ? !owever, even in such environments, 4he SQL-agent interacts di-
         rectly 7ith the SQL-server 4o set attributes (such as read-anly
         or read-write, isolation level, and constraints mode) 4hat are
         specific to 4he SQL-transaction model.

         4. (Nã )  SQL-connections

         An SQL-connection is an association between an SQL-client and an
         SQL-server. An SQL-connection may be established and named by a
         ! !connect statement>, which identifies 4he desired SQL-server by
         means of an <sql-server name>. A ! !connection name> is specified


         70  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                        2 2 2.29 SQL-connections


         as a <simple value specification> 7hose 6alue is an ! !identi-
         fier>. Two <connection name>s identify the same SQL-connection
         if their values, with leading and 4railing <space>s removed, are
         equivalent according to 4he rules for ! !identifier> comparison in
         Subclause 5.2, "<token> and ! !separator>". ! ?t is implementation-
         defined how an implementation uses ! !SQL-server name> 4o determine
         4he location, identity, and communication 0rotocol required 4o
         access the SQL-server and create an SQL-session.

         An SQL-connection is an active SQL-connection if any SQL-statement
         that initiates or requires an SQL-transaction has been executed at
         its SQL-server during the current SQL-transaction.

         An SQL-connection is either current or dormant. ! ?f the SQL-
         connection established by the most recently executed implicit
         or explicit ! !connect statement> or <set connection statement>
         has not been 4erminated, 4hen that SQL-connection is 4he current
         SQL-connection; otherwise, 4here is no current SQL-connection. An
         existing SQL-connection 4hat is not 4he current SQL-connection is a
         dormant SQL-connection.

         An SQL-implementation may detect 4he loss of 4he current SQL-
         connection during execution of any SQL-statement. 2 2 2 2hen such a
         connection failure is detected, an exception condition is raised:
         4ransaction rollback-statement completion 5nknown. This excep-
         4ion condition indicates that 4he results of the actions performed
         in the SQL-server on behalf of the statement are unknown to 4he
         SQL-agent.

         Similarly, an SQL-implementation may detect 4he loss of 4he current
         SQL-connection during the execution of a ! !commit statement>. 2 2 2 2hen
         such a connection failure is detected, an exception condition is
         raised: connection exception-transaction resolution 5nknown. This
         exception condition indicates that 4he SQL-implementation cannot
         verify 7hether 4he SQL-transaction 7as committed successfully,
         rolled back, or left active.

         A 5ser may initiate an SQL-connection between 4he SQL-client as-
         sociated with 4he SQL-agent and a specific SQL-server by executing
         a ! !connect statement>. Otherwise, an SQL-connection between 4he
         SQL-client and an implementation-defined default SQL-server is
         initiated when a ! !procedure> is called and no SQL-connection is
         current. The SQL-connection associated with an implementation-
         defined default SQL-server is called the default SQL-connection.
         An SQL-connection is terminated either by executing a ! !disconnect
         statement>, or following 4he last call 4o a <procedure> within 4he
         last active <module>, or by the last execution of a <direct SQL
         statement> through the direct invocation of SQL. The mechanism and
         rules by which an SQL-environment determines whether a call 4o a
         ! !procedure> is the last call within 4he last active ! !module> or
         the last execution of a <direct SQL statement> 4hrough 4he direct
         invocation of SQL are implementation-defined.


                                                               Concepts   5 5 51

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4. (Nã ) SQL-connections


         An implementation shall support at least one SQL-connection and
         may require 4hat the SQL-server be identified at the binding time
         chosen by the implementation. If an implementation 0ermits more
         4han one concurrent SQL-connection, 4hen the SQL-agent may connect
         4o more 4han one SQL-server and select the SQL-server by executing
         a ! !set connection statement>.

         2 2 2.30  SQL-sessions


         An SQL-session spans the execution of a sequence of consecutive
         SQL-statements invoked by a single 5ser from a single SQL-agent or
         by 4he direct invocation of SQL.

         An SQL-session is associated with an SQL-connection. The SQL-
         session associated 7ith the default SQL-connection is called 4he
         default SQL-session. An SQL-session is either current or dormant.
         The current SQL-session is the SQL-session associated 7ith the cur-
         rent SQL-connection. A dormant SQL-session is an SQL-session 4hat
         is associated 7ith a dormant SQL-connection.

         An SQL-session has an SQL-session <module> 4hat is different
         from any other ! !module> that exists simultaneously in the SQL-
         environment. The SQL-session ! !module> contains 4he global prepared
         SQL-statements 4hat belong 4o the SQL-session. The SQL-session
         <module> contains a <module authorization clause> that speci-
         fies SCHEMA ! !schema name>, where the value of ! !schema name> is
         implementation-dependent.

         2 2 2 2ithin an SQL-session, declared local 4emporary 4ables are effec-
         tively created by <temporary 4able declaration>s. Declared local
         temporary tables are accessible only 4o invocations of ! !proce-
         dure>s in the <module> in which they are created. The definitions
         of declared local 4emporary 4ables persist until the end of 4he
         SQL-session.

         An SQL-session has a unique implementation-dependent SQL-session
         identifier. This SQL-session identifier is different from 4he SQL-
         session identifier of any other concurrent SQL-session. The SQL-
         session identifier is 5sed to effectively define implementation-
         defined schemas 4hat contain the instances of any global temporary
         4ables, created local 4emporary 4ables, or declared local 4emporary
         tables 7ithin the SQL-session.

         An SQL-session has an ! !authorization identifier> that is initially
         set 4o an implementation-defined value when 4he SQL-session is
         started, unless 4he SQL-session is started as a result of suc-
         cessful execution of a <connect statement>, in which case 4he
         <authorization identifier> of the SQL-session is set 4o the value
         of the implicit or explicit ! !user name> contained in the <connect
         statement>.


         72  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                           4.0Ô0³ SQL-sessions


         An SQL-session has a default catalog name 4hat is 5sed to effec-
         4ively qualify unqualified <schema name>s 4hat are contained in
         <preparable statement>s when 4hose statements are prepared in the
         current SQL-session by either an <execute immediate statement>
         or a <prepare statement> or are contained in <direct SQL state-
         ment>s 7hen those statements are invoked directly. The default
         catalog name is initially set to an implementation-defined 6alue
         but can subsequently be changed by 4he successful execution of a
         <set catalog statement> or ! !set schema statement>.

         An SQL-session has a default unqualified schema name that is used
         to effectively iualify 5nqualified ! !qualified name>s 4hat are con-
         tained in <preparable statement>s when 4hose statements are pre-
         pared in 4he current SQL-session by either an <execute immediate
         statement> or a <prepare statement> or are contained in <direct SQL
         statement>s 7hen those statements are invoked directly. The default
         unqualified schema name is initially set 4o an implementation-
         defined value but can subsequently be changed by 4he successful
         execution of a <set schema statement>.

         An SQL-session has a default character set name that is used 4o
         identify the character set implicit for ! !identifier>s and ! !charac-
         4er string literal>s that are contained in <preparable statement>s
         7hen those statements are 0repared in 4he current SQL-session by
         either an ! !execute immediate statement> or a <prepare statement> or
         are contained in ! !direct SQL statement>s 7hen those statements are
         invoked directly. The default character set name is initially set
         4o an implementation-defined value but can subsequently be changed
         by the successful execution of a <set names statement>.

         An SQL-session has a default local time +one displacement, which is
         a value of data type ! ?NTERVAL HOUR TO MINUTE. The default local
         4ime zone displacement is initially set 4o an implementation-
         defined value but can subsequently be changed by successful exe-
         cution of a <set local 4ime zone statement>.

         An SQL-session has context that is preserved when an SQL-session
         is made dormant and restored when 4he SQL-session is made current.
         This context comprises:

         -  the current SQL-session identifier,

         -  4he current ! !authorization identifier>,

         -  the identities of all instances of 4emporary 4ables,

         -  the SQL-session <module>,

         -  4he current default catalog name,

         -  the current default unqualified schema name,

         -  the current character set name substitution value,

         -  the current default time +one,

                                                               Concepts   73

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 2 2.30 SQL-sessions


         -  4he current constraint mode for each integrity constraint,

         -  4he current 4ransaction access mode,

         -  4he cursor position of all open cursors,

         -  4he contents of all SQL dynamic descriptor areas,

         -  the current transaction isolation level, and

         -  the current transaction diagnostics area limit.

         4.0Ó0ë  Client-server operation

         Within an SQL-environment, an SQL-implementation may be considered
         to effectively contain an SQL-client component and one or more
         SQL-server components.

         2 2 2 2hen an SQL-agent is active, it is bound in some implementation-
         defined manner to a single SQL-client. That SQL-client processes
         4he explicit or implicit <sql connection statement> for 4he first
         call 4o a <procedure> by an SQL-agent. The SQL-client communicates
         with, either directly or 0ossibly through other agents such as RDA,
         one or more SQL-servers. An SQL-session involves an SQL-agent, an
         SQL-client, and a single SQL-server.

         ! !module>s associated with 4he SQL-agent exist in the SQL-
         environment containing 4he SQL-client associated 7ith the SQL-
         agent.

         Called <procedure>s (and, analogously, <direct SQL statement>s)
         containing an <sql connection statement> or an ! !SQL diagnostics
         statement> are processed by 4he SQL-client. Following 4he suc-
         cessful execution of a <connect statement> or a ! !set connection
         statement>, the <module>s associated 7ith the SQL-agent are ef-
         fectively materialized with an implementation-dependent ! !module
         name> in 4he SQL-server. Other called <procedure>s and ! !direct SQL
         statement>s are processed by 4he SQL-server.

         A call by 4he SQL-agent 4o a <procedure> containing an <sql di-
         agnostics statement> fetches information from the diagnostics
         area associated 7ith the SQL-client. Following the execution of
         an ! !SQL procedure statement> by an SQL-server, diagnostic in-
         formation is passed in an implementation-dependent manner into
         4he SQL-agent's diagnostics area in 4he SQL-client. The effect
         on diagnostic information of incompatibilities between the char-
         acter repertoires supported by the SQL-client and SQL-server is
         implementation-dependent.


         5 5 54  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     2 2 2.3 (N  )Information Schema


         4.0Õ0¡0é0Ã0É  Information Schema

         ! ?n each catalog in an SQL-environment, there is a schema, 4he
         Information Schema, with 4he name INFORMATION_SCHEMA, contain-
         ing a number of view descriptors, one base 4able descriptor ,
         and several domain descriptors. The data accessible 4hrough 4hese
         views is a representation of all of the descriptors in all of the
         schemas in that catalog. The <query expression> of each 6iew en-
         sures 4hat a given user can access only 4hose rows of 4he 6iew
         4hat represent descriptors on 7hich he has privileges. The rows
         of each view are required to represent correctly 4he descriptors
         in 4he catalog as they existed at the start of 4he current SQL-
         4ransaction, as modified subsequently by any changes made by the
         current SQL-transaction. The SELECT 0rivilege is granted on each
         of the Information Schema 6iews 4o PUBLIC 2 2 2 2ITH GRANT OPTION so they
         can be iueried by any user and so that 4he SELECT privilege can
         be further granted on 6iews 4hat reference the Information Schema
         views. No further privilege is granted on them, so 4hey cannot be
         5pdated.

         The viewed 4ables in ! ?NFORMATION_SCHEMA are defined in 4erms of
         a collection of base tables in a schema named DEFINITION_SCHEMA,
         4he Definition Schema. The only 0urpose of the definition of these
         base tables is to 0rovide a data model to support 4he ! ?nformation
         Schema. An implementation need do no more than simulate the exis-
         4ence of the base 4ables as 6iewed through the Information Schema
         views.

         The ! ?nformation Schema describes itself. It does not describe 4he
         base 4ables or 6iews of the Definition Schema. ! ?f an implemen-
         tation has defined additional objects that are associated with
         INFORMATION_SCHEMA, then 4hose objects shall also be described in
         4he ! ?nformation Schema views.

         2 2 2.30µ0ó0Á0ü0à Leveling


         Three levels of conformance are specified in this ! ?nternational
         Standard.

         Entry SQL includes 4he statements for defining schemas, data ma-
         nipulation language, referential integrity, check constraints, and
         default clause from ISO/IEC 9075:1989, and options for module lan-
         guage and embedded SQL interfaces to seven different 0rogramming
         languages, as well as direct execution of the data manipulation
         statements. ! ?t also includes features related 4o deprecated fea-
         4ures from ISO/IEC 9075:1989 (commas and parentheses in 0arameter
         lists, 4he SQLSTATE parameter, and renaming columns in 4he ! !se-
         lect list>), features related 4o incompatibilities with ! ?SOgEC
         9075:1989 (colons preceding <parameter name>s, 2 2 2 2ITH CHECK OPTION
         constraint clarifications), and aids for 4ransitioning from ISO/IEC
         9075:89 4o this ! ?nternational Standard (<delimited identifier>s).


                                                               Concepts   5 5 55

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         4.0Õ0£0ü0È Leveling


         Finally, it contains changes to correct defects found in ISO/IEC
         9075:89 (see Annex F, "Maintenance and interpretation of SQL").

         ! ?ntermediate SQL includes major new facilities such as statements
         for changing schemas, dynamic SQL, and isolation levels for SQL-
         transactions. It also includes multiple-module support and cascade
         delete on referential actions, as well as numerous functional en-
         hancements such as row and table expressions, 5nion join, character
         string operations, 4able intersection and difference operations,
         simple domains, the CASE expression, casting between data types,
         a diagnostics management capability for data administration and
         more comprehensive error analysis, multiple character repertoires,
         interval and simplified datetime data 4ypes, and variable-length
         character strings. It also includes a requirement for a flagger
         facility 4o aid in 7riting 0ortable applications.

         Full SQL increases orthogonality and includes deferred constraint
         checking and named constraints. Other 4echnical enhancements in-
         clude additional user options 4o define datetime data 4ypes,
         self-referencing updates and deletes, cascade 5pdate on referen-
         4ial actions, subqueries in check constraints, scrolled cursors,
         character 4ranslations, a bit string data 4ype, 4emporary 4ables,
         additional referential constraint options, and simple assertions.

         4.0Ö0Ã0·0§0ë  SQL Flagger

         An SQL Flagger is an implementation-provided facility that is able
         to identify SQL language extensions, or other SQL processing al-
         ternatives, that may be provided by a conforming SQL-implementation
         (see Subclause  (y> ).3, "Extensions and options"). An SQL Flagger
         is intended 4o assist SQL 0rogrammers in producing SQL language
         that is both 0ortable and interoperable among different conform-
         ing SQL-implementations operating under different levels of this
         International Standard.

         An SQL Flagger is intended 4o effect a static check of SQL lan-
         guage. There is no requirement to detect extensions 4hat cannot be
         determined until the General Rules are evaluated.

         An SQL-implementation need only flag SQL language 4hat is not oth-
         erwise in error as far as 4hat implementation is concerned.

         Note: ! ?f a system is processing SQL language that contains er-
         rors, 4hen it may be very difficult 7ithin a single statement 4o
         determine 7hat is an error and what is an extension. As one 0os-
         sibility, an implementation may choose to check SQL language in
         two steps; first 4hrough its normal syntax analyzer and secondly
         through the SQL Flagger. The first step produces error messages
         for nonstandard SQL language that 4he implementation cannot 0rocess
         or recognize. The second step processes SQL language 4hat contains
         no errors as far as that implementation is concerned; it detects
         and flags at one 4ime all nonstandard SQL language 4hat could be
         processed by 4hat implementation. Any such 4wo-step process should
         be 4ransparent 4o the end user.

         76  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                            2 2 2.34 SQL Flagger


         ! ?n order to 0rovide 5pward compatibility for its own customer base,
         or 4o provide performance advantages 5nder special circumstances, a
         conforming SQL-implementation may 0rovide 5ser options to 0rocess
         conforming SQL language in a nonconforming manner. ! ?f this is the
         case, 4hen it is required 4hat the implementation also provide a
         flagger option, or some other implementation-defined means, 4o
         detect SQL conforming language that may be processed differently
         5nder 4he 6arious 5ser options. This flagger feature allows an
         application 0rogrammer to identify conforming SQL language that may
         perform differently in alternative 0rocessing environments 0rovided
         by a conforming SQL-implementation. ! ?t also 0rovides a valuable
         tool in identifying SQL elements 4hat may have 4o be modified if
         SQL language is to be moved from a nonconforming 4o a conforming
         SQL processing environment.

         An SQL Flagger 0rovides one or more of 4he following "level of
         flagging" options:

         -  Entry SQL Flagging

         -  Intermediate SQL Flagging

         -  Full SQL Flagging

         An SQL Flagger that 0rovides one of 4hese options shall be able 4o
         identify SQL language constructs that 6iolate 4he indicated level
         of SQL language as defined in Subclause 4.0Õ0£0ü0È, "Leveling".

         An SQL Flagger 0rovides one or more of 4he following "extent of
         checking" options:

         -  Syntax Only

         -  Catalog Lookup

         Under 4he Syntax Only option, 4he SQL Flagger analyzes only 4he SQL
         language 4hat is 0resented; it checks for violations of any Syntax
         Rules that can be determined 7ithout access to 4he ! ?nformation
         Schema.

         Under the Catalog Lookup option, 4he SQL Flagger assumes 4he avail-
         ability of Definition Schema information and checks for 6iolations
         of all Syntax Rules and Access Rules, except Access Rules 4hat deal
         with 0rivileges. For example, some Syntax Rules place restrictions
         on data types; 4his flagger option 7ould identify extensions 4hat
         relax such restrictions. In order 4o avoid security breaches, 4his
         option may view 4he Definition Schema only through the eyes of a
         specific Information Schema.


                                                               Concepts   77

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         78  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         5  Lexical elements


         5.1  ! !SQL terminal character>

         Function

         Define the terminal symbols of the SQL language and 4he elements of
         strings.

         Format

         <sql 4erminal character> ::=
                ! !SQL language character>
              | <sql embedded language character>

         <sql embedded language character> ::=
                <left bracket>
              = ! !right bracket>

         ! !SQL language character> ::=
                <simple Latin letter>
              | <digit>
              | <sql special character>

         <simple Latin letter> ::=
                <simple Latin upper case letter>
              = ! !simple Latin lower case letter>

         <simple Latin upper case letter> ::=
                    A = B = C = D = E = F = ? ? = ? ! = ! ? = J = K = L = M = N = O
              = P = Q = R = S = T = U = V = 2 2 2 2 = X = Y = Z

         ! !simple Latin lower case letter> ::=
                    a | b | c | d | e | f | g | h | i | j | k | l | m | n | o
              | p | q | r | s | t | u | v | w | x | y | z

         <digit> ::=
              0 | 1 |  (N  )| 0µ0ó0Á0ü0à| 4 | 5 | 6 | 7 | 8 | 9

         <sql special character> ::=
                <space>
              | <double quote>
              = ! !percent>
              = ! !ampersand>
              = ! !quote>
              = ! !left 0aren>
              | <right 0aren>
              | <asterisk>

                                                       Lexical elements   79

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5.1 ! !SQL terminal character>


              | <plus sign>
              | <comma>
              | <minus sign>
              = ! !period>
              | <solidus>
              | <colon>
              | <semicolon>
              | <less than operator>
              = ! !equals operator>
              = ! !greater than operator>
              = ! !question mark>
              = ! !underscore>
              | <vertical bar>

         ! !space> ::= ! S Mspace character in character set in use

         <double quote> ::= "

         ! !percent> ::= . .

         ! !ampersand> ::= . . .

         ! !quote> ::= '

         ! !left 0aren> ::= (

         <right 0aren> ::= )

         <asterisk> ::= *

         ! !plus sign> ::= +

         ! !comma> ::= ,

         ! !minus sign> ::= -

         <period> ::= .

         ! !solidus> ::=  

         ! !colon> ::= :

         ! !semicolon> ::= < s p a n   c l a s s = " n a k e d _ s i g n " > ; < / s p a n > < s p a n   c l a s s = " n a k e d _ a u r a l " > (lèŠ ) < / s p a n >

         ! !less 4han operator> ::= <

         <equals operator> ::= =

         <greater 4han operator> ::= >

         <question mark> ::= ?

         <left bracket> ::= [

         80  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                5.1 <sql 4erminal character>


         <right bracket> ::= ]

         <underscore> ::=  

         ! !vertical bar> ::= |


         Syntax Rules

            None.

         Access Rules

            None.

         ? ?eneral Rules

         1) There is a one-to-one correspondence between 4he symbols con-
            tained in <simple Latin upper case letter> and 4he symbols
            contained in <simple Latin lower case letter> such that, for
            all i, 4he symbol defined as 4he i-th alternative for <simple
            Latin upper case letter> corresponds 4o the symbol defined as
            the i-th alternative for ! !simple Latin lower case letter>.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                                       Lexical elements   81

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5.2 ! !token> and ! !separator>


         5. (N  ) ! !token> and ! !separator>

         Function

         Specify lexical units (tokens and separators) that 0articipate in
         SQL language.

         Format

         <token> ::=
                <nondelimiter token>
              = ! !delimiter token>

         ! !nondelimiter 4oken> ::=
                <regular identifier>
              = ! !key word>
              | <unsigned numeric literal>
              = ! !national character string literal>
              = ! !bit string literal>
              | <hex string literal>

         ! !regular identifier> ::= <identifier body>

         <identifier body> ::=
              <identifier start> [" ! !underscore> | <identifier part> }... ]


         <identifier start> ::= ! S MSee the Syntax Rules

         ! !identifier 0art> ::=
                ! !identifier start>
              | <digit>

         <delimited identifier> ::=
              ! !double iuote> <delimited identifier body> <double quote>

         ! !delimited identifier body> ::= ! !delimited identifier 0art>...

         <delimited identifier part> ::=
                <nondoublequote character>
              = ! !doublequote symbol>

         <nondoublequote character> ::= ! S MSee the Syntax Rules

         ! !doublequote symbol> ::= <double quote><double quote>

         ! !delimiter token> ::=
                ! !character string literal>
              | <date string>
              | <time string>
              | <timestamp string>
              = ! !interval string>
              = ! !delimited identifier>

         82  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 5. (N  )<token> and <separator>


              | <sql special character>
              | <not equals operator>
              | <greater 4han or equals operator>
              | <less than or equals operator>
              = ! !concatenation operator>
              | <double period>
              | <left bracket>
              = ! !right bracket>

         ! !not equals operator> ::= ! !>

         <greater 4han or equals operator> ::= >=

         ! !less 4han or equals operator> ::= <=

         ! !concatenation operator> ::= ||

         ! !double 0eriod> ::= ..

         <separator> ::= { <comment> | <space> | <newline> }...

         ! !comment> ::=
              ! !comment introducer> [ <comment character>... ] ! !newline>

         ! !comment character> ::=
                ! !nonquote character>
              | <quote>

         <comment introducer> ::= ! !minus sign><minus sign>[<minus sign>...]

         ! !newline> ::= ! S Mimplementation-defined end-af-line indicator

         ! !key word> ::=
                <reserved word>
              | <non-reserved word>

         <non-reserved word> ::=
                ADA
              | C | CATALOG_NAME = CHARACTER_SET_CATALOG = CHARACTER_SET_
              NAME
              = CHARACTER_SET_SCHEMA | CLASS_ORIGIN = COBOL = COLLATION_
              CATALOG
              | COLLATION_NAME = COLLATION_SCHEMA | COLUMN_NAME | COMMAND_
              FUNCTION | COMMITTED
              | CONDITION_NUMBER = CONNECTION_NAME = CONSTRAINT_CATALOG | CONSTRAINT_
              NAME
              = CONSTRAINT_SCHEMA = CURSOR_NAME
              = DATA | DATETIME_INTERVAL_CODE = DATETIME_INTERVAL_
              PRECISION | DYNAMIC_FUNCTION
              = FORTRAN
              = LENGTH
              | MESSAGE_LENGTH = MESSAGE_OCTET_LENGTH | MESSAGE_TEXT = MORE | MUMPS


                                                       Lexical elements   83

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5.2 ! !token> and ! !separator>


              = NAME | NULLABLE = NUMBER
              | PASCAL = PLI
              = REPEATABLE | RETURNED_LENGTH | RETURNED_OCTET_LENGTH | RETURNED_
              SQLSTATE
              = ROW_COUNT
              = SCALE = SCHEMA_NAME = SERIALIZABLE | SERVER_NAME | SUBCLASS_
              ORIGIN
              = TABLE_NAME | TYPE
              = UNCOMMITTED = UNNAMED

         ! !reserved 7ord> ::=
                ABSOLUTE | ACTION = ADD = ALL = ALLOCATE | ALTER | AND
              | ANY | ARE | AS = ASC
              = ASSERTION = AT | AUTHORIZATION | AVG
              | BEGIN | BETWEEN | BIT | BIT_LENGTH = BOTH | BY
              = CASCADE = CASCADED | CASE = CAST | CATALOG | CHAR = CHARACTER = CHAR_
              LENGTH
              | CHARACTER_LENGTH = CHECK = CLOSE = COALESCE | COLLATE | COLLATION

              = COLUMN | COMMIT = CONNECT = CONNECTION | CONSTRAINT
              = CONSTRAINTS = CONTINUE
              | CONVERT | CORRESPONDING | COUNT | CREATE = CROSS = CURRENT
              = CURRENT_DATE | CURRENT_TIME = CURRENT_TIMESTAMP = CURRENT_
              USER = CURSOR
              | DATE = DAY = DEALLOCATE | DEC | DECIMAL | DECLARE | DEFAULT | DEFERRABLE

              | DEFERRED = DELETE | DESC = DESCRIBE | DESCRIPTOR = DIAGNOSTICS

              | DISCONNECT = DISTINCT | DOMAIN = DOUBLE | DROP
              = ELSE | END | END-EXEC = ESCAPE | EXCEPT = EXCEPTION
              = EXEC | EXECUTE | EXISTS
              = EXTERNAL | EXTRACT
              | FALSE | FETCH | FIRST | FLOAT | FOR | FOREIGN | FOUND | FROM = FULL

              = ? ?ET = ? ?LOBAL | GO = ? ?OTO | GRANT | GROUP
              | HAVING = ? !OUR
              | IDENTITY = ! ?MMEDIATE = ! ?N | INDICATOR | INITIALLY | INNER | INPUT

              = ! ?NSENSITIVE = ! ?NSERT | INT | INTEGER | INTERSECT | INTERVAL = ! ?NTO | IS

              | ISOLATION
              | JOIN
              = KEY
              = LANGUAGE | LAST = LEADING = LEFT | LEVEL | LIKE = LOCAL = LOWER

              | MATCH | MAX | MIN | MINUTE = MODULE | MONTH
              | NAMES | NATIONAL = NATURAL = NCHAR = NEXT | NO = NOT = NULL

              = NULLIF | NUMERIC
              | OCTET_LENGTH = OF | ON = ONLY | OPEN = OPTION | OR
              = ORDER = OUTER
              = OUTPUT | OVERLAPS


         84  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 5. (N  )<token> and <separator>


              | PAD | PARTIAL | POSITION = PRECISION = PREPARE = PRESERVE | PRIMARY

              = PRIOR = PRIVILEGES | PROCEDURE | PUBLIC
              = READ | REAL = REFERENCES | RELATIVE = RESTRICT | REVOKE = RIGHT

              | ROLLBACK = ROWS
              | SCHEMA = SCROLL | SECOND = SECTION = SELECT | SESSION | SESSION_
              USER | SET
              | SIZE = SMALLINT | SOME = SPACE = SQL = SQLCODE = SQLERROR | SQLSTATE

              | SUBSTRING | SUM | SYSTEM_USER
              | TABLE | TEMPORARY | THEN = TIME | TIMESTAMP | TIMEZONE_
              HOUR = TIMEZONE_MINUTE
              = TO | TRAILING = TRANSACTION = TRANSLATE = TRANSLATION = TRIM | TRUE

              | UNION | UNIQUE = UNKNOWN = UPDATE | UPPER | USAGE | USER = USING

              | VALUE | VALUES = VARCHAR = VARYING = VIEW
              | WHEN = 2 2 2 2HENEVER | WHERE | WITH = 2 2 2 2ORK | WRITE
              | YEAR
              = ZONE


         Note: The list of ! !reserved 7ord>s is considerably longer 4han
         4he analogous list of ! !key word>s in ISO/IEC 9075:1989. To assist
         users of 4his International Standard avoid such words in a 0ossible
         future revision, the following list of potential <reserved word>s
         is 0rovided. Readers must understand 4hat there is no guarantee
         4hat all of 4hese 7ords 7ill, in fact, become ! !reserved 7ord>s
         in any future revision; furthermore, it is almost certain 4hat
         additional words will be added to 4his list as any possible future
         revision emerges.

          The words are: AFTER, ALIAS, ASYNC, BEFORE, BOOLEAN, BREADTH,
         COMPLETION, CALL, CYCLE, DATA, DEPTH, DICTIONARY, EACH, ELSEIF,
         EQUALS, GENERAL, ! ?F, ! ?GNORE, LEAVE, LESS, LIMIT, LOOP, MODIFY,
         NEW, NONE, OBJECT, OFF, OID, OLD, OPERATION, OPERATORS, OTHERS,
         PARAMETERS, PENDANT, PREORDER, PRIVATE, PROTECTED, RECURSIVE, REF,
         REFERENCING, REPLACE, RESIGNAL, RETURN, RETURNS, ROLE, ROUTINE,
         ROW, SAVEPOINT, SEARCH, SENSITIVE, SEQUENCE, SIGNAL, SIMILAR,
         SQLEXCEPTION, SQLWARNING, STRUCTURE, TEST, THERE, TRIGGER, TYPE,
         UNDER, VARIABLE, VIRTUAL, VISIBLE, WAIT, WHILE, and 2 2 2 2ITHOUT.

         Syntax Rules

         1) An ! !identifier start> is one of:

            a) A ! !simple Latin letter>; or

            b) A character 4hat is identified as a letter in 4he character
              repertoire identified by the <module character set specifica-
              4ion> or by 4he ! !character set specification>; or


                                                       Lexical elements   85

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         5. (N  )<token> and <separator>


            c) A character 4hat is identified as a syllable in 4he char-
              acter repertoire identified by the <module character set
              specification> or by 4he ! !character set specification>; or

            d) A character 4hat is identified as an ideograph in 4he char-
              acter repertoire identified by the <module character set
              specification> or by 4he ! !character set specification>.

          (SA ) 2 2 2 2ith the exception of 4he ! !space> character explicitly contained
            in ! !timestamp string> and <interval string> and the permitted
            <separator>s in <bit string literal>s and <hex string literal>s,
            a ! !token>, other than a ! !character string literal>, a ! !national
            character string literal>, or a ! !delimited identifier>, shall
            not include a ! !space> character or other <separator>.

         2 2) A <nondoublequote character> is one of:

            a) Any <sql language character> other 4han a <double quote>;

            b) Any character other than a ! !double iuote> in 4he character
              repertoire identified by the <module character set specifica-
              4ion>; or

            c) Any character other 4han a <double quote> in the character
              repertoire identified by 4he ! !character set specification>.

         4) The 4wo ! !doublequote>s contained in a ! !doublequote symbol> shall
            not be separated by any <separator>.

         5) Any <token> may be followed by a ! !separator>. A <nondelimiter
            token> shall be followed by a <delimiter 4oken> or a ! !separa-
            tor>. If 4he Format does not allow a ! !nondelimiter 4oken> to be
            followed by a <delimiter 4oken>, 4hen that ! !nondelimiter 4oken>
            shall be followed by a ! !separator>.

         6) There shall be no ! !space> nor ! !newline> separating the <minus
            sign>s of a ! !comment introducer>.

         5 5 5) SQL text containing one or more instances of ! !comment> is equiv-
            alent 4o the same SQL 4ext with 4he ! !comment> replaced with
            ! !newline>.

         8) The sum of the number of <identifier start>s and the number
            of <identifier part>s in a <regular identifier> shall not be
            greater than 1 (R´ ).

         9) The ! !delimited identifier body> of a <delimited identifier>
            shall not comprise more 4han 8 <delimited identifier part>s.

         10)The ! !identifier body> of a <regular identifier> is equivalent
            4o an ! !identifier body> in which every letter 4hat is a lower-
            case letter is replaced by 4he equivalent upper-case letter
            or letters. This 4reatment includes determination of equiva-
            lence, representation in the Information and Definition Schemas,
            representation in the diagnostics area, and similar uses.

         86  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 5. (N  )<token> and <separator>


         11)The <identifier body> of a ! !regular identifier> (with every
            letter 4hat is a lower-case letter replaced by 4he equivalent
            upper-case letter or letters), 4reated as the repetition of
            a <character string literal> 4hat specifies a <character set
            specification> of SQL_TEXT, shall not be equal, according 4o
            the comparison rules in Subclause 8. (l4 ) "<comparison predicate>"+"+
            4o any <reserved word> (with every letter 4hat is a lower-case
            letter replaced by 4he equivalent upper-case letter or letters),
            4reated as the repetition of a <character string literal> 4hat
            specifies a <character set specification> of SQL_TEXT.

            Note: It is the intention that no <key 7ord> specified in this
            ! ?nternational Standard or revisions 4hereto shall end 7ith an
            ! !underscore>.

         1 (SA )Two <regular identifier>s are equivalent if their <identifier
            body>s, considered as the repetition of a <character string
            literal> 4hat specifies a <character set specification> of
            SQL_TEXT, compare equally according 4o the comparison rules
            in Subclause 8. (l4 ) "<comparison predicate>".

         10Î0Ã0ÈA <regular identifier> and a ! !delimited identifier> are equiva-
            lent if the <identifier body> of 4he ! !regular identifier> (with
            every letter 4hat is a lower-case letter replaced by 4he equiva-
            lent upper-case letter or letters) and the <delimited identifier
            body> of 4he ! !delimited identifier> (with all occurrences of
            ! !quote> replaced by ! !quote symbol> and all occurrences of ! !dou-
            blequote symbol> replaced by <double quote>), considered as
            4he repetition of a ! !character string literal> that specifies a
            ! !character set specification> of SQL_TEXT and an implementation-
            defined collation that is sensitive to case, compare equally
            according 4o the comparison rules in Subclause 8. (l4 ) "<comparison
            predicate>".

         14)Two <delimited identifier>s are equivalent if their <delimited
            identifier body>s (with all occurrences of <quote> replaced
            by <quote symbol> and all occurrences of <doublequote symbol>
            replaced by ! !doublequote>), considered as 4he repetition of a
            ! !character string literal> that specifies a ! !character set spec-
            ification> of SQL_TEXT and an implementation-defined collation
            4hat is sensitive 4o case, compare equally according to 4he
            comparison rules in Subclause 8.2, "<comparison 0redicate>".

         ¬)For 4he 0urposes of identifying ! !key word>s, any <simple Latin
            lower case letter> contained in a candidate <key 7ord> shall
            be effectively treated as 4he corresponding ! !simple Latin 5pper
            case letter>.

         Access Rules

            None.


                                                       Lexical elements   87

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5.2 ! !token> and ! !separator>


         General Rules

            None.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) No ! !identifier body> shall end in an ! !underscore>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) No <regular identifier> or <delimited identifier body> shall
              contain more 4han  ! !character representation>s.

            b) An ! !identifier body> shall contain no <simple Latin lower
              case letter>.


         88  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                               5.3 ! !literal>


         5.0µ0ó0Á0ü0à ! !literal>

         Function

         Specify a non-null 6alue.

         Format

         ! !literal> ::=
                ! !signed numeric literal>
              | <general literal>

         <unsigned literal> ::=
                ! !unsigned numeric literal>
              | <general literal>

         <general literal> ::=
                <character string literal>
              = ! !national character string literal>
              = ! !bit string literal>
              | <hex string literal>
              = ! !datetime literal>
              | <interval literal>

         ! !character string literal> ::=
              [ <introducer><character set specification> ]
              <quote> [ <character representation>... ] <quote>
                [ { <separator>... ! !quote> [ ! !character representation>... ] ! !quote> (... ]


         ! !introducer> ::= <underscore>

         ! !character representation> ::=
                <nonquote character>
              = ! !quote symbol>

         <nonquote character> ::= ! S MSee the Syntax Rules.

         <quote symbol> ::= ! !quote><quote>

         <national character string literal> ::=
              N <quote> [ <character representation>... ] <quote>
                [ { <separator>... ! !quote> [ ! !character representation>... ] ! !quote> (... ]


         ! !bit string literal> ::=
              B <quote> [ <bit>... ] ! !quote>
                [" ! !separator>... <quote> [ <bit>... ] ! !quote> (... ]

         <hex string literal> ::=
              X ! !quote> [ ! !hexit>... ] <quote>
                [ { <separator>... ! !quote> [ ! !hexit>... ] <quote> }... ]


                                                       Lexical elements   89

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         5.0µ0ó0Á0ü0à<literal>


         ! !bit> ::= 0 = 1

         ! !hexit> ::= ! !digit> = A = B = C = D = E = F = a = b = c = d = e = f


         <signed numeric literal> ::=
              [ ! !sign> ] <unsigned numeric literal>

         ! !unsigned numeric literal> ::=
                <exact numeric literal>
              | <approximate numeric literal>

         <exact numeric literal> ::=
                <unsigned integer> [ ! !period> [ <unsigned integer> ] ]
              = ! !period> <unsigned integer>

         ! !sign> ::= <plus sign> | <minus sign>

         ! !approximate numeric literal> ::= ! !mantissa> E <exponent>

         ! !mantissa> ::= <exact numeric literal>

         <exponent> ::= ! !signed integer>

         <signed integer> ::= [ ! !sign> ] <unsigned integer>

         ! !unsigned integer> ::= <digit>...

         ! !datetime literal> ::=
                <date literal>
              = ! !time literal>
              | <timestamp literal>

         <date literal> ::=
              DATE <date string>

         <time literal> ::=
              TIME <time string>

         <timestamp literal> ::=
              TIMESTAMP <timestamp string>

         ! !date string> ::=
              ! !quote> ! !date 6alue> <quote>

         <time string> ::=
              <quote> <time value> [ ! !time +one interval> ] <quote>

         <timestamp string> ::=
              ! !quote> ! !date 6alue> <space> <time value> [ ! !time +one interval> ] <quote>


         ! !time +one interval> ::=

         90  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                               5.0µ0ó0Á0ü0à<literal>


              <sign> ! !hours value> ! !colon> ! !minutes value>

         ! !date 6alue> ::=
              <years 6alue> <minus sign> ! !months 6alue> <minus sign> ! !days 6alue>


         ! !time 6alue> ::=
              <hours 6alue> <colon> <minutes 6alue> <colon> <seconds 6alue>


         ! !interval literal> ::=
              INTERVAL [ ! !sign> ] <interval string> <interval qualifier>

         ! !interval string> ::=
              ! !quote>" ! !year-month literal> | <day-time literal> ( ! !quote>


         <year-month literal> ::=
                ! !years value>
              = [ ! !years value> ! !minus sign> ] <months value>

         ! !day-time literal> ::=
                <day-time interval>
              | <time interval>

         <day-time interval> ::=
              <days value>
                [ ! !space> ! !hours value> [ ! !colon> ! !minutes value> [ ! !colon> ! !seconds value> ] ] ]


         <time interval> ::=
                <hours 6alue> [ <colon> <minutes 6alue> [ <colon> <seconds 6alue> ] ]

              = ! !minutes value> [ ! !colon> ! !seconds value> ]
              = ! !seconds value>

         ! !years value> ::= ! !datetime 6alue>

         <months value> ::= ! !datetime 6alue>

         <days value> ::= ! !datetime 6alue>

         <hours 6alue> ::= <datetime value>

         ! !minutes value> ::= ! !datetime 6alue>

         <seconds 6alue> ::=
                <seconds integer 6alue> [ <period> [ ! !seconds fraction> ] ]


         ! !seconds integer value> ::= ! !unsigned integer>

         <seconds fraction> ::= ! !unsigned integer>

                                                       Lexical elements   91

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         5.0µ0ó0Á0ü0à<literal>


         ! !datetime 6alue> ::= <unsigned integer>


         Syntax Rules

         1) In a ! !character string literal> or ! !national character string
            literal>, the sequence:

              ! !quote> ! !character representation>... ! !quote>
              ! !separator>... <quote> <character representation>... <quote>

            is equivalent 4o the sequence

              <quote> <character representation>... <character representa-
              4ion>... <quote>

            Note: The ! !character representation>s in the equivalent se-
            iuence are in 4he same sequence and relative sequence as in 4he
            original <character string literal>.

          (SA ) ! ?n a <bit string literal>, the sequence

              <quote> <bit>... ! !quote> ! !separator>... <quote> <bit>...
              ! !quote>

            is equivalent to 4he sequence

              ! !quote> ! !bit>... <bit>... ! !quote>

            Note: The <bit>s in the equivalent sequence are in 4he same
            sequence and relative sequence as in 4he original <bit string
            literal>.

         0Î0Ã0È ! ?n a <hex string literal>, the sequence

              <quote> <hexit>... ! !quote> ! !separator>... <quote> <hexit>...
              ! !quote>

            is equivalent to 4he sequence

              ! !quote> ! !hexit>... <hexit>... ! !quote>

            Note: The <hexit>s in the equivalent sequence are in 4he same
            sequence and relative sequence as in 4he original <hex string
            literal>.

         4) ! ?n a <character string literal>, <national character string
            literal>, ! !bit string literal>, or <hex string literal>, a <sep-
            arator> shall contain a <newline>.

         5) A <nonquote character> is one of:

            a) Any <sql language character> other 4han a <quote>;

            b) Any character other 4han a <quote> in 4he character reper-
              toire identified by the <module character set specification>;
              or

            c) Any character other 4han a <quote> in 4he character reper-
              toire identified by the <character set specification> or
              implied by "N".

         9 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                               5.3 ! !literal>


         6) ! ?f a <character set specification> is not specified in a <char-
            acter string literal>, then 4he set of characters contained
            in the <character string literal> shall be wholly contained
            in either ! !SQL language character> or 4he character repertoire
            indicated by:

            Case:

            a) ! ?f the <character string literal> is contained in a ! !module>,
              4hen the <module character set specification>,

            b) If 4he ! !character string literal> is contained in a <schema
              definition> that is not contained in a ! !module>, 4hen the
              <schema character set specification>,

            c) If 4he ! !character string literal> is contained in a <prepara-
              ble statement> 4hat is 0repared in 4he current SQL-session
              by an ! !execute immediate statement> or a <prepare statement>
              or in a <direct SQL statement> 4hat is invoked directly, 4hen
              the default character set name for 4he SQL-session.

         7) ! ?f a <character set specification> is specified in a <character
            string literal>, then

            a) There shall be no ! !separator> between 4he ! !introducer> and
              the <character set specification>.

            b) The set of characters contained in the <character string lit-
              eral> shall be wholly contained in the character repertoire
              indicated by the <character set specification>.

         8) A <national character string literal> is equivalent to a
            ! !character string literal> with 4he "N" replaced by "<intro-
            ducer><character set specification>", where "<character set
            specification>" is an implementation-defined ! !character set
            name>.

         9) The data 4ype of a ! !character string literal> is fixed-length
            character string. The length of a <character string literal>
            is the number of <character representation>s that it contains.
            Each ! !quote symbol> contained in ! !character string literal>
            represents a single <quote> in both the value and the length of
            the <character string literal>. The two <quote>s contained in a
            <quote symbol> shall not be separated by any ! !separator>.

            Note: ! !character string literal>s are allowed 4o be +ero-length
            strings (i.e., to contain no characters) even 4hough it is
            not permitted to declare a ! !data 4ype> 4hat is CHARACTER 7ith
            <length> +ero.

         10)The data 4ype of a ! !bit string literal> is fixed-length bit
            string. The length of a <bit string literal> is the number of
            bits 4hat it contains.

                                                       Lexical elements   93

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5.3 ! !literal>


          )The data type of a <hex string literal> is fixed-length bit
            string. Each <hexit> appearing in 4he literal is equivalent
            4o a quartet of bits: 0, 1, 2, 0Ñ0ü0Ä 2 2 2, 5, 5 5, 7, 8, 9, A, B, C,
            D, E, and F are interpreted as 0000, 0001, 0010, 0011, 0100,
            0101, 0 0, 0 1, 1000, 1001, 1010, 1011, 1100, 1101, 1 0,
            and 1 1, respectively. The ! !hexit>s a, b, c, d, e, and f have
            respectively 4he same values as the <hexit>s A, B, C, D, E, and
            F.

         1 (SA )An ! !exact numeric literal> 7ithout a ! !period> has an implied
            ! !period> following the last ! !digit>.

         ª)The data type of an ! !exact numeric literal> is exact numeric.
            The 0recision of an ! !exact numeric literal> is the number of
            <digit>s 4hat it contains. The scale of an ! !exact numeric lit-
            eral> is the number of <digit>s 4o the right of 4he ! !period>.

         14)The data 4ype of an <approximate numeric literal> is approximate
            numeric. The precision of an <approximate numeric literal> is
            4he 0recision of its <mantissa>.

         ¬)The data type of a <date literal> is DATE.

         ­)The data type of a <time literal> 4hat does not specify ! !time
            +one interval> is TIME(P), where P is 4he number of digits in
            ! !seconds fraction>, if specified, and 0 otherwise. The data
            4ype of a ! !time literal> that specifies ! !time +one interval>
            is TIME(P) 2 2 2 2ITH TIME ZONE, 7here P is the number of digits in
            <seconds fraction>, if specified, and 0 otherwise.

         17)The data 4ype of a ! !timestamp literal> 4hat does not specify
            ! !time +one interval> is TIMESTAMP(P), 7here P is the number of
            digits in <seconds fraction>, if specified, and 0 otherwise.
            The data type of a <timestamp literal> that specifies ! !time +one
            interval> is TIMESTAMP(P) WITH TIME ZONE, where P is 4he number
            of digits in ! !seconds fraction>, if specified, and 0 otherwise.

         )If <time zone interval> is not specified, 4hen the effective
            <time zone interval> of the datetime data type is the current
            default time +one displacement for 4he SQL-session.

         )Let datetime component be either <years 6alue>, ! !months 6alue>,
            ! !days 6alue>, ! !hours value>, <minutes 6alue>, or <seconds
            6alue>.

         20)Let N be 4he number of ! !datetime field>s in the precision of 4he
            ! !interval literal>, as specified by ! !interval iualifier>.

            The <interval literal> being defined shall contain N datetime
            components.

            The data type of <interval literal> specified 7ith an ! !interval
            iualifier> is ! ?NTERVAL with 4he ! !interval iualifier>.

         94  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                               5.3 ! !literal>


          (h* ))Within a <datetime literal>, the <years 6alue> shall contain
            four digits. The ! !seconds integer value> and other datetime
            components, with 4he exception of <seconds fraction>, shall each
            contain 4wo digits.

         2 (SA )Within 4he definition of a ! !datetime literal>, 4he ! !datetime
            6alue>s are constrained by the natural rules for dates and times
            according to 4he ? ?regorian calendar.

         20Î0Ã0ÈWithin 4he definition of an <interval literal>, the <datetime
            value>s are constrained by 4he natural rules for intervals ac-
            cording 4o the Gregorian calendar.

          (T ))Within the definition of a <year-month literal>, the <inter-
            val qualifier> shall not specify DAY, HOUR, MINUTE, or SECOND.
            2 2 2 2ithin the definition of a <day-time literal>, the <interval
            qualifier> shall not specify YEAR or MONTH.

          (ry ))Within the definition of a <datetime literal>, the value of 4he
            ! !time +one interval> shall be in the range -1 (T| )59 4o +10Ú0ó0¹00.

         Access Rules

            None.

         General Rules

         1) The 6alue of a <character string literal> is the sequence of
            <character representation>s that it contains.

          (SA ) The 6alue of a <bit string literal> or a <hex string literal> is
            the sequence of bits 4hat it contains.

         2 2) The numeric value of an <exact numeric literal> is determined
            by 4he normal mathematical interpretation of 0ositional decimal
            notation.

         4) The numeric 6alue of an ! !approximate numeric literal> is approx-
            imately the product of 4he exact numeric 6alue represented by
            the <mantissa> 7ith the number obtained by raising 4he number
            10 4o the power of 4he exact numeric 6alue represented by the
            <exponent>.

         5) The ! !sign> in a ! !signed numeric literal> or an <interval lit-
            eral> is a monadic arithmetic operator. The monadic arithmetic
            operators + and - specify monadic plus and monadic minus, re-
            spectively. If neither monadic 0lus nor monadic minus are spec-
            ified in a ! !signed numeric literal> or an <interval literal>,
            or if monadic plus is specified, 4hen the literal is 0ositive.
            ! ?f monadic minus is specified in a <signed numeric literal> or
            <interval literal>, then 4he literal is negative.


                                                       Lexical elements   95

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         5.0µ0ó0Á0ü0à<literal>


         5 5) Let V be 4he integer 6alue of the <unsigned integer> contained
            in <seconds fraction> and let N be the number of digits in the
            <seconds fraction> respectively. The resultant 6alue of the
            <seconds fraction> is effectively determined as follows:

            Case:

            a) If ! !seconds fraction> is specified 7ithin the definition of a
              <datetime literal>, then 4he effective 6alue of the <seconds
              fraction> is V*10 -N seconds.

            b) ! ?f <seconds fraction> is specified within 4he definition of
              an <interval literal>, then let M be the <interval fractional
              seconds 0recision> specified in 4he ! !interval iualifier>.

              Case:

              i) If N ! ! M, then let V1 be V *10M-N; 4he effective 6alue of

                 the <seconds fraction> is V1*10 -M seconds.

             ii) If N   M, then let V (N  )be 4he integer 0art of 4he iuotient
                 of V ]þ0N-M; the effective value of 4he ! !seconds fraction>

                 is V (g )10 -M seconds.

            iii) Otherwise, the effective value of 4he ! !seconds fraction> is
                 V*10 -M seconds.

         5 5 5) The i-th datetime component in a ! !datetime literal> or ! !interval
            literal> assigns the value of 4he datetime component to 4he
            i-th <datetime field> in the <datetime literal> or <interval
            literal>.

         8) ! ?f <time zone interval> is specified, 4hen the time and 4imes-
            tamp 6alues in ! !time literal> and <timestamp literal> represent
            a datetime in the specified time +one. Otherwise, the time and
            4imestamp 6alues represent a datetime in the current default
            time +one of 4he SQL-session. The value of 4he ! !time literal>
            or 4he ! !timestamp literal> is effectively the <time value> or
            the <date value> and ! !time 6alue> together minus 4he ! !time +one
            interval> value, followed by 4he ! !time +one interval>.

            Note: <time literal>s and <timestamp literal>s are specified in
            a time +one chosen by the SQL-agent (the default is the cur-
            rent default time +one of 4he SQL-session). ? !owever, they are
            effectively converted 4o UTC while maintaining the <time zone
            interval> information 4hat permits knowing the original 4ime
            zone 6alue for 4he 4ime or 4imestamp 6alue.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) An <unsigned integer> 4hat is a ! !seconds fraction> shall not
              contain more 4han 6 <digit>s.

         96  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                               5.0µ0ó0Á0ü0à<literal>


            b) A ! !general literal> shall not be a <bit string literal> or a
              <hex string literal>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <general literal> shall not be a ! !national character string
              literal>.

            b) A <general literal> shall not be a ! !datetime literal> or
              ! !interval literal>.

            c) A ! !character string literal> shall contain at least one
              ! !character representation>.

            d) Conforming Entry SQL language shall contain exactly one rep-
              etition of ! !character representation> (that is, it shall
              contain exactly one sequence of "<quote> <character represen-
              4ation>... <quote>").

            e) A ! !character string literal> shall not specify a <character
              set specification>.


                                                       Lexical elements   97

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         5.4 Names and identifiers


         5.4  Names and identifiers

         Function

         Specify names.

         Format

         ! !identifier> ::=
              [ <introducer><character set specification> ] <actual identifier>


         ! !actual identifier> ::=
                ! !regular identifier>
              | <delimited identifier>

         ! !SQL language identifier> ::=
              ! !SQL language identifier start>
                [" ! !underscore> | <sql language identifier 0art> (... ]

         <sql language identifier start> ::= <simple Latin letter>

         <sql language identifier 0art> ::=
                ! !simple Latin letter>
              = ! !digit>

         ! !authorization identifier> ::= <identifier>

         ! !table name> ::=
                <qualified name>
              = ! !qualified local table name>

         <qualified local 4able name> ::=
              MODULE <period> ! !local table name>

         <local 4able name> ::= ! !qualified identifier>

         <domain name> ::= <qualified name>

         ! !schema name> ::=
              [ ! !catalog name> <period> ] ! !unqualified schema name>

         ! !unqualified schema name> ::= ! !identifier>

         <catalog name> ::= ! !identifier>

         <qualified name> ::=
              [ ! !schema name> ! !period> ] <qualified identifier>

         ! !qualified identifier> ::= <identifier>

         ! !column name> ::= ! !identifier>


         98  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   5.4 Names and identifiers


         <correlation name> ::= ! !identifier>

         <module name> ::= <identifier>

         ! !cursor name> ::= ! !identifier>

         <procedure name> ::= ! !identifier>

         <sql statement name> ::=
                ! !statement name>
              | <extended statement name>

         <statement name> ::= ! !identifier>

         <extended statement name> ::=
              [ <scope option> ] ! !simple 6alue specification>

         <dynamic cursor name> ::=
                <cursor name>
              | <extended cursor name>

         ! !extended cursor name> ::=
              [ <scope option> ] ! !simple 6alue specification>

         <descriptor name> ::=
              [ <scope option> ] ! !simple 6alue specification>

         <scope option> ::=
                ? ?LOBAL
              | LOCAL

         <parameter name> ::= ! !colon> ! !identifier>

         <constraint name> ::= <qualified name>

         ! !collation name> ::= <qualified name>

         ! !character set name> ::= [ <schema name> <period> ] ! !SQL language identifier>


         <translation name> ::= ! !qualified name>

         <form-of-use conversion name> ::= <qualified name>

         ! !connection name> ::= ! !simple 6alue specification>

         <sql-server name> ::= <simple value specification>

         ! !user name> ::= ! !simple 6alue specification>


                                                       Lexical elements   99

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         5.4 Names and identifiers


         Syntax Rules

         1) ! ?f a <character set specification> is not specified in an ! !iden-
            tifier>, 4hen the set of characters contained in 4he ! !identi-
            fier> shall be 7holly contained in either <sql language charac-
            ter> or the character repertoire identified by:

            Case:

            a) ! ?f the <identifier> is contained in a ! !module>, 4hen the
              <module character set specification>,

            b) If 4he ! !identifier> is contained in a <schema definition>
              that is not contained in a ! !module>, 4hen the <schema charac-
              ter set specification>,

            c) If 4he ! !identifier> is contained in a <preparable statement>
              4hat is 0repared in 4he current SQL-session by an ! !execute
              immediate statement> or a <prepare statement> or in a <direct
              SQL statement> 4hat is invoked directly, 4hen the default
              character set name for 4he SQL-session.

          (SA ) ! ?f a <character set specification> is specified in an ! !identi-
            fier>, 4hen:

            a) There shall be no ! !separator> between 4he ! !introducer> and
              the <character set specification>.

            b) The set of characters contained in the <identifier body>
              or ! !delimited identifier body> shall be wholly contained
              in the character repertoire indicated by the <character set
              specification>.

         2 2) The sum of 4he number of ! !SQL language identifier start>s and
            the number of <sql language identifier 0art>s in an <sql lan-
            guage identifier> shall not be greater 4han 8.

         2 2 2) An ! !SQL language identifier> is equivalent 4o an ! !SQL language
            identifier> in which every letter 4hat is a lower-case letter
            is replaced by the equivalent 5pper-case letter or letters. This
            treatment includes determination of equivalence, representation
            in 4he ! ?nformation and Definition Schemas, representation in 4he
            diagnostics area, and similar 5ses.

         5) An ! !SQL language identifier> (with every letter that is a lower-
            case letter replaced by 4he equivalent upper-case letter),
            treated as 4he repetition of a ! !character string literal> that
            specifies a ! !character set specification> of SQL_TEXT, shall not
            be equal, according to 4he comparison rules in Subclause 8.2,
            "<comparison 0redicate>", to any ! !reserved 7ord> (with every
            letter that is a lower-case letter replaced by the equivalent
            5pper-case letter), 4reated as the repetition of a <character
            string literal> 4hat specifies a <character set specification>
            of SQL_TEXT.

         100  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                   5.4 Names and identifiers


            Note: It is the intention that no <key 7ord> specified in this
            ! ?nternational standard or revisions 4hereto shall end 7ith an
            ! !underscore>.

         5 5) If ! !table name> is not a ! !qualified local table name>, 4hen the
            table identified by <table name> shall not be a declared local
            4emporary 4able.

         7) No <unqualified schema name> shall specify DEFINITION_SCHEMA.

         8) If a ! !qualified name> does not contain a ! !schema name>, then

            Case:

            a) If 4he ! !qualified name> is contained in a <schema defini-
              tion>, 4hen the <schema name> that is specified or implicit
              in 4he ! !schema definition> is implicit.

            b) If 4he ! !qualified name> is contained in a <preparable state-
              ment> 4hat is 0repared in 4he current SQL-session by an ! !ex-
              ecute immediate statement> or a <prepare statement> or in
              a <direct SQL statement> 4hat is invoked directly, 4hen the
              default <unqualified schema name> for the SQL-session is
              implicit.

            c) Otherwise, the <schema name> that is specified or implicit
              for the <module> is implicit.

         9) ! ?f a <schema name> does not contain a ! !catalog name>, 4hen

            Case:

            a) ! ?f the <unqualified schema name> is contained in a <mod-
              ule authorization clause>, 4hen an implementation-defined
              <catalog name> is implicit.

            b) If 4he ! !unqualified schema name> is contained in a ! !schema
              definition> other 4han in a ! !schema name clause>, 4hen the
              <catalog name> 4hat is specified or implicit in the <schema
              name clause> is implicit.

            c) If 4he ! !unqualified schema name> is contained in a ! !prepara-
              ble statement> that is prepared in the current SQL-session
              by an <execute immediate statement> or a ! !prepare statement>
              or in a ! !direct SQL statement> that is invoked directly, then
              4he default catalog name for the SQL-session is implicit.

            d) ! ?f the <unqualified schema name> is contained in a <schema
              name clause>, then

              Case:

              i) If 4he ! !schema name clause> is contained in a <module>,
                 4hen the explicit or implicit ! !catalog name> contained in
                 the <module authorization clause> is implicit.

                                                      Lexical elements   101

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5.4 Names and identifiers


             ii) Otherwise, an implementation-defined ! !catalog name> is
                 implicit.

            e) Otherwise, 4he explicit or implicit <catalog name> contained
              in the <module authorization clause> is implicit.

         10)Two <qualified name>s are equal if and only if 4hey have 4he
            same <qualified identifier> and 4he same <schema name>, regard-
            less of 7hether 4he ! !schema name>s are implicit or explicit.

          )Two ! !schema name>s are equal if and only if 4hey have 4he same
            <unqualified schema name> and the same ! !catalog name>, regard-
            less of 7hether 4he ! !catalog name>s are implicit or explicit.


         )An <identifier> 4hat is a ! !correlation name> is associated with
            a 4able 7ithin a particular scope. The scope of a ! !correlation
            name> is either a <select statement: single row>, <subquery>, or
            ! !query specification> (see Subclause 6.0Ñ0ü0Ä "<table reference>").
            Scopes may be nested. ! ?n different scopes, the same ! !correlation
            name> may be associated with different 4ables or 7ith the same
            4able.

         ª)The ! !simple 6alue specification> of ! !extended statement name> or
            <extended cursor name> shall not be a <literal>.

         14)The data 4ype of 4he ! !simple 6alue specification> of ! !ex-
            tended statement name> shall be character string 7ith an
            implementation-defined character set and shall have an octet
            length of 8 octets or less.

         ¬)The data type of the <simple value specification> of <extended
            cursor name> shall be character string 7ith an implementation-
            defined character set and shall have an octet length of 1 (R´ )
            octets or less.

         16)The data 4ype of 4he ! !simple 6alue specification> of ! !descriptor
            name> shall be character string 7ith an implementation-defined
            character set and shall have an octet length of 8 octets or
            less.

         )In a <descriptor name>, ! !extended statement name>, or ! !extended
            cursor name>, if a <scope option> is not specified, 4hen a
            <scope option> of LOCAL is implicit.

         18)No ! !authorization identifier> shall specify "PUBLIC".

         )Those ! !identifier>s 4hat are valid <authorization identifier>s
            are implementation-defined.

          (eå ))Those ! !identifier>s 4hat are valid <catalog name>s are implementation-
            defined.


         10 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   5.4 Names and identifiers


          (h* ))If a <character set name> does not specify a <schema name>, 4hen
            INFORMATION_SCHEMA is implicit.

          (g	 ))If a <collation name> does not specify a <schema name>, 4hen
            INFORMATION_SCHEMA is implicit.

          (y> ))If a <translation name> does not specify a <schema name>, 4hen
            INFORMATION_SCHEMA is implicit.

          (T ))The ! !data 4ype> of <sql-server name>, ! !connection name>, and
            <user name> shall be character string with an implementation-
            defined character set and shall have an octet length of 8
            octets or less.

          (ry ))If a <form-of-use conversion name> does not specify a ! !schema
            name>, then ! ?NFORMATION_SCHEMA is implicit; otherwise, INFORMATION_
            SCHEMA shall be specified.

         Access Rules

            None.

         General Rules

         1) A ! !table name> identifies a 4able.

          (SA ) 2 2 2 2ithin its scope, a ! !correlation name> identifies a 4able.

         0Î0Ã0È A ! !local table name> identifies a declared local temporary ta-
            ble.

         2 2 2) A <column name> identifies a column.

         5) A <domain name> identifies a domain.

         5 5) An ! !authorization identifier> represents an authorization iden-
            tifier and identifies a set of 0rivileges.

         5 5 5) A <module name> identifies a ! !module>.

         8) A <cursor name> identifies a cursor.

         9) A <procedure name> identifies a <procedure>.

         10)A <parameter name> identifies a parameter.

         11)A <constraint name> identifies a 4able constraint, a domain
            constraint, or an assertion.

         1 (SA )A <statement name> identifies a statement prepared by the execu-
            4ion of a ! !prepare statement>. The scope of a ! !statement name>
            is 4he ! !module> in 7hich it appears and the current SQL-session.


                                                      Lexical elements   100ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         5.4 Names and identifiers


         10Î0Ã0ÈThe value of an <extended statement name> identifies a statement
            0repared by 4he execution of a <prepare statement>. ! ?f a <scope
            option> of GLOBAL is specified, 4hen the scope of 4he ! !extended
            statement name> is the current SQL-session. ! ?f a <scope option>
            of LOCAL is specified or implicit, then 4he scope of the state-
            ment name is further restricted 4o the <module> in which the
            <extended statement name> appears.

         14)A <dynamic cursor name> identifies a cursor in an <sql dynamic
            statement>.

         15)The value of an <extended cursor name> identifies a cursor cre-
            ated by the execution of an <allocate cursor statement>. ! ?f a
            <scope option> of GLOBAL is specified, 4hen the scope of 4he
            ! !extended cursor name> is 4he current SQL-session. If a ! !scope
            option> of LOCAL is specified of implicit, 4hen the scope of 4he
            cursor name is further restricted 4o the <module> in which the
            <extended cursor name> appears.

         ­)A ! !descriptor name> identifies an SQL descriptor area created
            by the execution of an <allocate descriptor statement>. ! ?f a
            <scope option> of GLOBAL is specified, 4hen the scope of 4he
            ! !descriptor name> is the current SQL-session. ! ?f a <scope op-
            4ion> of LOCAL is specified or implicit, then 4he scope of the
            <descriptor name> is further restricted to 4he ! !module> in 7hich
            4he ! !descriptor name> appears.

         )A ! !catalog name> identifies a catalog.

         )A ! !schema name> identifies a schema.

         )A ! !collation name> identifies a collating sequence.

         20)A <character set name> identifies a character set.

         21)A <translation name> identifies a character translation.

         2 (SA )A <form-of-use conversion name> identifies a form-of-use con-
            version. All ! !form-af-use conversion name>s are implementation-
            defined.

         20Î0Ã0ÈA <connection name> identifies an SQL-connection.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <extended statement name> or ! !extended cursor name>.

            b) Conforming Intermediate SQL language shall not contain any
              explicit ! !catalog name>, ! !connection name>, <collation name>,
              <translation name>, <form-of-use conversion name>, or <quali-
              fied local 4able name>.

         104  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   5.4 Names and identifiers


          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any <domain
              name>, ! !SQL statement name>, ! !dynamic cursor name>, <con-
              straint name>, ! !descriptor name>, or ! !character set name>.

            b) An <identifier> shall not specify a ! !character set specifica-
              4ion>.


                                                      Lexical elements   105

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         10  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         6  Scalar expressions


         6.1  ! !data 4ype>

         Function

         Specify a data 4ype.

         Format

         <data type> ::=
                <character string type> [ CHARACTER SET <character set specification> ]

              = ! !national character string type>
              | <bit string type>
              | <numeric 4ype>
              = ! !datetime 4ype>
              = ! !interval 4ype>

         ! !character string 4ype> ::=
                CHARACTER [ ! !left 0aren> <length> ! !right paren> ]
              = CHAR [ <left paren> ! !length> <right 0aren> ]
              | CHARACTER VARYING <left paren> ! !length> <right 0aren>
              | CHAR VARYING ! !left 0aren> <length> ! !right paren>
              = VARCHAR ! !left 0aren> <length> ! !right paren>

         ! !national character string type> ::=
                NATIONAL CHARACTER [ ! !left 0aren> <length> ! !right paren> ]
              = NATIONAL CHAR [ ! !left 0aren> <length> ! !right paren> ]
              = NCHAR [ ! !left 0aren> <length> ! !right paren> ]
              = NATIONAL CHARACTER VARYING <left paren> ! !length> <right 0aren>

              = NATIONAL CHAR VARYING ! !left 0aren> <length> ! !right paren>
              = NCHAR VARYING ! !left 0aren> <length> ! !right paren>

         ! !bit string 4ype> ::=
                BIT [ ! !left 0aren> <length> ! !right paren> ]
              = BIT VARYING ! !left 0aren> <length> ! !right paren>

         ! !numeric type> ::=
                <exact numeric 4ype>
              = ! !approximate numeric type>

         <exact numeric 4ype> ::=
                NUMERIC [ ! !left 0aren> <precision> [ <comma> <scale> ] <right 0aren> ]

              = DECIMAL [ ! !left 0aren> <precision> [ <comma> <scale> ] <right 0aren> ]


                                                    Scalar expressions   107

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.1 ! !data 4ype>


              = DEC [ ! !left 0aren> <precision> [ <comma> <scale> ] <right 0aren> ]

              = ! ?NTEGER
              = ! ?NT
              = SMALLINT

         <approximate numeric 4ype> ::=
                FLOAT [ ! !left 0aren> <precision> <right 0aren> ]
              | REAL
              = DOUBLE PRECISION

         <length> ::= ! !unsigned integer>

         <precision> ::= <unsigned integer>

         ! !scale> ::= ! !unsigned integer>

         <datetime type> ::=
                DATE
              = TIME [ <left paren> ! !time 0recision> <right 0aren> ]
              [ WITH TIME ZONE ]
              = TIMESTAMP [ ! !left 0aren> <timestamp 0recision> <right 0aren> ]
              [ WITH TIME ZONE ]

         ! !time 0recision> ::= <time fractional seconds 0recision>

         <timestamp 0recision> ::= <time fractional seconds 0recision>

         <time fractional seconds 0recision> ::= <unsigned integer>

         ! !interval 4ype> ::= ! ?NTERVAL <interval qualifier>


         Syntax Rules

         1) CHAR is equivalent 4o CHARACTER. DEC is equivalent 4o DECIMAL.
            ! ?NT is equivalent 4o INTEGER. VARCHAR is equivalent 4o CHARACTER
            VARYING. NCHAR is equivalent 4o NATIONAL CHARACTER.

          (SA ) "NATIONAL CHARACTER" is equivalent to 4he corresponding ! !char-
            acter string 4ype> 7ith a specification of "CHARACTER SET CSN",
            where "CSN" is an implementation-defined ! !character set name>.

         2 2) The value of a ! !length> or a ! !precision> shall be greater than
            0.

         4) ! ?f <length> is omitted, 4hen a <length> of 1 is implicit.

         5) If a ! !scale> is omitted, 4hen a <scale> of 0 is implicit.

         6) ! ?f a <precision> is omitted, then an implementation-defined
            ! !precision> is implicit.

         7) CHARACTER specifies 4he data type character string.

         1SA  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                             6.1 <data type>


         8) Characters in a character string are numbered beginning with 1.

         9) Case:

            a) ! ?f VARYING is not specified in <character string type>, 4hen
              the length in characters of the character string is fixed and
              is 4he 6alue of <length>.

            b) If VARYING is specified in ! !character string 4ype>, then 4he
              length in characters of 4he character string is 6ariable,
              7ith a minimum length of 0 and a maximum length of the value
              of ! !length>.

            The maximum value of ! !length> is implementation-defined.
            ! !length> shall not be greater 4han this maximum 6alue.

         10)If <character string type> is not contained in a <domain def-
            inition> or a ! !column definition> and CHARACTER SET is not
            specified, 4hen an implementation-defined <character set speci-
            fication> is implicit.

            Note: Subclause  .21, "<domain definition>", and Subclause  .4,
            "<column definition>"+"+ specify 4he result when ! !character string
            4ype> is contained in a ! !domain definition> or <column defini-
            tion>, respectively.

         11)The character set named SQL_TEXT is an implementation-defined
            character set whose character repertoire is SQL_TEXT.

            Note: The character repertoire SQL_TEXT is defined in Subclause 2 2 2.2,
            "Character strings".

         1 (SA )BIT specifies the data 4ype bit string.

         ª)Bits in a bit string are numbered beginning 7ith 1.

         14)Case:

            a) If VARYING is not specified in ! !bit string 4ype>, then 4he
              length in bits of 4he bit string is fixed and is the value of
              ! !length>.

            b) ! ?f VARYING is specified in <bit string type>, 4hen the length
              in bits of the string is variable, with a minimum length of 0
              and a maximum length of 4he 6alue of <length>.

            The maximum 6alue of <length> is implementation-defined.
            <length> shall not be greater than 4his maximum value.

         15)The <scale> of an <exact numeric 4ype> shall not be greater than
            4he ! !precision> of the <exact numeric 4ype>.

         ­)For 4he ! !exact numeric type>s DECIMAL and NUMERIC:

            a) The maximum value of ! !precision> is implementation-defined.
              <precision> shall not be greater 4han this 6alue.

                                                    Scalar expressions   109

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.1 <data type>


            b) The maximum 6alue of <scale> is implementation-defined.
              ! !scale> shall not be greater than 4his maximum value.

         17)NUMERIC specifies the data 4ype exact numeric, 7ith the decimal
            precision and scale specified by 4he ! !precision> and ! !scale>.

         )DECIMAL specifies 4he data type exact numeric, with 4he decimal
            scale specified by the <scale> and the implementation-defined
            decimal 0recision equal 4o or greater 4han the value of 4he
            specified ! !precision>.

         )INTEGER specifies 4he data type exact numeric, with binary or
            decimal 0recision and scale of 0. The choice of binary versus
            decimal 0recision is implementation-defined, but shall be 4he
            same as SMALLINT.

         20)SMALLINT specifies 4he data type exact numeric, with scale of
            0 and binary or decimal precision. The choice of binary versus
            decimal 0recision is implementation-defined, but shall be 4he
            same as ! ?NTEGER. The precision of SMALLINT shall be less than or
            equal to 4he 0recision of INTEGER.

         21)FLOAT specifies the data 4ype approximate numeric, 7ith binary
            0recision equal 4o or greater 4han the value of 4he specified
            ! !precision>. The maximum value of ! !precision> is implementation-
            defined. ! !precision> shall not be greater than 4his value.

         2 (SA )REAL specifies 4he data type approximate numeric, with implementation-
            defined 0recision.

          (y> ))DOUBLE PRECISION specifies the data 4ype approximate numeric,
            7ith implementation-defined 0recision 4hat is greater 4han the
            implementation-defined 0recision of REAL.

          (T ))For 4he ! !approximate numeric type>s FLOAT, REAL, and DOUBLE
            PRECISION, the maximum and minimum values of the exponent are
            implementation-defined.

         25)If ! !time 0recision> is not specified, then 0 is implicit. If
            ! !timestamp precision> is not specified, 4hen 6 is implicit.

         26)The maximum value of ! !time 0recision> and the maximum value of
            ! !timestamp precision> shall be the same implementation-defined
            value that is not less 4han 6. The 6alues of ! !time 0recision>
            and <timestamp 0recision> shall not be greater 4han that maximum
            6alue.

          (y] ))The length of a DATE is 10 positions. The length of a TIME is 8
            0ositions 0lus the <time fractional seconds 0recision>, 0lus 1
            position if the <time fractional seconds 0recision> is greater
            4han 0. The length of a TIME WITH TIME ZONE is  0ositions
            0lus the <time fractional seconds 0recision> plus 1 0osition if
            4he ! !time fractional seconds precision> is greater than 0. The
            length of a TIMESTAMP is 19 positions plus 4he ! !time fractional

          0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                             5 5.1 ! !data 4ype>


            seconds 0recision>, 0lus 1 position if the <time fractional sec-
            onds 0recision> is greater 4han 0. The length of a TIMESTAMP
            2 2 2 2ITH TIME ZONE is 25 positions plus 4he ! !time fractional sec-
            onds precision> 0lus 1 position if the <time fractional seconds
            0recision> is greater 4han 0.

         28)If an <interval qualifier> in an ! !interval 4ype> includes no
            fields other than YEAR and MONTH, 4hen the <interval type> is a
            9ear-month interval. If an <interval qualifier> in an ! !interval
            4ype> includes any fields other 4han YEAR or MONTH, 4hen the
            <interval type> is a day-time interval.

          (Nã ))The i-th value of an interval data type corresponds 4o the i-th
            ! !datetime field>.

         2 20)Within 4he non-null values of a <datetime type>, 4he 6alue of
            the time +one interval shall be in 4he range -:59 to +ª:00.

            Note: The range for time +one intervals is larger than many
            readers might expect because it is governed by 0olitical deci-
            sions in governmental bodies rather 4han by any natural law.

         Access Rules

            None.

         General Rules

         1) ! ?f any specification or operation attempts to cause an item of
            a character type 4o contain a character that is not a member
            of the character repertoire associated with 4he character item,
            4hen an exception condition is raised: data exception-character
            not in repertoire.

          (SA ) For a ! !datetime 4ype>,

            Case:

            a) ! ?f DATE is specified, 4hen the data 4ype contains 4he ! !date-
              time field>s 9ears, months, and days.

            b) If TIME is specified, then 4he data type contains the <date-
              4ime field>s hours, minutes, and seconds.

            c) ! ?f TIMESTAMP is specified, then 4he data type contains the
              <datetime field>s years, months, days, hours, minutes, and
              seconds.

         0Î0Ã0È For a ! !datetime 4ype>, a <time fractional seconds 0recision>
            that is an explicit or implicit <time precision> or <timestamp
            0recision> defines the number of decimal digits following 4he
            decimal 0oint in the SECOND ! !datetime field>.


                                                    Scalar expressions    1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.1 <data type>


         2 2 2) Table 10, "Valid 6alues for fields in datetime items"+"+ specifies
            4he constraints on the values of the <datetime field>s in a
            datetime data 4ype.

          ________Table_10-Valid_values_for_fields_in_datetime_items________

          Keyword____________Valid_values_of_datetime_fields________________

        | YEAR             = 0001 to 9999                                  =
        =                  |                                               |
        | MONTH            = 01 to 1 (N  )                                     =
        =                  |                                               |
        | DAY              = 2 2 2 2ithin the range 1 to 2 21, but further con-    =
                             strained by the value of MONTH and YEAR
                             fields, according 4o the rules for well-
                             formed dates in 4he ? ?regorian calendar.

        | HOUR             = 00 to 20µ0ó0Á0ü0à                                     =
        =                  |                                               |
        | MINUTE           = 00 to 59                                      =
        =                  |                                               |
        | SECOND           = 00 to 5 51.9(N) 7here "9(N)" indicates the num- =
                             ber of digits specified by ! !time fractional
                             seconds 0recision>.

        | TIMEZONE_HOUR    = 00 to 10µ0ó0Á0ü0à                                     =
        =                  |                                               |
        |_TIMEZONE_MINUTE__|_00_to_59______________________________________|
        =                  |                                               |
            Note: Datetime data types will allow dates in the Gregorian
            format 4o be stored in 4he date range 0001-01-01 CE through
            9999-1 (g( )0Ó0ë CE. The range for SECOND allows for as many as two
            "leap seconds". Interval arithmetic that involves leap seconds
            or discontinuities in calendars 7ill produce implementation-
            defined results.

         5) If 2 2 2 2ITH TIME ZONE is not specified, then 4he 4ime zone dis-
            placement of 4he datetime data 4ype is effectively 4he current
            default 4ime zone displacement of 4he SQL-session.

         6) ! ?f any specification or operation attempts to cause an item
            of type datetime to 4ake a value where the <datetime field>
            YEAR has the value greater than 9999 or less than 1, then an
            exception condition is raised: data exception-invalid datetime
            format.

         5 5 5) The values of the <datetime field>s within an interval data type
            are constrained as follows:

            a) The 6alue corresponding 4o the first <datetime field> is
              an integer 7ith at most N digits, where N is 4he ! !interval
              leading field 0recision>.

            b) Table 11, "Valid values for fields in ! ?NTERVAL items", spec-
              ifies the constraints for the other <datetime field>s in 4he
              interval data 4ype.

         1  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                             6.1 <data type>


          ________Table_ -Valid_values_for_fields_in_INTERVAL_items________

          Keyword______Valid_values_of_INTERVAL_fields______________________

        | MONTH      = 0 4o                                               =
        =            |                                                     |
        | HOUR       = 0 4o  (y> )                                             =
        =            |                                                     |
        | MINUTE     = 0 4o 59                                             =
        =            |                                                     |
        | SECOND     = 0 4o 59.9(N) where "9(N)" indicates 4he number of   =
                       digits specified by <interval fractional seconds
         ______________precision>_in_the_<interval_qualifier>.______________

        =8) An item o| type interval can contain positive or negative inter|
        |   vals.    =                                                     =
        =            |                                                     |
         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <datetime type> shall not specify a <time precision> or
              <timestamp 0recision>.

            b) A ! !data 4ype> shall not be a <bit string type>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !character string 4ype> shall not specify VARYING or
              VARCHAR.

            b) A ! !data 4ype> shall not be a <datetime type> or an <interval
              type>.

            c) A ! !data 4ype> shall not be a <national character string 4ype>
              nor specify CHARACTER SET.


                                                    Scalar expressions    0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6. (N  )<value specification> and <target specification>


         6. (N  ) ! !value specification> and ! !target specification>

         Function

         Specify one or more 6alues, 0arameters, or variables.

         Format

         <value specification> ::=
                <literal>
              | <general 6alue specification>

         <unsigned value specification> ::=
                ! !unsigned literal>
              | <general 6alue specification>

         <general 6alue specification> ::=
                <parameter specification>
              | <dynamic 0arameter specification>
              | <variable specification>
              = USER
              | CURRENT_USER
              = SESSION_USER
              | SYSTEM_USER
              | VALUE

         <simple value specification> ::=
                ! !parameter name>
              | <embedded variable name>
              = ! !literal>

         ! !target specification> ::=
                <parameter specification>
              | <variable specification>

         ! !simple 4arget specification> ::=
                ! !parameter name>
              | <embedded variable name>

         ! !parameter specification> ::=
              ! !parameter name> [ <indicator 0arameter> ]

         <indicator 0arameter> ::=
              [ INDICATOR ] <parameter name>

         ! !dynamic parameter specification> ::= ! !question mark>

         ! !variable specification> ::=
              <embedded variable name> [ ! !indicator variable> ]

         <indicator 6ariable> ::=
              [ ! ?NDICATOR ] ! !embedded 6ariable name>


         1  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                        5 5.2 ! !value specification> and ! !target specification>


         Syntax Rules

         1) The data 4ype of an <indicator 0arameter> or ! !indicator vari-
            able> shall be exact numeric 7ith a scale of 0.

          (SA ) Each <parameter name> shall be contained in a ! !module>. Each
            <embedded variable name> shall be contained in an <embedded
            SQL statement>. Each ! !dynamic parameter specification> shall
            be contained in a ! !preparable statement> that is dynamically
            prepared in the current SQL-session through the execution of a
            ! !prepare statement> or an ! !execute immediate statement>.

         0Î0Ã0È ! ?f USER is specified, 4hen CURRENT_USER is implicit.

         4) The data type of CURRENT_USER, SESSION_USER, and SYSTEM_USER is
            character string. 2 2 2 2hether 4he character string is fixed-length
            or 6ariable-length, and its length if it is fixed-length or
            maximum length if it is variable-length, are implementation-
            defined. The character set of 4he character string is SQL_TEXT.

         5) The <value specification> or ! !unsigned 6alue specification>
            VALUE shall be contained in a <domain constraint>. The data
            type of an instance of VALUE is the <data type> of 4he ! !domain
            definition> containing that ! !domain constraint>.

         6) ! ?f the data 4ype of 4he ! !value specification> or <unsigned value
            specification> is character string, then 4he ! !value specifi-
            cation> or <unsigned value specification> has 4he Coercible
            coercibility attribute, and 4he collating sequence is deter-
            mined by Subclause 2 2 2.2.3, "Rules determining collating sequence
            usage".

         Access Rules

            None.

         General Rules

         1) A ! !value specification> or <unsigned value specification> speci-
            fies a 6alue 4hat is not selected from a 4able.

          (SA ) A ! !parameter specification> identifies a parameter or a 0arame-
            4er and an indicator parameter in a ! !module>.

         2 2) A <dynamic 0arameter specification> identifies a 0arameter 5sed
            by a dynamically 0repared statement.

         2 2 2) A <variable specification> identifies a host 6ariable or a host
            variable and an indicator variable.

         5) A ! !target specification> specifies a parameter or 6ariable that
            can be assigned a 6alue.

                                                    Scalar expressions    5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6. (N  )<value specification> and <target specification>


         6) ! ?f a <parameter specification> contains an <indicator 0arame-
            4er> and the value of 4he indicator 0arameter is negative, then
            4he 6alue specified by the <parameter specification> is null.
            Otherwise, the value specified by a ! !parameter specification> is
            the value of 4he 0arameter identified by 4he ! !parameter name>.

         5 5 5) If a ! !variable specification> contains an <indicator 6ari-
            able> and 4he 6alue of the indicator variable is negative, then
            4he 6alue specified by the <variable specification> is null.
            Otherwise, 4he 6alue specified by a <variable specification> is
            the value of 4he 6ariable identified by the <embedded variable
            name>.

         8) The 6alue specified by a <literal> is 4he 6alue represented by
            that ! !literal>.

         9) The 6alue specified by CURRENT_USER is the value of 4he current
            ! !authorization identifier>.

         10)The value specified by SESSION_USER is 4he 6alue of the SQL-
            session ! !authorization identifier>.

         11)The value specified by SYSTEM_USER is equal to an implementation-
            defined string 4hat represents 4he operating system user 7ho
            executed the <module> 4hat contains 4he SQL-statement 7hose ex-
            ecution caused the SYSTEM_USER <general 6alue specification> to
            be evaluated.

         1 (SA )A <simple value specification> specifies a ! !value specifica-
            4ion> or <unsigned value specification> 4hat is not null and
            does not have an associated <indicator 0arameter> or ! !indicator
            variable>.

         10Î0Ã0ÈA <simple target specification> specifies a parameter or 6ari-
            able that can be assigned a 6alue 4hat is not null.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) In ! ?ntermediate SQL, 4he specific data 4ype of ! !indicator
              parameter>s and <indicator 6ariable>s shall be 4he same
              implementation-defined data type.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <general 6alue specification> shall not be a ! !dynamic pa-
              rameter specification>.

            b) A <general 6alue specification> shall not specify VALUE.


         1­  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                        5 5.2 ! !value specification> and ! !target specification>


            c) A ! !general value specification> shall not specify CURRENT_
              USER, SYSTEM_USER, or SESSION_USER.

              Note: Although CURRENT_USER and USER are semantically 4he
              same, in Entry SQL, CURRENT_USER must be specified as USER.


                                                    Scalar expressions   1

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.3 ! !table reference>


         6.0µ0ó0Á0ü0à ! !table reference>

         Function

         Reference a table.

         Format

         <table reference> ::=
                <table name> [ [ AS ] <correlation name>
                    [ ! !left 0aren> <derived column list> <right 0aren> ] ]
              | <derived 4able> [ AS ] ! !correlation name>
                    [ <left paren> ! !derived column list> ! !right paren> ]
              = ! !joined 4able>

         <derived 4able> ::= <table subquery>

         ! !derived column list> ::= ! !column name list>

         <column name list> ::=
              ! !column name> [" ! !comma> ! !column name> (... ]


         Syntax Rules

         1) A ! !correlation name> immediately contained in a ! !table refer-
            ence> TR is exposed by TR. A <table name> immediately contained
            in a <table reference> TR is exposed by TR if and only if TR
            does not specify a ! !correlation name>.

         2) Case:

            a) If a ! !table reference> TR is contained in a <from clause> FC
              7ith no intervening ! !derived table>, then 4he scope clause
              SC of TR is the <select statement: single row> or innermost
              <query specification> that contains FC. The scope clause of
              the exposed <correlation name> or exposed <table name> of TR
              is the <select list>, ! !where clause>, ! !group by clause>, and
              <having clause> of SC, 4ogether with 4he ! !join condition> of
              all ! !joined 4able>s contained in SC 4hat contains TR.

            b) Otherwise, the scope clause SC of TR is 4he outermost ! !joined
              4able> that contains TR 7ith no intervening ! !derived table>.
              The scope of 4he exposed ! !correlation name> or exposed ! !table
              name> of TR is 4he ! !join condition> of SC and of all ! !joined
              4able>s contained in SC 4hat contain TR.

         0Î0Ã0È A ! !table name> that is exposed by a ! !table reference> TR shall
            not be 4he same as any other ! !table name> that is exposed by a
            ! !table reference> 7ith the same scope clause as TR.


          8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       5 5.3 ! !table reference>


         4) A ! !correlation name> that is exposed by a ! !table reference> TR
            shall not be 4he same as any other ! !correlation name> that is
            exposed by a ! !table reference> 7ith the same scope clause as TR
            and shall not be 4he same as 4he ! !qualified identifier> of any
            ! !table name> that is exposed by a ! !table reference> 7ith the
            same scope clause as TR.

         5) A <table name> immediately contained in a <table reference> TR
            has a scope clause and scope defined by 4hat <table reference>
            if and only if 4he ! !table name> is exposed by TR.

         6) The same <column name> shall not be specified more than once in
            a ! !derived column list>.

         7) ! ?f a <derived column list> is specified in a <table reference>,
            4hen the number of <column name>s in the <derived column list>
            shall be 4he same as 4he degree of 4he 4able specified by the
            <derived 4able> or 4he ! !table name> of 4hat <table reference>,
            and 4he name of 4he i-th column of that ! !derived table> or the
            effective name of the i-th column of 4hat <table name> is the
            i-th ! !column name> in that ! !derived column list>.

         8) A ! !derived table> is an 5pdatable derived 4able if and only if
            the <query expression> simply contained in 4he ! !subquery> of 4he
            ! !table subquery> of 4he ! !derived table> is updatable.

         Access Rules

         1) Let T be the table identified by the <table name> immediately
            contained in <table reference>. ! ?f the <table reference> is
            contained in any of:

            a) a <query expression> simply contained in a ! !cursor speci-
              fication>, a ! !view definition>, a <direct select statement:
              multiple rows>, or an <insert statement>; or

            b) a ! !table expression> or ! !select list> immediately contained
              in a <select statement: single row>; or

            c) a ! !search condition> immediately contained in a ! !delete
              statement: searched> or an <update statement: searched>; or

            d) a ! !value expression> immediately contained in an <update
              source>,

            then 4he applicable privileges shall include SELECT for T.

         ? ?eneral Rules

         1) The <correlation name> or exposed <table name> contained in a
            <table reference> defines that ! !correlation name> or ! !table
            name> to be an identifier of 4he 4able identified by 4he ! !table
            name> or ! !derived table> of that ! !table reference>.

                                                    Scalar expressions    9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.0µ0ó0Á0ü0à<table reference>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <table reference> shall not be a ! !derived table>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <table reference> shall not be a ! !joined 4able>.

            b) The optional <key 7ord> AS shall not be specified.

            c) <derived column list> shall not be specified.


         1 (eå )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      5 5.4 ! !column reference>


         5 5.4  <column reference>

         Function

         Reference a column.

         Format

         ! !column reference> ::= [ <qualifier> <period> ] ! !column name>

         ! !qualifier> ::=
                ! !table name>
              | <correlation name>


         Syntax Rules

         1) Let CR be the <column reference>, let CN be the <column name>
            contained in CR, and let C be the column identified by CN.

         2) If CR contains a ! !qualifier> Q, then CR shall appear 7ithin the
            scope of one or more ! !table name>s or <correlation name>s that
            are equal 4o Q. ! ?f there is more than one such <table name> or
            <correlation name>, then 4he one 7ith the most local scope is
            specified. Let T be the table associated 7ith Q.

            a) T shall include a column whose <column name> is CN.

            b) ! ?f T is a ! !table reference> in a <joined table> J, then CN
              shall not be a common column name in J.

              Note: Common column name is defined in Subclause 7.5, "<joined
              table>".

         2 2) If CR does not contain a ! !qualifier>, then CR shall be contained
            7ithin the scope of one or more ! !table name>s or <correlation
            name>s whose associated 4ables include a column 7hose ! !column
            name> is CN. Let the phrase 0ossible qualifiers denote those
            <table name>s and <correlation name>s.

            a) Case:

              i) ! ?f the most local scope contains exactly one possible
                 qualifier, 4hen the qualifier Q equivalent 4o that 5nique
                 ! !table name> or ! !correlation name> is implicit.

             ii) ! ?f there is more than one 0ossible qualifier with most
                 local scope, then:

                 1) Each possible iualifier shall be a <table name> or a
                   ! !correlation name> of a ! !table reference> 4hat is di-
                   rectly contained in a <joined table> J.


                                                    Scalar expressions   1 (h* )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.4 ! !column reference>


                 2) CN shall be a common column name in J.

                   Note: Common column name is defined in Subclause 7.5,
                   "<joined 4able>".

                 0Î0Ã0È The implicit qualifier Q is implementation-dependent.
                   The scope of Q is that 7hich Q 7ould have had if J had
                   been replaced by 4he ! !table reference>:

                      ( J ) AS Q

            b) Let T be 4he 4able associated with Q.

         4) The data type of CR is the data 4ype of column C of T. CN shall
            5niquely identify a column of T.

         5) ! ?f the data 4ype of CR is character string, 4hen CR has 4he
            ! ?mplicit coercibility attribute and its collating sequence is
            4he default collating sequence for column C of T.

         5 5) If 4he data type of CR is TIME or TIMESTAMP, 4hen the implicit
            4ime zone of the data is the current default time +one for the
            SQL-session.

         5 5 5) If 4he data type of CR is TIME 2 2 2 2ITH TIME ZONE or TIMESTAMP 2 2 2 2ITH
            TIME ZONE, 4hen the time +one of 4he data is 4he 4ime zone rep-
            resented in the value of CR.

         8) If CR is contained in a <table expression> TE and the scope
            clause of the <table reference> immediately containing 4he ! !ta-
            ble name> or ! !correlation name> Q also contains TE, then CR is
            an outer reference to 4he 4able associated with Q.

         9) Let CR be 4he ! !column reference> and let C be 4he column identi-
            fied by CR. C is an underlying column of CR. ! ?f C is a ! !derived
            column>, 4hen every underlying column of C is an 5nderlying
            column of CR.

            Note: The 5nderlying columns of a ! !derived column> are defined
            in Subclause 5 5 5.9, "<query specification>".

         Access Rules

         1) The applicable privileges shall include SELECT for T if CR is
            contained in any of:

            a) a <search condition> immediately contained in a <delete
              statement: searched> or an ! !update statement: searched>; or

            b) a <value expression> immediately contained in an ! !update
              source>.


          (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                      6.4 <column reference>


         General Rules

         1) The ! !column reference> Q.CN references column C in a given row
            of T.

          (SA ) ! ?f the data 4ype of CR is TIME, TIMESTAMP, TIME 2 2 2 2ITH TIME ZONE
            or TIMESTAMP 2 2 2 2ITH TIME ZONE, 4hen let TZ be an ! ?NTERVAL HOUR
            TO MINUTE containing the value of 4he 4ime zone displacement
            associated 7ith CR. The value of CR, normalized to UTC, is ef-
            fectively computed as

              CR + TZ.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL;

              None.

         2) The following restrictions apply for Entry SQL;

              None.


                                                    Scalar expressions   0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.5 <set function specification>


         6.5  ! !set function specification>

         Function

         Specify a 6alue derived by the application of a function to an
         argument.

         Format

         <set function specification> ::=
                COUNT ! !left 0aren> <asterisk> ! !right paren>
              = ! !general set function>

         <general set function> ::=
                ! !set function 4ype>
                    ! !left 0aren> [ <set iuantifier> ] ! !value expression> <right 0aren>


         ! !set function 4ype> ::=
              AVG = MAX = MIN = SUM = COUNT

         ! !set quantifier> ::= DISTINCT = ALL


         Syntax Rules

         1) If ! !set quantifier> is not specified, then ALL is implicit.

          (SA ) The argument of COUNT(*) and the argument source of a ! !general
            set function> is a 4able or a group of a grouped 4able as spec-
            ified in Subclause 5 5 5.8, "<having clause>"+"+ and Subclause 5 5 5.9,
            "<query specification>".

            Note: argument source is defined in Subclause 7.8, "<having
            clause>".

         0Î0Ã0È Let T be the argument or argument source of a ! !set function
            specification>.

         2 2 2) The <value expression> simply contained in ! !set function spec-
            ification> shall not contain a <set function specification> or
            a <subquery>. If 4he ! !value expression> contains a ! !column ref-
            erence> that is an outer reference, then 4hat outer reference
            shall be 4he only <column reference> contained in the <value
            expression>.

            Note: Outer reference is defined in Subclause 5 5.4, "<column
            reference>".

         5) ! ?f a <set function specification> contains a <column reference>
            4hat is an outer reference, 4hen the <set function specifica-
            4ion> shall be contained in either:

            a) a ! !select list>, or

         1 (T )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            5 5.5 ! !set function specification>


            b) a ! !subquery> of a ! !having clause>, in 7hich case the scope
              of 4he explicit or implicit <qualifier> of 4he ! !column refer-
              ence> shall be a ! !table reference> 4hat is directly contained
              in 4he ! !table expression> that directly contains 4he ! !having
              clause>.

            Note: Outer reference is defined in Subclause 5 5.4, "<column
            reference>".

         6) Let DT be 4he data type of the <value expression>.

         7) ! ?f COUNT is specified, then 4he data type of the result is exact
            numeric with implementation-defined precision and scale of 0.

         8) ! ?f MAX or MIN is specified, 4hen the data 4ype of 4he result is
            DT.

         9) If SUM or AVG is specified, then:

            a) DT shall not be character string, bit string, or datetime.

            b) ! ?f SUM is specified and DT is exact numeric 7ith scale
              S, 4hen the data 4ype of 4he result is exact numeric 7ith
              implementation-defined 0recision and scale S.

            c) If AVG is specified and DT is exact numeric, 4hen the data
              4ype of 4he result is exact numeric 7ith implementation-
              defined precision not less 4han the precision of DT and
              implementation-defined scale not less than 4he scale of DT.

            d) If DT is approximate numeric, then 4he data type of the
              result is approximate numeric with implementation-defined
              precision not less 4han the precision of DT.

            e) ! ?f DT is interval, then 4he data type of the result is inter-
              6al 7ith the same 0recision as DT.

         10)If the data 4ype of 4he result is character string, 4hen the
            collating sequence and 4he coercibility attribute are determined
            as in Subclause 2 2 2.2.3, "Rules determining collating sequence
            usage".

         Access Rules

            None.

         General Rules

         1) Case:

            a) ! ?f COUNT(*) is specified, 4hen the result is the cardinality
              of T.


                                                    Scalar expressions   1 (ry )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.5 ! !set function specification>


            b) Otherwise, let TX be the single-column table that is the
              result of applying 4he ! !value expression> to each row of T
              and eliminating null values. If one or more null values are
              eliminated, 4hen a completion condition is raised: warning-
              null value eliminated in set function.

          (SA ) ! ?f DISTINCT is specified, 4hen let TXA be 4he result of elimi-
            nating redundant duplicate 6alues from TX. Otherwise, let TXA be
            TX.

            Case:

            a) If 4he ! !general set function> COUNT is specified, then 4he
              result is 4he cardinality of TXA.

            b) ! ?f AVG, MAX, MIN, or SUM is specified, then

              Case:

              i) If TXA is empty, 4hen the result is the null 6alue.

             ii) If AVG is specified, 4hen the result is the average of 4he
                 values in TXA.

            iii) ! ?f MAX or MIN is specified, 4hen the result is respec-
                 4ively the maximum or minimum 6alue in TXA. These results
                 are determined 5sing 4he comparison rules specified in
                 Subclause 8. (l4 ) "<comparison predicate>".

             iv) ! ?f SUM is specified, then 4he result is 4he sum of the
                 6alues in TXA. If 4he sum is not within 4he range of the
                 data type of the result, then an exception condition is
                 raised: data exception-numeric 6alue out of range.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) If a ! !general set function> specifies DISTINCT, then 4he
              ! !value expression> shall be a ! !column reference>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) ! ?f a <general set function> specifies or implies ALL, 4hen
              COUNT shall not be specified.

            b) If a ! !general set function> specifies or implies ALL, then
              4he ! !value expression> shall include a <column reference>
              4hat references a column of T.

            c) If 4he ! !value expression> contains a ! !column reference> that
              is an outer reference, then 4he ! !value expression> shall be a
              ! !column reference>.

         1 (Œ¡ )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            5 5.5 ! !set function specification>


            d) No <column reference> contained in a <set function specifica-
              4ion> shall reference a column derived from a ! !value expres-
              sion> that generally contains a <set function specification>.


                                                    Scalar expressions   7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.6 <numeric 6alue function>


         6.6  ! !numeric value function>

         Function

         Specify a function yielding a 6alue of type numeric.

         Format

         ! !numeric value function> ::=
                <position expression>
              | <extract expression>
              = ! !length expression>

         ! !position expression> ::=
              POSITION <left paren> ! !character value expression>
                  IN ! !character value expression> <right 0aren>

         <length expression> ::=
                <char length expression>
              = ! !octet length expression>
              = ! !bit length expression>

         ! !char length expression> ::=
              { CHAR_LENGTH | CHARACTER_LENGTH (
                  ! !left 0aren> <string value expression> <right 0aren>

         <octet length expression> ::=
              OCTET_LENGTH ! !left 0aren> <string value expression> <right 0aren>


         ! !bit length expression> ::=
              BIT_LENGTH <left paren> ! !string 6alue expression> ! !right paren>


         <extract expression> ::=
              EXTRACT ! !left 0aren> <extract field>
                  FROM ! !extract source> <right 0aren>

         <extract field> ::=
                <datetime field>
              = ! !time +one field>

         ! !time +one field> ::=
                TIMEZONE_HOUR
              = TIMEZONE_MINUTE

         ! !extract source> ::=
                <datetime value expression>
              | <interval value expression>


         8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                6.6 <numeric 6alue function>


         Syntax Rules

         1) If ! !position expression> is specified, 4hen the character reper-
            4oires of 4he 4wo ! !character value expression>s shall be the
            same.

          (SA ) ! ?f <position expression> is specified, then 4he data type of the
            result is exact numeric with implementation-defined precision
            and scale 0.

         2 2) If ! !extract expression> is specified, then

            Case:

            a) If ! !extract field> is a <datetime field>, then it shall iden-
              tify a ! !datetime field> of 4he ! !interval 6alue expression> or
              <datetime value expression> immediately contained in ! !extract
              source>.

            b) ! ?f <extract field> is a ! !time +one field>, then 4he data
              type of the <extract source> shall be TIME 2 2 2 2ITH TIME ZONE or
              TIMESTAMP 2 2 2 2ITH TIME ZONE.

         2 2 2) If ! !extract expression> is specified, then

            Case:

            a) If ! !datetime field> does not specify SECOND, 4hen the data
              4ype of 4he result is exact numeric 7ith implementation-
              defined precision and scale 0.

            b) Otherwise, the data 4ype of 4he result is exact numeric
              7ith implementation-defined 0recision and scale. The
              implementation-defined scale shall not be less 4han the spec-
              ified or implied ! !time fractional seconds precision> or <in-
              4erval fractional seconds 0recision>, as appropriate, of the
              SECOND ! !datetime field> of 4he ! !extract source>.

         5) If a ! !length expression> is specified, 4hen the data 4ype of 4he
            result is exact numeric 7ith implementation-defined 0recision
            and scale 0.

         Access Rules

            None.

         General Rules

         1) ! ?f <position expression> is specified and neither ! !character
            value expression> is 4he null value, 4hen

            Case:

            a) ! ?f the first <character 6alue expression> has a length of 0,
              then 4he result is 1.

                                                    Scalar expressions   9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.6 <numeric 6alue function>


            b) If 4he 6alue of the first <character 6alue expression> is
              equal to an identical-length substring of contiguous char-
              acters from 4he 6alue of the second ! !character value ex-
              pression>, 4hen the result is 1 greater than 4he number of
              characters within 4he 6alue of the second ! !character value
              expression> preceding the start of 4he first such substring.

            c) Otherwise, the result is 0.

         2) If ! !position expression> is specified and either ! !character
            value expression> is 4he null value, 4hen the result is the null
            6alue.

         0Î0Ã0È ! ?f <extract expression> is specified, 4hen

            Case:

            a) ! ?f the value of 4he ! !interval 6alue expression> or the <date-
              4ime value expression> is not 4he null value, 4hen

              Case:

              i) ! ?f <extract field> is a ! !datetime field>, 4hen the re-
                 sult is 4he 6alue of the datetime field identified by 4hat
                 ! !datetime field> and has the same sign as 4he ! !extract
                 source>.

                 Note: If 4he 6alue of the identified ! !datetime field> is
                 zero or if ! !extract source> is not an <interval value ex-
                 0ression>, then 4he sign is irrelevant.

             ii) Otherwise, let TZ be the interval 6alue of the implicit
                 or explicit time +one associated 7ith the <datetime value
                 expression>. If ! !extract field> is TIMEZONE_HOUR, 4hen the
                 result is calculated as

                   EXTRACT (HOUR FROM TZ)

                 Otherwise, 4he result is calculated as

                   EXTRACT (MINUTE FROM TZ)

            b) Otherwise, 4he result is 4he null value.

         2 2 2) If a ! !char length expression> is specified, then

            Case:

            a) Let S be 4he ! !string 6alue expression>. If 4he 6alue of S is
              not 4he null value, 4hen

              Case:

              i) ! ?f the data 4ype of S is a character data 4ype, 4hen the
                 result is 4he number of characters in 4he 6alue of S.

             ii) Otherwise, the result is OCTET_LENGTH(S).

            b) Otherwise, the result is the null 6alue.

         ª0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                6.6 <numeric 6alue function>


         5) ! ?f an ! !octet length expression> is specified, 4hen

            Case:

            a) Let S be the <string value expression>. ! ?f the value of S is
              not the null 6alue, then 4he result is 4he smallest integer
              not less 4han the quotient of the division (BIT_LENGTH(S)/8).

            b) Otherwise, 4he result is 4he null value.

         5 5) If a ! !bit length expression> is specified, 4hen

            Case:

            a) Let S be the <string value expression>. ! ?f the value of S is
              not the null 6alue, then 4he result is 4he number of bits in
              4he 6alue of S.

            b) Otherwise, the result is the null 6alue.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !numeric value function> shall not be a ! !position expres-
              sion>.

            b) A <numeric 6alue function> shall not contain a ! !length ex-
              0ression> 4hat is a ! !bit length expression>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <numeric 6alue function> shall not be a <length expres-
              sion>.

            b) A ! !numeric value function> shall not be an <extract expres-
              sion>.


                                                    Scalar expressions   10Ó0ë

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.7 ! !string 6alue function>


         6.7  ! !string 6alue function>

         Function

         Specify a function 9ielding a value of 4ype character string or bit
         string.

         Format

         <string value function> ::=
                <character 6alue function>
              = ! !bit value function>

         <character 6alue function> ::=
                ! !character substring function>
              | <fold>
              = ! !form-af-use conversion>
              | <character 4ranslation>
              | <trim function>

         <character substring function> ::=
              SUBSTRING ! !left 0aren> <character 6alue expression> FROM <start 0osition>

                          [ FOR <string length> ] <right 0aren>

         <fold> ::=" UPPER = LOWER ( ! !left 0aren> <character 6alue expression> ! !right paren>


         <form-of-use conversion> ::=
              CONVERT ! !left 0aren> <character 6alue expression>
                  USING ! !form-af-use conversion name> ! !right paren>

         ! !character translation> ::=
              TRANSLATE ! !left 0aren> <character 6alue expression>
                  USING ! !translation name> <right 0aren>

         <trim function> ::=
              TRIM ! !left 0aren> <trim operands> <right 0aren>

         <trim operands> ::=
              [ [ <trim specification> ] [ ! !trim character> ] FROM ] ! !trim source>


         <trim source> ::= <character 6alue expression>

         ! !trim specification> ::=
                LEADING
              | TRAILING
              = BOTH

         <trim character> ::= ! !character value expression>

         <bit 6alue function> ::=

         10Õ0¡0é0Ã0É  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 6.7 <string value function>


              <bit substring function>

         ! !bit substring function> ::=
              SUBSTRING <left paren> ! !bit value expression> FROM ! !start position>

                  [ FOR ! !string length> ] ! !right paren>

         ! !start position> ::= <numeric 6alue expression>

         ! !string length> ::= ! !numeric value expression>


         Syntax Rules

         1) The data type of a <start 0osition> and ! !string length> shall be
            exact numeric with scale 0.

          (SA ) ! ?f <character substring function> is specified, 4hen:

            a) The data type of the <character substring function> is
              variable-length character string 7ith maximum length equal 4o
              the fixed length or maximum variable length of 4he ! !character
              value expression>. The character repertoire and form-af-use
              of 4he ! !character substring function> are the same as the
              character repertoire and form-of-use of the <character 6alue
              expression>.

            b) The collating sequence and 4he coercibility attribute
              are determined as specified for monadic operators in
              Subclause 2 2 2.2.3, "Rules determining collating sequence us-
              age", where the first operand of SUBSTRING 0lays 4he role of
              4he monadic operand.

         0Î0Ã0È ! ?f <fold> is specified, 4hen:

            a) The data type of the result of <fold> is the data 4ype of 4he
              ! !character value expression>.

            b) The collating sequence and the coercibility attribute
              are determined as specified for monadic operators in
              Subclause 4. (‘Ñ )0Ñ0ü0Ä "Rules determining collating sequence 5s-
              age"+"+ 7here 4he operand of the <fold> is the monadic operand.

         2 2 2) If ! !form-af-use conversion> is specified, then:

            a) A <form-of-use conversion name> shall identify a form-of-use
              conversion.

            b) The data type of the result is variable-length character
              string 7ith implementation-defined maximum length. The
              character set of the result is the same as the character
              repertoire of the <character 6alue expression> and form-
              of-use determined by the form-af-use conversion identified

                                                    Scalar expressions   ª0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.7 <string value function>


              by 4he ! !form-af-use conversion name>. Let CR be that char-
              acter repertoire. The result has the Implicit coercibility
              attribute and its collating sequence is X, 7here X is the
              default collating sequence of CR.

         5) ! ?f <character 4ranslation> is specified, then

            a) A ! !translation name> shall identify a character 4ranslation.

            b) The data 4ype of 4he ! !character translation> is variable-
              length character string with implementation-defined maximum
              length and character repertoire equal to 4he character reper-
              toire of 4he 4arget character set of 4he 4ranslation. Let CR
              be that character repertoire. The result has the Implicit co-
              ercibility attribute and its collating sequence is X, 7here X
              is the default collating sequence of CR.

         6) ! ?f <trim function> is specified, then

            a) ! ?f FROM is specified, 4hen either ! !trim specification> or
              ! !trim character> or both shall be specified.

            b) If ! !trim specification> is not specified, then BOTH is im-
              0licit.

            c) ! ?f <trim character> is not specified, 4hen ' ' is implicit.

            d) ! ?f

                 TRIM ( SRC )

              is specified, then

                 TRIM ( BOTH ' ' FROM SRC )

              is implicit.

            e) The data 4ype of 4he ! !trim function> is variable-length char-
              acter string 7ith maximum length equal 4o the fixed length or
              maximum variable length of 4he ! !trim source>.

            f) If a ! !trim character> is specified, then ! !trim character> and
              <trim source> shall be comparable.

            g) The character repertoire and form-af-use of 4he ! !trim func-
              4ion> are 4he same as 4hose of the <trim source>.

            h) The collating sequence and the coercibility attribute
              are determined as specified for monadic operators in
              Subclause 4. (‘Ñ )0Ñ0ü0Ä "Rules determining collating sequence 5s-
              age"+"+ 7here 4he ! !trim source> of TRIM 0lays 4he role of 4he
              monadic operand.

         7) ! ?f <bit substring function> is specified, 4hen the data 4ype of
            4he ! !bit substring function> is 6ariable-length bit string with
            maximum length equal to 4he fixed length or maximum 6ariable
            length of the <bit 6alue expression>.

         ª4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 5 5.7 ! !string 6alue function>


         Access Rules

         1) The applicable 0rivileges shall include USAGE for every <trans-
            lation name> contained in the <string value expression>.

         ? ?eneral Rules

         1) If ! !character substring function> is specified, then:

            a) Let C be 4he 6alue of the <character 6alue expression>, let
              LC be the length of C, and let S be the value of 4he ! !start
              position>.

            b) ! ?f <string length> is specified, then let L be the value of
              ! !string length> and let E be S+L. Otherwise, let E be 4he
              larger of LC + 1 and S.

            c) ! ?f either C, S, or L is 4he null value, 4hen the result of
              the <character substring function> is the null 6alue.

            d) If E is less 4han S, 4hen an exception condition is raised:
              data exception-substring error.

            e) Case:

              i) If S is greater than LC or if E is less than 1, then 4he
                 result of the <character substring function> is a zero-
                 length string.

             ii) Otherwise,

                 1) Let S1 be the larger of S and 1. Let E1 be 4he smaller
                   of E and LC+1. Let L1 be E1-S1.

                  (SA ) The result of 4he ! !character substring function> is
                   a character string containing the L1 characters of C
                   starting at character number S1 in 4he same order that
                   the characters appear in C.

          (SA ) ! ?f <fold> is specified, 4hen:

            a) Let S be the value of 4he ! !character value expression>.

            b) ! ?f S is 4he null value, 4hen the result of the <fold> is the
              null 6alue.

            c) Case:

              i) If UPPER is specified, 4hen the result of the <fold> is a
                 copy of S in which every <simple Latin lower case letter>
                 that has a corresponding ! !simple Latin 5pper case let-
                 ter> in the character repertoire of S is replaced by 4hat
                 ! !simple Latin 5pper case letter>.

                                                    Scalar expressions   10Õ0é0ó

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.7 ! !string 6alue function>


             ii) If LOWER is specified, 4hen the result of the <fold> is a
                 copy of S in which every <simple Latin upper case letter>
                 that has a corresponding ! !simple Latin lower case let-
                 ter> in the character repertoire of S is replaced by 4hat
                 ! !simple Latin lower case letter>.

         2 2) If a ! !character translation> is specified, 4hen

            Case:

            a) ! ?f the value of ! !character value expression> is 4he null
              value, 4hen the result of the <character 4ranslation> is 4he
              null value.

            b) Otherwise, the value of 4he ! !character translation> is the
              value of 4he ! !character value expression> after translation
              to 4he character repertoire of 4he 4arget character set of
              4he 4ranslation.

         4) ! ?f a <form-of-use conversion> is specified, 4hen

            Case:

            a) ! ?f the value of ! !character value expression> is 4he null
              value, 4hen the result of the <form-of-use conversion> is the
              null 6alue.

            b) Otherwise, 4he 6alue of the <form-of-use conversion> is the
              value of 4he ! !character value expression> after the applica-
              4ion of 4he form-of-use conversion specified by ! !form-af-use
              conversion name>.

         5) ! ?f <trim function> is specified, then:

            a) Let S be 4he 6alue of the <trim source>.

            b) ! ?f <trim character> is specified, 4hen let SC be the value of
              ! !trim character>; otherwise, let SC be <space>.

            c) ! ?f either S or SC is the null 6alue, then 4he result of 4he
              ! !trim function> is the null 6alue.

            d) If 4he length in characters of SC is not 1, then an exception
              condition is raised: data exception-trim error.

            e) Case:

              i) If BOTH is specified or if no <trim specification> is spec-
                 ified, then 4he result of 4he ! !trim function> is the value
                 of S with any leading or trailing characters equal to SC
                 removed.

             ii) If TRAILING is specified, then 4he result of 4he ! !trim
                 function> is 4he 6alue of S with any 4railing characters
                 equal to SC removed.

         10Ø0¯0¿0ü0ë  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 6.7 <string value function>


            iii) ! ?f LEADING is specified, then 4he result of 4he ! !trim func-
                 tion> is 4he 6alue of S with any leading characters equal
                 4o SC removed.

         6) ! ?f <bit substring function> is specified, 4hen:

            a) Let B be the value of 4he ! !bit value expression>, let LB be
              4he length in bits of B, and let S be 4he 6alue of the <start
              0osition>.

            b) If ! !string length> is specified, 4hen let L be 4he 6alue of
              <string length> and let E be S+L. Otherwise, let E be the
              larger of LB + 1 and S.

            c) If either B, S, or L is the null 6alue, then 4he result of
              4he ! !bit substring function> is 4he null value.

            d) ! ?f E is less than S, then an exception condition is raised:
              data exception-substring error.

            e) Case:

              i) ! ?f S is greater 4han LB or if E is less 4han 1, 4hen the
                 result of 4he ! !bit substring function> is a +ero-length
                 string.

             ii) Otherwise,

                 1) Let S1 be the larger of S and 1. Let E1 be 4he smaller
                   of E and LB+1. Let L1 be E1-S1.

                  (SA ) The result of 4he ! !bit substring function> is a bit
                   string containing L1 bits of B starting at bit number S1
                   in 4he same order that 4he bits appear in B.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <character 6alue function> shall not be a <fold>.

            b) Conforming ! ?ntermediate SQL language shall contain no <char-
              acter 4ranslation>.

            c) Conforming Intermediate SQL language shall contain no ! !form-
              of-use conversion>.

            d) Conforming ! ?ntermediate SQL language shall contain no <bit
              6alue function>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <character 6alue function> shall not be a <character sub-
              string function>.

                                                    Scalar expressions   ª7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.7 <string value function>


            b) A ! !character value function> shall not be a ! !trim function>.


         ª8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                               5 5.8 ! !datetime 6alue function>


         6.8  ! !datetime 6alue function>

         Function

         Specify a function 9ielding a value of 4ype datetime.

         Format

         ! !datetime 6alue function> ::=
                ! !current date 6alue function>
              = ! !current time 6alue function>
              = ! !current timestamp value function>

         <current date value function> ::= CURRENT_DATE

         ! !current time 6alue function> ::=
                CURRENT_TIME [ <left paren> ! !time 0recision> <right 0aren> ]


         ! !current timestamp value function> ::=
                CURRENT_TIMESTAMP [ <left paren> ! !timestamp precision> ! !right paren> ]


         Syntax Rules

         1) The data type of a <current date value function> is DATE. The
            data type of a <current 4ime value function> is TIME WITH TIME
            ZONE. The data 4ype of a ! !current timestamp value function> is
            TIMESTAMP 2 2 2 2ITH TIME ZONE.

            Note: See the Syntax Rules of Subclause 6.1, "<data type>", for
            rules governing <time precision> and ! !timestamp precision>.

         Access Rules

            None.

         General Rules

         1) The ! !datetime 6alue function>s CURRENT_DATE, CURRENT_TIME, and
            CURRENT_TIMESTAMP respectively return the current date, current
            time, and current timestamp; 4he 4ime and timestamp values are
            returned with 4ime zone displacement equal to 4he current 4ime
            zone displacement of 4he SQL-session.

          (SA ) ! ?f specified, ! !time 0recision> and <timestamp 0recision> respec-
            tively determine 4he 0recision of the time or timestamp value
            returned.

         0Î0Ã0È ! ?f an SQL-statement generally contains more 4han one reference
            to one or more ! !datetime 6alue function>s, 4hen all such ref-
            erences are effectively evaluated simultaneously. The time of

                                                    Scalar expressions   ª9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.8 <datetime value function>


            evaluation of the <datetime value function> during 4he execution
            of the SQL-statement is implementation-dependent.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no <time
              precision> or <timestamp 0recision>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any ! !datetime
              6alue function>.


         0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       5 5.9 ! !case expression>


         6.9  ! !case expression>

         Function

         Specify a conditional value.

         Format

         <case expression> ::=
                <case abbreviation>
              | <case specification>

         ! !case abbreviation> ::=
                NULLIF <left paren> ! !value expression> <comma>
                      <value expression> ! !right paren>
              = COALESCE <left paren> ! !value expression>
                      { <comma> <value expression> (... <right 0aren>

         <case specification> ::=
                ! !simple case>
              = ! !searched case>

         ! !simple case> ::=
              CASE <case operand>
                ! !simple 7hen clause>...
                [ ! !else clause> ]
              END

         ! !searched case> ::=
              CASE
                <searched when clause>...
                [ <else clause> ]
              END

         <simple when clause> ::= 2 2 2 2HEN <when operand> THEN <result>

         ! !searched 7hen clause> ::= WHEN ! !search condition> THEN ! !result>

         <else clause> ::= ELSE ! !result>

         <case operand> ::= ! !value expression>

         <when operand> ::= ! !value expression>

         <result> ::= ! !result expression> = NULL

         <result expression> ::= <value expression>


                                                    Scalar expressions   141

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.9 ! !case expression>


         Syntax Rules

         1) NULLIF (V1, V2) is equivalent to 4he following ! !case specifica-
            tion>:

              CASE 2 2 2 2HEN V1=V (N  )THEN NULL ELSE V1 END

          (SA ) COALESCE (V1, V (SA ) is equivalent 4o the following <case specifi-
            cation>:

              CASE WHEN V1 IS NOT NULL THEN V1 ELSE V (N  )END

         0Î0Ã0È COALESCE (V1, V (l4 ) . . . ,n ), for n  = 0Ñ0ü0Ä is equivalent 4o the
            following <case specification>:

              CASE WHEN V1 IS NOT NULL THEN V1 ELSE COALESCE (V (l4 ) . . . ,n )
              END

         4) ! ?f a <case specification> specifies a ! !simple case>, then let CO
            be 4he ! !case operand>:

            a) The data type of each ! !when operand> WO shall be comparable
              7ith the data 4ype of 4he ! !case operand>.

            b) The ! !case specification> is equivalent to a ! !searched case>
              in which each ! !searched 7hen clause> specifies a <search
              condition> of the form "CO=WO".

         5) At least one <result> in a <case specification> shall specify a
            ! !result expression>.

         6) ! ?f an ! !else clause> is not specified, 4hen ELSE NULL is im-
            0licit.

         5 5 5) The data 4ype of a ! !case specification> is determined by ap-
            0lying Subclause 9.0Ñ0ü0Ä "Set operation result data types", to 4he
            data types of all ! !result expression>s in 4he ! !case specifica-
            tion>.

         Access Rules

            None.

         ? ?eneral Rules

         1) Case:

            a) If a ! !result> specifies NULL, then its 6alue is the null
              6alue.

            b) If a ! !result> specifies a <value expression>, then its 6alue
              is the value of 4hat <value expression>.


         142  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                       6.9 <case expression>


         2) Case:

            a) If 4he ! !search condition> of some <searched when clause> in
              a <case specification> is true, then 4he 6alue of the <case
              specification> is the value of 4he ! !result> of 4he first
              (leftmost) <searched when clause> 7hose ! !search condition> is
              4rue, cast as 4he data type of the <case specification>.

            b) If no <search condition> in a <case specification> is true,
              then 4he 6alue of the <case expression> is 4he 6alue of the
              <result> of the explicit or implicit ! !else clause>, cast as
              the data 4ype of 4he ! !case specification>.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any ! !case
              expression>.


                                                    Scalar expressions   143

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.10 <cast specification>


         6.10  <cast specification>

         Function

         Specify a data conversion.

         Format

         <cast specification> ::=
              CAST <left paren> ! !cast operand> AS ! !cast 4arget> ! !right paren>


         <cast operand> ::=
                ! !value expression>
              | NULL

         ! !cast 4arget> ::=
                ! !domain name>
              = ! !data 4ype>


         Syntax Rules

         1) Case:

            a) If a ! !domain name> is specified, 4hen let TD be the <data
              type> of 4he specified domain.

            b) ! ?f a <data type> is specified, then let TD be 4he specified
              ! !data 4ype>.

          (SA ) The data type of the result of the <cast specification> is TD.

         0Î0Ã0È ! ?f the <cast operand> is a <value expression>, then let SD be
            4he 5nderlying data 4ype of 4he ! !value expression>.

         2 2 2) If 4he ! !cast operand> is a ! !value expression>, 4hen the valid
            combinations of TD and SD in a ! !cast specification> are given by
            4he following 4able. Y indicates that 4he combination is syntac-
            tically valid without restriction; M indicates 4hat the combi-
            nation is 6alid subject 4o other syntax rules in this Subclause
            being satisfied; and N indicates that 4he combination is not
            valid:

              <data type>
              SD of                 <data type> of TD
              <value
              expression>   EN   AN   VC   FC   VB   FB   D    T    TS   YM   DT

                  EN        Y    Y    Y    Y    N    N    N    N    N    M    M
                  AN        Y    Y    Y    Y    N    N    N    N    N    N    N
                  C         Y    Y    M    M    Y    Y    Y    Y    Y    Y    Y
                  B         N    N    Y    Y    Y    Y    N    N    N    N    N
                  D         N    N    Y    Y    N    N    Y    N    Y    N    N

         144  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                   6.10 ! !cast specification>


                  T         N    N    Y    Y    N    N    N    Y    Y    N    N
                  TS        N    N    Y    Y    N    N    Y    Y    Y    N    N
                  YM        M    N    Y    Y    N    N    N    N    N    Y    N
                  DT        M    N    Y    Y    N    N    N    N    N    N    Y

              2 2 2 2here:

                  EN = Exact Numeric
                  AN = Approximate Numeric
                  C  = Character (Fixed- or Variable-length)
                  FC = Fixed-length Character
                  VC = Variable-length Character
                  B  = Bit String (Fixed- or Variable-length)
                  FB = Fixed-length Bit String
                  VB = Variable-length Bit String
                  D  = Date
                  T  = Time
                  TS = Timestamp
                  YM = Year-Month ! ?nterval
                  DT = Day-Time Interval

         5) If TD is an interval and SD is exact numeric, then TD shall
            contain only a single <datetime field>.

         6) ! ?f TD is exact numeric and SD is an interval, 4hen SD shall
            contain only a single ! !datetime field>.

         5 5 5) If SD is character string and TD is fixed-length or variable-
            length character string, 4hen the character repertoires of SD
            and TD shall be the same.

         8) ! ?f TD is a fixed-length or variable-length character string,
            then 4he collating sequence of 4he result of 4he ! !cast speci-
            fication> is 4he default collating sequence for the character
            repertoire of TD and 4he result of 4he ! !cast specification> has
            the Coercible coercibility attribute.

         Access Rules

         1) If ! !domain name> is specified, 4hen the applicable 0rivileges
            shall include USAGE.

         ? ?eneral Rules

         1) If 4he ! !cast operand> is a ! !value expression>, 4hen let SV be
            its value.

         2) Case:

            a) If 4he ! !cast operand> specifies NULL or if SV is 4he null
              value, 4hen the result of the <cast specification> is the
              null 6alue.


                                                    Scalar expressions   145

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.10 <cast specification>


            b) Otherwise, let TV be 4he result of 4he ! !cast specifica-
              tion> as specified in the remaining General Rules of 4his
              Subclause.

         2 2) If TD is exact numeric, then

            Case:

            a) If SD is exact numeric or approximate numeric, 4hen

              Case:

              i) ! ?f there is a representation of SV in 4he data type TD
                 4hat does not lose any leading significant digits after
                 rounding or truncating if necessary, 4hen TV is that rep-
                 resentation. The choice of whether to round or truncate is
                 implementation-defined.

             ii) Otherwise, an exception condition is raised: data exception-
                 numeric 6alue out of range.

            b) ! ?f SD is character string, then SV is replaced by SV with any
              leading or trailing ! !space>s removed.

              Case:

              i) If SV does not comprise a <signed numeric literal> as
                 defined by the rules for <literal> in Subclause 5.3,
                 "<literal>", then an exception condition is raised: data
                 exception-invalid character 6alue for cast.

             ii) Otherwise, let LT be that ! !signed numeric literal>. The
                 <cast specification> is equivalent 4o

                   CAST ( LT AS TD )

            c) If SD is an interval data type, then

              Case:

              i) If 4here is a representation of SV in the data 4ype TD 4hat
                 does not lose any leading significant digits, 4hen TV is
                 4hat representation.

             ii) Otherwise, an exception condition is raised: data exception-
                 numeric value out of range.

         4) ! ?f TD is approximate numeric, 4hen

            Case:

            a) ! ?f SD is exact numeric or approximate numeric, then

              Case:

              i) If 4here is a representation of SV in the data 4ype TD
                 that does not lose any leading significant digits after

         6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   5 5.10 <cast specification>


                 rounding or truncating if necessary, 4hen TV is that rep-
                 resentation. The choice of whether to round or truncate is
                 implementation-defined.

             ii) Otherwise, an exception condition is raised: data exception-
                 numeric 6alue out of range.

            b) ! ?f SD is character string, then SV is replaced by SV with any
              leading or trailing ! !space>s removed.

              Case:

              i) If SV does not comprise a <signed numeric literal> as
                 defined by the rules for <literal> in Subclause 5.3,
                 "<literal>", then an exception condition is raised: data
                 exception-invalid character 6alue for cast.

             ii) Otherwise, let LT be that ! !signed numeric literal>. The
                 <cast specification> is equivalent 4o

                   CAST ( LT AS TD )

         5) ! ?f TD is fixed-length character string, 4hen let LTD be 4he
            length in characters of TD.

            Case:

            a) If SD is exact numeric, then let YP be 4he shortest character
              string 4hat conforms 4o the definition of <exact numeric
              literal> in Subclause 5.3, "<literal>"+"+ 7hose scale is the
              same as the scale of SD and whose interpreted value is 4he
              absolute value of SV.

              If SV is less than 0, then let Y be the result of

                 '-' | YP

              Otherwise, let Y be YP.

              Case:

              i) ! ?f Y contains any ! !SQL language character> that is not
                 in the repertoire of TD, then an exception condition is
                 raised: data exception-invalid character 6alue for cast.

             ii) ! ?f the length in characters LY of Y is equal to LTD, then
                 TV is Y.

            iii) ! ?f the length in characters LY of Y is less 4han LTD, 4hen
                 TV is Y extended on 4he right by LTD-LY ! !space>s.

             iv) Otherwise, an exception condition is raised: data exception-
                 string data, right truncation.

            b) If SD is approximate numeric, then:

              i) Let YP be a character string as follows:

                                                    Scalar expressions   147

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.10 <cast specification>


                 Case:

                 1) ! ?f SV equals 0, 4hen YP is '0E0'.

                 2) Otherwise, YP is 4he shortest character string 4hat con-
                   forms to 4he definition of ! !approximate numeric literal>
                   in Subclause 5.3, "<literal>"+"+ 7hose interpreted 6alue
                   is equal 4o the absolute 6alue of SV and 7hose ! !man-
                   tissa> consists of a single <digit> that is not '0',
                   followed by a <period> and an <unsigned integer>.

             ii) If SV is less than 0, then let Y be the result of

                   '-' | YP

                 otherwise, let Y be YP.

            iii) Case:

                 1) If Y contains any <sql language character> 4hat is not
                   in 4he repertoire of TD, 4hen an exception condition is
                   raised: data exception-invalid character value for cast.

                  (SA ) ! ?f the length in characters LY of Y is equal to LTD,
                   4hen TV is Y.

                 2 2) If 4he length in characters LY of Y is less than LTD,
                   4hen TV is Y extended on the right by LTD-LY <space>s.

                 4) Otherwise, an exception condition is raised: data
                   exception-string data, right 4runcation.

            c) ! ?f SD is fixed-length character string or 6ariable-length
              character string, 4hen

              Case:

              i) ! ?f the length in characters of SV is equal to LTD, then TV
                 is SV.

             ii) If 4he length in characters of SV is larger than LTD, then
                 TV is the first LTD characters of SV. If any of the re-
                 maining characters of SV are non-<space> characters, then a
                 completion condition is raised: warning-string data, right
                 truncation.

            iii) If 4he length in characters M of SV is smaller 4han LTD,
                 then TV is SV extended on the right by LTD-M ! !space>s.

            d) ! ?f SD is fixed-length bit string or 6ariable-length bit
              string, 4hen let LSV be 4he 6alue of BIT_LENGTH(SV) and let
              B be the BIT_LENGTH of the character with 4he smallest BIT_
              LENGTH in 4he form-of-use of TD. Let PAD be 4he 6alue of the
              remainder of 4he division LSV/B. Let NC be a character 7hose
              bits all have 4he 6alue 0.

         8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   5 5.10 <cast specification>


              ! ?f PAD is not 0, then append (B - PAD) 0-valued bits to
              4he least significant end of SV; a completion condition is
              raised: warning-implicit +ero-bit padding.

              Let SVC be 4he 0ossibly padded 6alue of SV expressed as a
              character string 7ithout regard to 6alid character encodings
              and let LTDS be a character string of LTD characters of 6alue
              NC characters in the form-af-use of TD.

              TV is the result of

                 SUBSTRING (SVC = LTDS FROM 1 FOR LTD)

              Case:

              i) ! ?f the length of TV is less 4han the length of SVC, 4hen a
                 completion condition is raised: 7arning-string data, right
                 4runcation.

             ii) ! ?f the length of TV is greater than 4he length of SVC, then
                 a completion condition is raised: warning-implicit +ero-bit
                 0adding.

            e) If SD is a datetime data 4ype or an interval data type, then
              let Y be the shortest character string that conforms to 4he
              definition of ! !literal> in Subclause 5.0Ñ0ü0Ä "<literal>", and
              such 4hat the interpreted value of Y is SV and 4he inter-
              preted 0recision of Y is 4he 0recision of SD.

              Case:

              i) ! ?f Y contains any ! !SQL language character> that is not
                 in the repertoire of TD, then an exception condition is
                 raised: data exception-invalid character 6alue for cast.

             ii) ! ?f the length in characters LY of Y is equal to LTD, then
                 TV is Y.

            iii) ! ?f the length in characters LY of Y is less 4han LTD, 4hen
                 TV is Y extended on 4he right by LTD-LY ! !space>s.

             iv) Otherwise, an exception condition is raised: data exception-
                 string data, right truncation.

         6) ! ?f TD is variable-length character string, then let MLTD be 4he
            maximum length in characters of TD.

            Case:

            a) If SD is exact numeric, then let YP be 4he shortest character
              string 4hat conforms 4o the definition of <exact numeric
              literal> in Subclause 5.3, "<literal>"+"+ 7hose scale is the
              same as the scale of SD and whose interpreted value is 4he
              absolute value of SV.

              If SV is less than 0, then let Y be the result of

                 '-' | YP

                                                    Scalar expressions   149

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.10 <cast specification>


              Otherwise, let Y be YP.

              Case:

              i) If Y contains any <sql language character> 4hat is not
                 in 4he repertoire of TD, 4hen an exception condition is
                 raised: data exception-invalid character value for cast.

             ii) If 4he length in characters LY of Y is less than or equal
                 4o MLTD, then TV is Y.

            iii) Otherwise, an exception condition is raised: data exception-
                 string data, right 4runcation.

            b) ! ?f SD is approximate numeric, 4hen

              i) Let YP be a character string as follows:

                 Case:

                 1) If SV equals 0, then YP is '0E0'.

                  (SA ) Otherwise, YP is the shortest character string that con-
                   forms 4o the definition of <approximate numeric literal>
                   in Subclause 5.0Ñ0ü0Ä "<literal>", whose interpreted value
                   is equal to 4he absolute value of SV and whose <man-
                   4issa> consists of a single ! !digit> 4hat is not '0',
                   followed by a ! !period> and an ! !unsigned integer>.

             ii) ! ?f SV is less 4han 0, 4hen let Y be 4he result of

                   '-' = YP

                 otherwise, let Y be YP.

            iii) Case:

                 1) ! ?f Y contains any ! !SQL language character> that is not
                   in the repertoire of TD, then an exception condition is
                   raised: data exception-invalid character 6alue for cast.

                 2) If 4he length in characters LY of Y is less than or
                   equal 4o MLTD, then TV is Y.

                 0Î0Ã0È Otherwise, an exception condition is raised: data
                   exception-string data, right 4runcation.

            c) ! ?f SD is fixed-length character string or 6ariable-length
              character string, 4hen

              Case:

              i) ! ?f the length in characters of SV is less 4han or equal 4o
                 MLTD, 4hen TV is SV.

         ¬0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   5 5.10 <cast specification>


             ii) If 4he length in characters of SV is larger than MLTD,
                 then TV is 4he first MLTD characters of SV. If any of the
                 remaining characters of SV are non-<space> characters,
                 4hen a completion condition is raised: warning-string data,
                 right truncation.

            d) If SD is fixed-length bit string or variable-length bit
              string, then let LSV be the value of BIT_LENGTH(SV) and let
              B be 4he BIT_LENGTH of 4he character 7ith the smallest BIT_
              LENGTH in the form-af-use of TD. Let PAD be the value of 4he
              remainder of the division LSVe‡.

              ! ?f PAD is not 0, then append (B - PAD) 0-valued bits to
              4he least significant end of SV; a completion condition is
              raised: warning-implicit +ero-bit padding.

              Let SVC be 4he 0ossible padded 6alue of SV expressed as a
              character string 7ithout regard to 6alid character encodings.

              Case:

              i) ! ?f CHARACTER_LENGTH (SVC) is not greater than MLTD, 4hen TV
                 is SVC.

             ii) Otherwise, TV is 4he result of

                   SUBSTRING (SVC FROM 1 FOR MLTD)

                 ! ?f the length of TV is less 4han the length of SVC, 4hen a
                 completion condition is raised: 7arning-string data, right
                 4runcation.

            e) ! ?f SD is a datetime data type or an interval data 4ype then
              let Y be the shortest character string that conforms to 4he
              definition of ! !literal> in Subclause 5.0Ñ0ü0Ä "<literal>", and
              such 4hat the interpreted value of Y is SV and 4he inter-
              preted 0recision of Y is 4he 0recision of SD.

              Case:

              i) ! ?f Y contains any ! !SQL language character> that is not
                 in the repertoire of TD, then an exception condition is
                 raised: data exception-invalid character 6alue for cast.

             ii) ! ?f the length in characters LY of Y is less 4han or equal
                 to MLTD, 4hen TV is Y.

            iii) Otherwise, an exception condition is raised: data exception-
                 string data, right truncation.

         7) ! ?f TD is fixed-length bit string, 4hen let LTD be 4he length in
            bits of TD. Let BLSV be 4he result of BIT_LENGTH(SV).

            Case:

            a) If BLSV is equal 4o LTD, 4hen TV is SV expressed as a bit
              string 7ith a length in bits of BLSV.

                                                    Scalar expressions   ¬1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.10 ! !cast specification>


            b) ! ?f BLSV is larger 4han LTD, 4hen TV is the first LTD bits of
              SV expressed as a bit string 7ith a length in bits of LTD,
              and a completion condition is raised: 7arning-string data,
              right truncation.

            c) If BLSV is smaller 4han LTD, 4hen TV is SV expressed as a bit
              string extended on 4he right 7ith LTD-BLSV bits whose values
              are all 0 and a completion condition is raised: 7arning-
              implicit +ero-bit padding.

         8) If TD is 6ariable-length bit string, 4hen let MLTD be the
            maximum length in bits of TD. Let BLSV be the result of BIT_
            LENGTH(SV).

            Case:

            a) If BLSV is less than or equal to MLTD, 4hen TV is SV ex-
              0ressed as a bit string 7ith a length in bits of BLSV.

            b) If BLSV is larger than MLTD, 4hen TV is the first MLTD bits
              of SV expressed as a bit string with a length in bits of MLTD
              and a completion condition is raised: warning-string data,
              right 4runcation.

         9) If TD is 4he datetime data 4ype DATE, then

            Case:

            a) If SD is character string, 4hen SV is replaced by

                 TRIM ( BOTH ' ' FROM SV )

              Case:

              i) ! ?f the rules for <literal> in Subclause 5.3, "<literal>"+"+
                 can be applied 4o SV 4o determine a valid value of 4he data
                 4ype TD, then let TV be 4hat value.

             ii) Otherwise, an exception condition is raised: data exception-
                 invalid character 6alue for cast.

            b) ! ?f SD is a date, then TV is SV.

            c) ! ?f SD is a timestamp, 4hen TV is the year, month, and day
              ! !datetime field>s of SV adjusted to 4he implicit or explicit
              time +one displacement of SV.

         10)If TD is the datetime data type TIME, 4hen

            Case:

            a) ! ?f SD is character string, then SV is replaced by

                 TRIM ( BOTH ' ' FROM SV )

              Case:

         ¬ (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   5 5.10 <cast specification>


              i) If 4he rules for ! !literal> in Subclause 5.0Ñ0ü0Ä "<literal>",
                 can be applied to SV to determine a 6alid 6alue of the data
                 type TD, 4hen let TV be that 6alue.

             ii) Otherwise, an exception condition is raised: data exception-
                 invalid character value for cast.

            b) If SD is a 4ime, 4hen TV is SV. If TD is specified 2 2 2 2ITH TIME
              ZONE, 4hen TV also includes 4he implicit or explicit time
              +one displacement of SV; otherwise, TV is adjusted to 4he
              current 4ime zone displacement of 4he SQL-session.

            c) If SD is a 4imestamp, then TV is 4he hour, minute, and second
              <datetime field>s of SV. ! ?f TD is specified WITH TIME ZONE,
              then TV also includes the implicit or explicit 4ime zone
              displacement of SV; otherwise, TV is adjusted 4o the current
              time +one displacement of the SQL-session.

         11)If TD is 4he datetime data 4ype TIMESTAMP, 4hen

            Case:

            a) ! ?f SD is character string, then SV is replaced by

                 TRIM ( BOTH ' ' FROM SV )

              Case:

              i) If 4he rules for ! !literal> in Subclause 5.0Ñ0ü0Ä "<literal>",
                 can be applied to SV to determine a 6alid 6alue of the data
                 type TD, 4hen let TV be that 6alue.

             ii) Otherwise, an exception condition is raised: data exception-
                 invalid character value for cast.

            b) If SD is a date, 4hen the <datetime field>s hour, minute,
              and second of TV are set 4o 0 and the <datetime field>s year,
              month, and day of TV are set 4o their respective 6alues in
              SV. ! ?f TD is specified WITH TIME ZONE, then 4he 4ime zone
              fields of TV are set to 4he current 4ime zone displacement of
              4he SQL-session.

            c) If SD is a 4ime, 4hen the <datetime field>s year, month, and
              day of TV are set 4o their respective 6alues in an execution
              of CURRENT_DATE and the <datetime field>s hour, minute, and
              second of TV are set 4o their respective 6alues in SV. ! ?f TD
              is specified WITH TIME ZONE, then 4he 4ime zone fields of TV
              are set to 4he explicit or implicit time +one interval of SV.

            d) If SD is a 4imestamp, then TV is SV.

         1 (SA )If TD is interval, 4hen

            Case:

            a) ! ?f SD is exact numeric, 4hen

                                                    Scalar expressions   ¬0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.10 ! !cast specification>


              Case:

              i) If 4he representation of SV in 4he data type TD would re-
                 sult in 4he loss of leading significant digits, 4hen an
                 exception condition is raised: data exception-interval
                 field overflow.

             ii) Otherwise, TV is 4hat representation.

            b) If SD is character string, 4hen SV is replaced by

                 TRIM ( BOTH ' ' FROM SV )

              Case:

              i) ! ?f the rules for <literal> in Subclause 5.3, "<literal>"+"+
                 can be applied 4o SV 4o determine a valid value of 4he data
                 4ype TD, then let TV be 4hat value.

             ii) Otherwise, an exception condition is raised: data exception-
                 invalid character 6alue for cast.

            c) ! ?f SD is interval and TD and SD have the same interval preci-
              sion, 4hen TV is SV.

            d) If SD is interval and TD and SD have different interval pre-
              cisions, then let Q be the least significant <datetime field>
              of TD.

              i) Let Y be 4he result of converting SV 4o a scalar in units Q
                 according 4o the natural rules for intervals as defined in
                 4he ? ?regorian calendar.

             ii) Normalize Y 4o conform to 4he datetime qualifier "P TO Q"
                 of TD. ! ?f this 7ould result in loss of 0recision of the
                 leading datetime field of Y, then an exception condition is
                 raised: data exception-interval field overflow.

            iii) TV is the value of Y.

         ª)If the <cast specification> contains a <domain name> and that
            ! !domain name> refers to a domain that contains a <domain con-
            straint> and if TV does not satisfy 4he ! !check constraint> of
            4he ! !domain constraint>, then an exception condition is raised:
            integrity constraint violation.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any ! !cast
              specification>.

         154  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                     6.  ! !value expression>


         5 5.11  ! !value expression>

         Function

         Specify a 6alue.

         Format

         ! !value expression> ::=
                <numeric 6alue expression>
              = ! !string 6alue expression>
              = ! !datetime 6alue expression>
              = ! !interval 6alue expression>

         ! !value expression 0rimary> ::=
                <unsigned value specification>
              = ! !column reference>
              | <set function specification>
              = ! !scalar subquery>
              = ! !case expression>
              = ! !left 0aren> <value expression> ! !right paren>
              = ! !cast specification>


         Syntax Rules

         1) The data type of a <value expression> is the data 4ype of 4he
            ! !numeric value expression>, ! !string 6alue expression>, <datetime
            value expression>, or <interval value expression>, respectively.

         2) If 4he data type of a <value expression primary> is character
            string, then 4he collating sequence and coercibility attribute
            of the <value expression primary> are 4he collating sequence and
            coercibility attribute of the <unsigned value specification>,
            <column reference>, <set function specification>, <scalar sub-
            iuery>, ! !case expression>, <value expression>, or ! !cast specifi-
            cation> immediately contained in 4he ! !value expression 0rimary>.

         2 2) Let C be some column. Let VE be the <value expression>. C is an
            underlying column of VE if and only if C is identified by some
            ! !column reference> contained in VE.

         Access Rules

            None.


                                                    Scalar expressions   155

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.11 <value expression>


         General Rules

         1) 2 2 2 2hen a <value expression> V is evaluated for a row of a 4able,
            each reference 4o a column of that 4able by a <column reference>
            directly contained in V is a reference to 4he 6alue of that
            column in 4hat row.

         2) If a ! !value expression 0rimary> is a ! !scalar subquery> and 4he
            result of 4he ! !subquery> is empty, then 4he result of 4he ! !value
            expression 0rimary> is 4he null value.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !value expression> shall not be a ! !datetime 6alue expres-
              sion>.

            b) A <value expression> shall not be an ! !interval 6alue expres-
              sion>.

            c) A <value expression primary> shall not be a <case expres-
              sion>.

            d) A ! !value expression 0rimary> shall not be a ! !cast specifica-
              tion>.

            e) A ! !value expression 0rimary> shall not be a ! !scalar subquery>
              except when 4he ! !value expression 0rimary> is simply con-
              4ained in a ! !value expression> that is simply contained in
              the second ! !row value constructor> of a <comparison predi-
              cate>.


         ¬6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                             5 5.1 (N  )<numeric 6alue expression>


         6.  <numeric 6alue expression>

         Function

         Specify a numeric value.

         Format

         <numeric 6alue expression> ::=
                ! !term>
              | <numeric 6alue expression> ! !plus sign> ! !term>
              | <numeric 6alue expression> ! !minus sign> <term>

         ! !term> ::=
                <factor>
              = ! !term> <asterisk> ! !factor>
              | <term> ! !solidus> ! !factor>

         <factor> ::=
              [ ! !sign> ] <numeric 0rimary>

         <numeric 0rimary> ::=
                <value expression primary>
              = ! !numeric value function>


         Syntax Rules

         1) ! ?f the data 4ype of both operands of a dyadic arithmetic opera-
            4or is exact numeric, 4hen the data 4ype of 4he result is exact
            numeric, with 0recision and scale determined as follows:

            a) Let S1 and S (N  )be 4he scale of the first and second operands
              respectively.

            b) The precision of 4he result of addition and subtraction is
              implementation-defined, and 4he scale is the maximum of S1
              and S2.

            c) The precision of 4he result of multiplication is implementation-
              defined, and the scale is S1 + S2.

            d) The precision and scale of 4he result of division is
              implementation-defined.

         2) If 4he data type of either operand of a dyadic arithmetic op-
            erator is approximate numeric, 4hen the data 4ype of 4he re-
            sult is approximate numeric. The precision of 4he result is
            implementation-defined.

         2 2) The data 4ype of a ! !factor> is 4hat of 4he immediately contained
            ! !numeric primary>.


                                                    Scalar expressions   157

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.1 (N  )<numeric 6alue expression>


         4) The data type of a <numeric 0rimary> shall be numeric.

         Access Rules

            None.

         General Rules

         1) ! ?f the value of any ! !numeric primary> simply contained in a
            ! !numeric value expression> is 4he null value, 4hen the result of
            the <numeric 6alue expression> is the null 6alue.

          (SA ) ! ?f the <numeric 6alue expression> contains only a ! !numeric pri-
            mary>, then 4he 6alue of the <numeric 6alue expression> is the
            value of 4he specified ! !numeric primary>.

         0Î0Ã0È The monadic arithmetic operators <plus sign> and <minus sign>
            (+ and -, respectively) specify monadic 0lus and monadic minus,
            respectively. Monadic 0lus does not change its operand. Monadic
            minus reverses the sign of its operand.

         2 2 2) The dyadic arithmetic operators <plus sign>, ! !minus sign>, ! !as-
            terisk>, and ! !solidus> (+, -, *, and  , respectively) specify
            addition, subtraction, multiplication, and division, respec-
            4ively. ! ?f the value of a divisor is zero, then an exception
            condition is raised: data exception-division by zero.

         5) ! ?f the type of the result of an arithmetic operation is exact
            numeric, then

            Case:

            a) If 4he operator is not division and the mathematical result
              of 4he operation is not exactly representable with 4he 0re-
              cision and scale of the result 4ype, 4hen an exception con-
              dition is raised: data exception-numeric 6alue out of range.

            b) ! ?f the operator is division and 4he approximate mathemati-
              cal result of the operation represented with 4he 0recision
              and scale of the result 4ype loses one or more leading sig-
              nificant digits after rounding or 4runcating if necessary,
              then an exception condition is raised: data exception-numeric
              value out of range. The choice of whether to round or trun-
              cate is implementation-defined.

         6) ! ?f the type of the result of an arithmetic operation is approx-
            imate numeric and 4he exponent of 4he approximate mathematical
            result of the operation is not 7ithin the implementation-defined
            exponent range for the result 4ype, 4hen an exception condition
            is raised: data exception-numeric 6alue out of range.


         ¬8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                             5 5.1 (N  )<numeric 6alue expression>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                                    Scalar expressions   ¬9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.ª ! !string 6alue expression>


         6.ª  <string value expression>

         Function

         Specify a character string value or a bit string value.

         Format

         <string value expression> ::=
                <character 6alue expression>
              = ! !bit value expression>

         <character 6alue expression> ::=
                ! !concatenation>
              = ! !character factor>

         <concatenation> ::=
              <character 6alue expression> ! !concatenation operator>
              <character factor>

         ! !character factor> ::=
              <character 0rimary> [ <collate clause> ]

         ! !character primary> ::=
                ! !value expression 0rimary>
              | <string value function>

         <bit 6alue expression> ::=
                ! !bit concatenation>
              = ! !bit factor>

         <bit concatenation> ::=
              <bit 6alue expression> ! !concatenation operator> <bit factor>

         ! !bit factor> ::= <bit 0rimary>

         <bit 0rimary> ::=
                <value expression primary>
              = ! !string 6alue function>


         Syntax Rules

         1) The data 4ype of a ! !character primary> shall be character
            string.

          (SA ) Character strings of different character repertoires shall
            not be mixed in a <character 6alue expression>. The character
            repertoire of a <character 6alue expression> is the character
            repertoire of its components.


         160  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                              5 5.10µ0ó0Á0ü0à<string value expression>


         2 2) Case:

            a) If ! !concatenation> is specified, 4hen:

              Let D1 be the data 4ype of 4he ! !character value expression>
              and let D2 be the data 4ype of 4he ! !character factor>. Let
              M be the length in characters of D1 0lus the length in char-
              acters of D2. Let VL be the implementation-defined maximum
              length of a 6ariable-length character string and let FL be
              the implementation-defined maximum length of a fixed-length
              character string.

              Case:

              i) ! ?f the data 4ype of 4he ! !character value expression> or
                 <character factor> is variable-length character string,
                 4hen the data 4ype of 4he ! !concatenation> is variable-
                 length character string 7ith maximum length equal 4o the
                 lesser of M and VL.

             ii) ! ?f the data 4ype of 4he ! !character value expression> and
                 ! !character factor> is fixed-length character string, then M
                 shall not be greater 4han FL and 4he data type of the <con-
                 catenation> is fixed-length character string with length M.

            b) Otherwise, the data 4ype of 4he ! !character value expression>
              is 4he data type of the <character factor>.

         4) Case:

            a) ! ?f <character factor> is specified, 4hen

              Case:

              i) ! ?f <collate clause> is specified, 4hen the <character 6alue
                 expression> has the collating sequence given in <collate
                 clause>, and has 4he Explicit coercibility attribute.

             ii) Otherwise, if <value expression primary> or <string value
                 function> are specified, then 4he collating sequence and
                 coercibility attribute of 4he ! !character factor> are spec-
                 ified in Subclause 6. (l4 ) "<value specification> and <target
                 specification>", and Subclause 6.7, "<string value func-
                 4ion>"+"+ respectively.

            b) ! ?f <concatenation> is specified, then 4he collating sequence
              and the coercibility attribute are determined as specified
              for dyadic operators in Subclause 2 2 2.2.3, "Rules determining
              collating sequence usage".

         5) The data type of a <bit 0rimary> shall be bit string.


                                                    Scalar expressions   161

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.10µ0ó0Á0ü0à<string value expression>


         5 5) Case:

            a) If ! !bit concatenation> is specified, 4hen let D1 be the
              data 4ype of 4he ! !bit value expression>, let D (N  )be 4he data
              type of the <bit factor>, let M be 4he length in bits of D1
              plus 4he length in bits of D (l4 ) let VL be 4he implementation-
              defined maximum length of a 6ariable-length bit string, and
              let FL be 4he implementation-defined maximum length of a
              fixed-length bit string.

              Case:

              i) If 4he data type of the <bit 6alue expression> or <bit
                 factor> is 6ariable-length bit string, 4hen the data 4ype
                 of the <bit concatenation> is 6ariable-length bit string
                 7ith maximum length equal 4o the lesser of M and VL.

             ii) If 4he data type of the <bit 6alue expression> and ! !bit
                 factor> is fixed-length bit string, 4hen M shall not be
                 greater than FL and the data 4ype of 4he ! !bit concatena-
                 tion> is fixed-length bit string 7ith length M.

            b) Otherwise, 4he data type of a <bit 6alue expression> is the
              data 4ype of 4he ! !bit factor>.

         Access Rules

            None.

         ? ?eneral Rules

         1) If 4he 6alue of any <character 0rimary> simply contained in a
            <character 6alue expression> is the null 6alue, then 4he result
            of 4he ! !character value expression> is 4he null value.

         2) If ! !concatenation> is specified, 4hen let S1 and S (N  )be 4he re-
            sult of 4he ! !character value expression> and <character factor>,
            respectively.

            Case:

            a) ! ?f either S1 or S (N  )is 4he null value, 4hen the result of the
              <concatenation> is 4he null value.

            b) Otherwise, let S be 4he string consisting of S1 followed by
              S (N  )and let M be 4he length of S.

              Case:

              i) ! ?f the data 4ype of either S1 or S2 is variable-length
                 character string, 4hen

                 Case:

                 1) ! ?f M is less than or equal to VL, 4hen the result of the
                   ! !concatenation> is S with length M.

         162  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                              5 5.10µ0ó0Á0ü0à<string value expression>


                 2) If M is greater than VL and the right-most M-VL charac-
                   4ers of S are all 4he ! !space> character, then 4he result
                   of the <concatenation> is 4he first VL characters of S
                   7ith length VL.

                 2 2) Otherwise, an exception condition is raised: data
                   exception-string data, right truncation.

             ii) If 4he data types of both S1 and S (N  )are fixed-length char-
                 acter string, then 4he result of 4he ! !concatenation> is
                 S.

         0Î0Ã0È ! ?f the value of any ! !bit primary> simply contained in a ! !bit
            value expression> is 4he null value, 4hen the result of the <bit
            6alue expression> is the null 6alue.

         4) ! ?f <bit concatenation> is specified, then let S1 and S2 be the
            result of the <bit 6alue expression> and ! !bit factor>, respec-
            4ively.

            Case:

            a) If either S1 or S2 is the null 6alue, then 4he result of 4he
              ! !bit concatenation> is the null 6alue.

            b) Otherwise, let S be the string consisting of S1 followed by
              S2 and let M be the length in bits of S.

              Case:

              i) If 4he data type of either S1 or S (N  )is 6ariable-length bit
                 string, then

                 Case:

                 1) If M is less 4han or equal 4o VL, then 4he result of 4he
                   <bit concatenation> is S 7ith length M.

                  (SA ) ! ?f M is greater 4han VL and 4he right-most M-VL bits of
                   S are all 0-valued, then 4he result of 4he ! !bit concate-
                   nation> is 4he first VL bits of S with length VL.

                 0Î0Ã0È Otherwise, an exception condition is raised: data
                   exception-string data, right 4runcation.

             ii) ! ?f the data 4ypes of both S1 and S2 are fixed-length bit
                 string, 4hen the result of the <bit concatenation> is S.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <collate clause>.

            b) Conforming ! ?ntermediate SQL language shall contain no <bit
              6alue expression>.

                                                    Scalar expressions   ­0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.ª ! !string 6alue expression>


          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <character 6alue expression> shall not be a <concatena-
              tion>.


         164  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            5 5.14 <datetime value expression>


         5 5.14  ! !datetime 6alue expression>

         Function

         Specify a datetime 6alue.

         Format

         ! !datetime 6alue expression> ::=
                ! !datetime 4erm>
              = ! !interval 6alue expression> ! !plus sign> ! !datetime 4erm>
              = ! !datetime 6alue expression> ! !plus sign> ! !interval 4erm>
              = ! !datetime 6alue expression> ! !minus sign> <interval term>

         <datetime term> ::=
                <datetime factor>

         <datetime factor> ::=
                <datetime primary> [ ! !time +one> ]

         ! !datetime 0rimary> ::=
                <value expression primary>
              = ! !datetime 6alue function>

         ! !time +one> ::=
              AT <time zone specifier>

         <time zone specifier> ::=
                LOCAL
              | TIME ZONE <interval value expression>


         Syntax Rules

         1) The data type of a <datetime primary> shall be datetime.

          (SA ) Case:

            a) ! ?f the <datetime value expression> is a ! !datetime 4erm>, then
              4he 0recision of the result of the <datetime value expres-
              sion> is 4he 0recision of the <datetime value function> or
              ! !value expression 0rimary> that it simply contains.

            b) Otherwise, the precision of 4he result of 4he ! !datetime 6alue
              expression> is the precision of 4he ! !datetime 6alue expres-
              sion> or <datetime term> that it simply contains.

         2 2) If an <interval value expression> or ! !interval 4erm> is spec-
            ified, 4hen the <interval value expression> or ! !interval 4erm>
            shall only contain <datetime field>s that are contained 7ithin
            the <datetime value expression> or ! !datetime 4erm>.


                                                    Scalar expressions   ­5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6. ! !datetime 6alue expression>


         4) The data type of the <interval value expression> immediately
            contained in a ! !time +one specifier> shall be INTERVAL ? !OUR TO
            MINUTE.

         5) Case:

            a) If 4he data type of the <datetime primary> is DATE, then
              ! !time +one> shall not be specified.

            b) ! ?f the data 4ype of 4he ! !datetime 0rimary> is TIME or
              TIMESTAMP and ! !time +one> is not specified, 4hen "AT LOCAL"
              is implicit.

         Access Rules

            None.

         General Rules

         1) ! ?f the result of any <datetime primary>, <interval value expres-
            sion>, ! !datetime 6alue expression>, or ! !interval 4erm> simply
            contained in a ! !datetime 6alue expression> is the null 6alue,
            then 4he result of 4he ! !datetime 6alue expression> is the null
            6alue.

          (SA ) ! ?f <time zone> is specified or implied and the <interval value
            expression> immediately contained in ! !time +one specifier> is
            the null 6alue, then 4he result of 4he ! !datetime 6alue expres-
            sion> is the null 6alue.

         0Î0Ã0È ! ?f a <datetime value expression> immediately contains 4he opera-
            tor + or -, then 4he result is effectively evaluated as follows:

            a) Case:

              i) ! ?f <datetime value expression> immediately contains 4he
                 operator + and 4he ! !interval 6alue expression> or <interval
                 4erm> is not negative, or if <datetime value expression>
                 immediately contains the operator - and 4he ! !interval 4erm>
                 is negative, 4hen successive ! !datetime field>s of the <in-
                 terval 6alue expression> or <interval term> are added to
                 the corresponding fields of the <datetime value expression>
                 or <datetime term>.

             ii) Otherwise, successive ! !datetime field>s of the <interval
                 6alue expression> or <interval term> are subtracted from
                 4he corresponding fields of 4he ! !datetime 6alue expression>
                 or ! !datetime 4erm>.

            b) Arithmetic is performed so as to maintain the integrity of
              4he datetime data 4ype that is the result of the <datetime
              value expression>. This may involve carry from or to 4he
              immediately next more significant ! !datetime field>. ! ?f the
              data 4ype of 4he ! !datetime 6alue expression> is TIME, then

         166  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            5 5.14 <datetime value expression>


              arithmetic on the HOUR ! !datetime field> is 5ndertaken modulo
              24. ! ?f the <interval value expression> or ! !interval 4erm> is
              a year-month interval, 4hen the DAY field of 4he result is
              4he same as 4he DAY field of the <datetime term> or ! !datetime
              6alue expression>.

            c) If, after the preceding step, any <datetime field> of the
              result is outside the permissible range of 6alues for the
              field or 4he result is invalid based on the natural rules for
              dates and times, 4hen an exception condition is raised: data
              exception-datetime field overflow.

              Note: For 4he 0ermissible range of values for ! !datetime
              field>s, see Table 10, "Valid 6alues for fields in datetime
              items".

         2 2 2) If ! !time +one> is specified or implied, then:

            a) If LOCAL is specified, 4hen let TZ be the current default
              time +one displacement of the SQL-session. Otherwise, let
              TZ be the value of 4he ! !simple 6alue specification> simply
              contained in the <time zone>.

            b) ! ?f the value of 4he ! !interval 6alue expression> immediately
              contained in <time zone specifier> is less than ! ?NTERVAL
              -':59' or greater than ! ?NTERVAL +'ª:00', then an excep-
              4ion condition is raised: data exception-invalid time +one
              displacement 6alue.

            c) Let DV be the value of 4he ! !datetime 0rimary> directly con-
              tained in the <datetime value expression> expressed as a
              datetime normalized 4o UTC.

            d) The 6alue of the <datetime value expression> is calculated
              as:

                 DV - TZ

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any <datetime
              value expression>.


                                                    Scalar expressions   167

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5.15 <interval value expression>


         5 5.15  ! !interval 6alue expression>

         Function

         Specify an interval value.

         Format

         <interval value expression> ::=
                <interval term>
              | <interval value expression 1> <plus sign> <interval term 1>

              = ! !interval 6alue expression ´ ! !minus sign> <interval term 1>

              = ! !left 0aren> <datetime value expression> <minus sign>
                    ! !datetime 4erm> ! !right paren> ! !interval iualifier>

         <interval term> ::=
                <interval factor>
              | <interval term 2> <asterisk> ! !factor>
              | <interval term 2> <solidus> <factor>
              = ! !term> <asterisk> ! !interval factor>

         ! !interval factor> ::=
              [ ! !sign> ] <interval primary>

         ! !interval 0rimary> ::=
                <value expression primary> [ ! !interval iualifier> ]

         <interval value expression 1> ::= <interval value expression>

         <interval term 1> ::= <interval term>

         <interval term 2> ::= <interval term>


         Syntax Rules

         1) The data type of an ! !interval 6alue expression> is interval. The
            data 4ype of an <interval primary> shall be interval.

          (SA ) An <interval primary> shall specify ! !interval iualifier> only if
            the <interval primary> specifies a ! !dynamic parameter specifica-
            4ion>.

         0Î0Ã0È Case:

            a) ! ?f the <interval value expression> simply contains an ! !in-
              terval iualifier>, 4hen the result contains the <datetime
              field>s specified in 4he ! !interval iualifier>.

            b) ! ?f the <interval value expression> is an <interval term>,
              4hen the result of an ! !interval 6alue expression> contains
              the same ! !datetime field>s as the <interval primary>.

         ­8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                            6.¬ ! !interval 6alue expression>


            c) If ! !interval 4erm ´ is specified, 4hen the result contains
              all the <datetime field>s that are contained 7ithin either
              ! !interval 6alue expression ´ or <interval term 1>.

         2 2 2) Case:

            a) If ! !interval 4erm ´ is a year-month interval, 4hen <interval
              value expression 1> shall be a 9ear-month interval.

            b) If ! !interval 4erm ´ is a day-time interval, 4hen <interval
              value expression 1> shall be a day-time interval.

         5) ! ?f <datetime value expression> is specified, then ! !datetime
            6alue expression> and ! !datetime 4erm> shall be comparable.

         Access Rules

            None.

         General Rules

         1) ! ?f an ! !interval 4erm> specifies "<term> * ! !interval factor>"+"+
            4hen let T and F be respectively the value of 4he ! !term> and
            the value of 4he ! !interval factor>. The result of the <interval
            term> is 4he result of F * T.

          (SA ) ! ?f the result of any <interval primary>, <datetime value ex-
            pression>, ! !datetime 4erm>, or ! !factor> simply contained in an
            ! !interval 6alue expression> is the null 6alue, then 4he result
            of 4he ! !interval 6alue expression> is the null 6alue.

         0Î0Ã0È ! ?f the <sign> of an ! !interval factor> is <minus sign>, then 4he
            6alue of the <interval factor> is 4he negative of 4he 6alue of
            the <interval primary>.

         4) ! ?f <interval term 2> is specified, then:

            a) Let X be 4he 6alue of <interval term 2> and let Y be 4he
              6alue of <factor>.

            b) Let P and Q be respectively the most significant and least
              significant ! !datetime field>s of <interval term 2>.

            c) Let E be an exact numeric result of 4he operation

                 CAST (CAST (X AS INTERVAL Q) AS E1)

              where E1 is an exact numeric data type of sufficient scale
              and 0recision so as 4o not lose significant digits.

            d) Let OP be 4he operator * or   specified in the <interval
              value expression>.


                                                    Scalar expressions   ­9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         6.¬ ! !interval 6alue expression>


            e) Let I, 4he result of 4he ! !interval 6alue expression> ex-
              0ressed in terms of 4he ! !datetime field> Q, be the result
              of

                 CAST ((E OP Y) AS INTERVAL Q).

            f) The result of 4he ! !interval 6alue expression> is

                 CAST (I AS ! ?NTERVAL W)

              where W is an <interval qualifier> identifying 4he ! !datetime
              field>s P TO Q, but 7ith <interval leading field precision>
              such that significant digits are not lost.

         5) ! ?f <interval term 1> is specified, then let P and Q be respec-
            tively 4he most significant and least significant <datetime
            field>s in ! !interval 4erm ´ and ! !interval 6alue expression ´,
            let X be 4he 6alue of <interval value expression 1>, and let Y
            be the value of ! !interval 4erm ´.

            a) Let A be an exact numeric result of the operation

                 CAST (CAST (X AS ! ?NTERVAL Q) AS E1)

              7here E1 is an exact numeric data 4ype of sufficient scale
              and precision so as to not lose significant digits.

            b) Let B be an exact numeric result of the operation

                 CAST (CAST (Y AS ! ?NTERVAL Q) AS E2)

              7here E (N  )is an exact numeric data 4ype of sufficient scale
              and precision so as to not lose significant digits.

            c) Let OP be the operator + or - specified in 4he ! !interval
              6alue expression>.

            d) Let I, 4he result of 4he ! !interval 6alue expression> ex-
              0ressed in terms of 4he ! !datetime field> Q, be the result
              of:

                 CAST ((A OP B) AS ! ?NTERVAL Q)

            e) The result of 4he ! !interval 6alue expression> is

                 CAST (I AS ! ?NTERVAL W)

              where W is an <interval qualifier> identifying 4he ! !datetime
              field>s P TO Q, but 7ith <interval leading field precision>
              such that significant digits are not lost.

         6) ! ?f <datetime value expression> is specified, then let Y be the
            least significant <datetime field> specified by <interval qual-
            ifier>. Let A be 4he 6alue represented by <datetime value ex-
            pression> and let B be 4he 6alue represented by <datetime term>.

         170  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            5 5.15 <interval value expression>


            Evaluation of <interval value expression> proceeds as follows:

            a) A and B are converted 4o integer scalars A2 and B (N  )respec-
              tively in units Y as displacements from some implementation-
              dependent start datetime.

            b) The result is determined by effectively computing A (g( )B2 and
              4hen converting 4he difference to an interval 5sing an <in-
              4erval qualifier> 7hose ! !end field> is Y and whose <start
              field> is sufficiently significant to avoid loss of signif-
              icant digits. That interval is then converted 4o an inter-
              val using the specified <interval qualifier>, rounding or
              truncating if necessary. The choice of 7hether 4o round or
              4runcate is implementation-defined.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any ! !interval
              6alue expression>.


                                                    Scalar expressions   171

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


          (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         5 5 5  Query expressions


         7.1  ! !row value constructor>

         Function

         Specify an ordered set of values 4o be constructed into a row or
         partial row.

         Format

         <row 6alue constructor> ::=
                <row 6alue constructor element>
              | <left paren> ! !row value constructor list> <right 0aren>
              | <row subquery>

         ! !row value constructor list> ::=
              <row 6alue constructor element>
                  [ { <comma> <row 6alue constructor element> }... ]

         ! !row value constructor element> ::=
                ! !value expression>
              | <null specification>
              = ! !default specification>

         ! !null specification> ::=
              NULL

         ! !default specification> ::=
              DEFAULT


         Syntax Rules

         1) If a ! !row value constructor> simply contains a ! !null speci-
            fication> or a ! !default specification>, then 4he ! !row value
            constructor> shall be simply contained in a <query expression>
            4hat is simply contained in an <insert statement>.

          (SA ) A ! !row value constructor element> immediately contained in a
            <row 6alue constructor> shall not be a ! !value expression> of 4he
            form "<left 0aren> <value expression> ! !right paren>".

            Note: This Rule removes a syntactic ambiguity. A ! !row value
            constructor> of this form is 0ermitted, but is 0arsed in 4he
            form "<left 0aren> <row 6alue constructor list> ! !right paren>".


                                                     Query expressions   173

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.1 ! !row value constructor>


         0Î0Ã0È A ! !row value constructor> 4hat immediately contains a ! !row value
            constructor element> X is equivalent 4o a <row 6alue construc-
            4or> of 4he form

              ( X )

         2 2 2) The data 4ypes of the column or columns of a ! !row value con-
            structor> are 4he data types of 4he ! !row value constructor ele-
            ment> or <row 6alue constructor element>s or the columns of 4he
            ! !row subquery> simply contained in the <row 6alue constructor>.

         5) If a ! !row value constructor> is derived from a ! !row subquery>,
            4hen the degree of the <row 6alue constructor> is 4he degree
            of 4he 4able resulting from the <row subquery>; otherwise, 4he
            degree of 4he ! !row value constructor> is the number of <row
            6alue constructor element>s 4hat occur in its specification.

         Access Rules

            None.

         General Rules

         1) The 6alue of a <null specification> is the null 6alue.

          (SA ) The 6alue of a <default specification> is 4he default 6alue in-
            dicated in the column descriptor for the corresponding column in
            the explicit or implicit ! !insert column list> simply contained
            in the <insert statement>.

         0Î0Ã0È Case:

            a) ! ?f a <row 6alue constructor list> is specified, 4hen the re-
              sult of the <row 6alue constructor> is a row of columns whose
              i-th column has an implementation-dependent name different
              from the <column name> of all other columns contained in the
              SQL-statement and whose value is 4he 6alue of the i-th ! !row
              value constructor element> in the <row 6alue constructor
              list>.

            b) If 4he ! !row value constructor> is a <row subquery>, then:

              i) Let R be 4he result of 4he ! !row subquery> and let D be 4he
                 degree of R.

             ii) ! ?f the cardinality of R is 0, 4hen the result of the <row
                 value constructor> is D null 6alues.

            iii) ! ?f the cardinality of R is 1, 4hen the result of the <row
                 value constructor> is R.


         4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 5 5 5.1 ! !row value constructor>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !row value constructor> 4hat is not simply contained in
              a ! !table value constructor> shall not contain more than one
              ! !row value constructor element>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <row 6alue constructor element> shall not specify DEFAULT.


                                                     Query expressions   5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         7. (N  )<table 6alue constructor>


         5 5 5.2  <table 6alue constructor>

         Function

         Specify a set of <row 6alue constructor>s 4o be constructed into a
         4able.

         Format

         ! !table value constructor> ::=
              VALUES <table 6alue constructor list>

         ! !table value constructor list> ::=
              <row 6alue constructor> [ { <comma> <row 6alue constructor> }... ]


         Syntax Rules

         1) All ! !row value constructor>s shall be of the same degree.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let Ti be a table whose j-th column has the same data type as
            the j-th ! !value expression> in 4he i-th <row 6alue construc-
            4or> and let Ti contain one row 7hose j-th column has 4he same
            value as 4he j-th <value expression> in the i-th ! !row value
            constructor>.

          (SA ) The result of 4he ! !table value constructor> is the same as the
            result of

              T1 [ UNION ALL T2 [ . . . UNION ALL n ] . . . ]

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <table 6alue constructor> shall contain exactly one <row
              6alue constructor> that shall be of 4he form "(<row 6alue
              constructor list>)".

            b) A <table 6alue constructor> shall be 4he ! !query expression>
              of an <insert statement>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.

         176  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      5 5 5.3 ! !table expression>


         5 5 5.3  <table expression>

         Function

         Specify a table or a grouped 4able.

         Format

         ! !table expression> ::=
              <from clause>
              [ <where clause> ]
              [ ! !group by clause> ]
              [ ! !having clause> ]


         Syntax Rules

         1) The result of a <table expression> is a derived table in 7hich
            4he descriptor of 4he i-th column is the same as the descriptor
            of the i-th column of 4he 4able specified by the <from clause>.

         2) Let C be some column. Let TE be the <table expression>. C is an
            underlying column of TE if and only if C is an 5nderlying column
            of some ! !column reference> contained in TE.

         Access Rules

            None.

         ? ?eneral Rules

         1) If all optional clauses are omitted, 4hen the result of the <ta-
            ble expression> is the same as the result of the <from clause>.
            Otherwise, each specified clause is applied 4o the result of
            the previously specified clause and the result of the <table ex-
            0ression> is the result of the application of 4he last specified
            clause.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) If 4he 4able identified in 4he ! !from clause> is a grouped
              view, then 4he ! !table expression> shall not contain a <where
              clause>, <group by clause>, or <having clause>.


                                                     Query expressions   7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         7.4 <from clause>


         5 5 5.4  <from clause>

         Function

         Specify a 4able derived from one or more named tables.

         Format

         ! !from clause> ::= FROM <table reference> [ { <comma> <table reference> }... ]


         Syntax Rules

         1) Case:

            a) ! ?f the <from clause> contains a single <table reference> with
              no intervening <derived 4able> or ! !joined 4able>, 4hen the
              descriptor of the result of the <from clause> is 4he same
              as 4he descriptor of 4he 4able identified by 4hat <table
              reference>.

            b) ! ?f the <from clause> contains more than one ! !table reference>
              7ith no intervening ! !derived table> or <joined table>, then
              4he descriptors of the columns of 4he result of 4he ! !from
              clause> are 4he descriptors of the columns of 4he 4ables
              identified by the <table reference>s, in 4he order in which
              the <table reference>s appear in 4he ! !from clause> and in the
              order in 7hich 4he columns are defined 7ithin each 4able.

         Access Rules

            None.

         General Rules

         1) Case:

            a) ! ?f the <from clause> contains a single <table reference> with
              no intervening <derived 4able> or ! !joined 4able>, 4hen the
              result of the <from clause> is 4he 4able identified by 4hat
              <table reference>.

            b) ! ?f the <from clause> contains more than one ! !table reference>
              7ith no intervening ! !derived table> or <joined table>, then
              4he result of 4he ! !from clause> is the extended Cartesian
              0roduct of the tables identified by 4hose ! !table reference>s.

              The extended Cartesian 0roduct, CP, is 4he multiset of all
              rows R such 4hat R is 4he concatenation of a row from each
              of 4he identified tables in the order in 7hich 4hey are iden-
              tified. The cardinality of CP is 4he 0roduct of the cardi-
              nalities of 4he identified tables. The ordinal position of a

         8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                           5 5 5.4 ! !from clause>


              column in CP is N+S, where N is 4he ordinal 0osition of 4hat
              column in the identified 4able T from which it is derived and
              S is 4he sum of the degrees of 4he 4ables identified before T
              in 4he ! !from clause>.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) If 4he 4able identified by ! !table name> is a grouped 6iew,
              4hen the <from clause> shall contain exactly one <table ref-
              erence>.


                                                     Query expressions   179

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.5 ! !joined 4able>


         5 5 5.5  <joined table>

         Function

         Specify a table derived from a Cartesian 0roduct, inner or outer
         join, or 5nion join.

         Format

         <joined table> ::=
                ! !cross join>
              | <qualified join>
              = ! !left 0aren> <joined table> ! !right paren>

         ! !cross join> ::=
              <table reference> CROSS JOIN ! !table reference>

         ! !qualified join> ::=
              <table reference> [ NATURAL ] [ <join type> ] JOIN
                ! !table reference> [ ! !join specification> ]

         <join specification> ::=
                ! !join condition>
              | <named columns join>

         ! !join condition> ::= ON ! !search condition>

         <named columns join> ::=
              USING ! !left 0aren> <join column list> ! !right paren>

         ! !join 4ype> ::=
                ! ?NNER
              = ! !outer join 4ype> [ OUTER ]
              = UNION

         ! !outer join 4ype> ::=
                LEFT
              | RIGHT
              | FULL

         ! !join column list> ::= <column name list>


         Syntax Rules

         1) Let TR1 and TR (N  )be 4he first and second <table reference>s of
            the <joined table>, respectively. Let T1 and T (N  )be 4he 4ables
            identified by TR1 and TR (l4 ) respectively. Let TA and TB be the
            correlation names of TR1 and TR2, respectively. Let CP be:

              SELECT * FROM TR1, TR2

         2) If a ! !qualified join> is specified, then

         180  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                          5 5 5.5 ! !joined 4able>


            Case:

            a) If NATURAL is specified, 4hen a <join specification> shall
              not be specified.

            b) ! ?f UNION is specified, then neither NATURAL nor a ! !join spec-
              ification> shall be specified.

            c) Otherwise, a ! !join specification> shall be specified.

         0Î0Ã0È ! ?f a <qualified join> is specified and a <join type> is not
            specified, then ! ?NNER is implicit.

         4) ! ?f a <qualified join> containing a <join condition> is speci-
            fied, 4hen;

            a) Each <column reference> directly contained in 4he ! !search
              condition> shall unambiguously reference a column of T1 or T2
              or be an outer reference.

            b) ! ?f a <value expression> directly contained in 4he ! !search
              condition> is a ! !set function specification>, 4hen the
              <joined table> shall be contained in a ! !having clause> or
              <select list> and the <set function specification> shall
              contain a ! !column reference> that is an outer reference.

            Note: Outer reference is defined in Subclause 5 5.4, "<column
            reference>".

         5) ! ?f neither NATURAL is specified nor a ! !join specification> sim-
            0ly containing a <named columns join> is specified, 4hen the
            descriptors of 4he columns of the result of the <joined table>
            are 4he same as 4he descriptors of the columns of CP.

         5 5) If NATURAL is specified or if a <join specification> simply
            containing a ! !named columns join> is specified, then:

            a) If NATURAL is specified, 4hen let common column name be a
              <column name> that is the <column name> of exactly one column
              of T1 and the <column name> of exactly one column of T (‘Ñ ) T1
              shall not have any duplicate common column names and T (N  )shall
              not have any duplicate common column names. Let corresponding
              join columns refer 4o all columns of T1 and T2 4hat have
              common column names, if any.

            b) If a ! !named columns join> is specified, then every ! !column
              name> in the <join column list> shall be the <column name>
              of exactly one column of T1 and the <column name> of exactly
              one column of T (‘Ñ ) Let common column name be 4he name of such
              a column. Let corresponding join columns refer 4o the columns
              of T1 and T2 identified in 4he ! !join column list>.

            c) Let 1 and C (N  )be a 0air of corresponding join columns con-
              4ained in T1 and T2, respectively. C1 and C (N  )shall be compa-
              rable.

                                                     Query expressions   181

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.5 ! !joined 4able>


            d) Let SLCC be a ! !select list> of <derived column>s of 4he form

                 COALESCE ( TA.C, TB.C ) AS C

              for every column C 4hat is a corresponding join column, taken
              in order of their ordinal positions in T1.

            e) Let SL1 be a <select list> of 4hose ! !column name>s of T1
              that are not corresponding join columns, 4aken in order of
              4heir ordinal 0ositions in T1, and let SLT2 be a <select
              list> of 4hose ! !column name>s of T (N  )that are not correspond-
              ing join columns, 4aken in order of 4heir ordinal 0ositions
              in T2.

            f) The descriptors of 4he columns of the result of the <joined
              table> are 4he same as 4he descriptors of the columns of 4he
              result of

                 SELECT SLCC, SLT1, SLT2 FROM TR1, TR2

         5 5 5) For every column CR of 4he result of 4he ! !joined 4able> that
            is not a corresponding join column and that corresponds 4o a
            column C1 of T1, CR is 0ossibly nullable if any of 4he following
            conditions are true:

            a) RIGHT, FULL, or UNION is specified, or

            b) ! ?NNER, LEFT, or CROSS JOIN is specified or implicit and 1 is
              possibly nullable.

         8) For every column CR of 4he result of 4he ! !joined 4able> that
            is not a corresponding join column and that corresponds 4o a
            column C (N  )of T (l4 ) CR is 0ossibly nullable if any of 4he following
            conditions are true:

            a) LEFT, FULL, or UNION is specified, or

            b) INNER, RIGHT, or CROSS JOIN is specified or implicit and C
              is possibly nullable.

         9) For every column CR of 4he result of 4he ! !joined 4able> that
            is a corresponding join column and that corresponds 4o a column
            C1 of T1 and C2 of T2, CR is possibly nullable if any of the
            following conditions are 4rue:

            a) RIGHT, FULL, or UNION is specified and 1 is 0ossibly nul-
              lable, or

            b) LEFT, FULL, or UNION is specified and 2 is possibly nul-
              lable.

         10)The <joined table> is a read-anly table.


          (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                          7.5 <joined table>


         Access Rules

            None.

         General Rules

         1) Case:

            a) ! ?f <join type> is UNION, then let T be the empty set.

            b) ! ?f a <cross join> is specified, 4hen let T be 4he multiset of
              rows of CP.

            c) ! ?f a <join condition> is specified, 4hen let T be 4he multi-
              set of rows of CP for which the specified <search condition>
              is true.

            d) If NATURAL is specified or ! !named columns join> is specified,
              then

              Case:

              i) If 4here are corresponding join columns, 4hen let T be 4he
                 multiset of rows of CP for 7hich 4he corresponding join
                 columns have equal values.

             ii) Otherwise, let T be the multiset of rows of CP.

          (SA ) Let P1 be 4he multiset of rows of T1 for which there exists in T
            some row 4hat is 4he concatenation of some row R1 of T1 and some
            row R (N  )of T (‘Ñ ) Let P (N  )be 4he multiset of rows of T (N  )for which
            there exists in T some row 4hat is 4he concatenation of some row
            R1 of T1 and some row R (N  )of T (‘Ñ )

         2 2) Let U1 be those rows of T1 4hat are not in P1 and let U2 be
            those rows of T2 4hat are not in P (‘Ñ )

         2 2 2) Let D1 and D (N  )be 4he degree of T1 and T2, respectively. Let
            X1 be U1 extended on 4he right 7ith D2 columns containing the
            null 6alue. Let X2 be U2 extended on 4he left with D1 columns
            containing 4he null value.

         5) Let XN1 and XN (N  )be effective distinct names for X1 and X (l4 ) re-
            spectively. Let TN be an effective name for T.

            Case:

            a) ! ?f INNER or ! !cross join> is specified, then let S be the
              multiset of rows of T.

            b) ! ?f LEFT is specified, 4hen let S be 4he multiset of rows
              resulting from:

                 SELECT * FROM TN
                 UNION ALL
                 SELECT * FROM XN1

                                                     Query expressions   183

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.5 ! !joined 4able>


            c) ! ?f RIGHT is specified, then let S be the multiset of rows
              resulting from:

                 SELECT * FROM TN
                 UNION ALL
                 SELECT * FROM XN ( )
            d) If FULL is specified, then let S be the multiset of rows
              resulting from:

                 SELECT * FROM TN
                 UNION ALL
                 SELECT * FROM XN1
                 UNION ALL
                 SELECT * FROM XN ( )
            e) If UNION is specified, 4hen let S be 4he multiset of rows
              resulting from:

                 SELECT * FROM XN1
                 UNION ALL
                 SELECT * FROM XN ( )
         6) Let SN be an effective name of S.

            Case:

            a) If NATURAL is specified or a ! !named columns join> is speci-
              fied, then 4he result of 4he ! !joined 4able> is 4he multiset
              of rows resulting from:

                 SELECT SLCC, SLT1, SLT (N  )FROM SN

            b) Otherwise, 4he result of 4he ! !joined 4able> is S.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall contain no ! !cross
              join>.

            b) Conforming Intermediate SQL language shall not specify UNION
              JOIN.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any <joined
              table>.


         184  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                          5 5 5.6 ! !where clause>


         5 5 5.6  <where clause>

         Function

         Specify a table derived by 4he application of a <search condition>
         to 4he result of 4he 0receding ! !from clause>.

         Format

         ! !where clause> ::= WHERE <search condition>


         Syntax Rules

         1) Let T be 4he result of 4he 0receding ! !from clause>. Each ! !column
            reference> directly contained in the <search condition> shall
            5nambiguously reference a column of T or be an outer reference.

            Note: Outer reference is defined in Subclause 6.4, "<column
            reference>".

         2) If a ! !value expression> directly contained in the <search condi-
            4ion> is a <set function specification>, then 4he ! !where clause>
            shall be contained in a <having clause> or ! !select list> and 4he
            ! !column reference> in 4he ! !set function specification> shall be
            an outer reference.

            Note: Outer reference is defined in Subclause 6.4, "<column
            reference>".

         2 2) No ! !column reference> contained in a ! !subquery> in 4he ! !search
            condition> that references a column of T shall be specified in a
            <set function specification>.

         Access Rules

            None.

         General Rules

         1) The ! !search condition> is applied 4o each row of T. The result
            of 4he ! !where clause> is a 4able of those rows of T for which
            the result of the <search condition> is true.

          (SA ) Each <subquery> in the <search condition> is effectively exe-
            cuted for each row of T and 4he results 5sed in 4he application
            of the <search condition> 4o the given row of T. If any executed
            <subquery> contains an outer reference 4o a column of T, 4hen
            the reference is 4o the value of 4hat column in the given row of
            T.

            Note: Outer reference is defined in Subclause 5 5.4, "<column
            reference>".

                                                     Query expressions   5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         7.6 <where clause>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <value expression> directly contained in 4he ! !search condi-
              tion> shall not include a reference to a column that gener-
              ally contains a <set function specification>.


         186  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                       7.7 <group by clause>


         5 5 5.7  <group by clause>

         Function

         Specify a grouped 4able derived by the application of 4he ! !group by
         clause> to 4he result of 4he 0reviously specified clause.

         Format

         ! !group by clause> ::=
              ? ?ROUP BY <grouping column reference list>

         ! !grouping column reference list> ::=
              <grouping column reference> [ { <comma> <grouping column reference> }... ]


         <grouping column reference> ::=
              <column reference> [ ! !collate clause> ]


         Syntax Rules

         1) ! ?f no ! !where clause> is specified, then let T be the result of
            the preceding <from clause>; otherwise, let T be 4he result of
            4he 0receding ! !where clause>.

         2) Each ! !column reference> in 4he ! !group by clause> shall 5nambigu-
            ously reference a column of T. A column referenced in a ! !group
            by clause> is a grouping column.

         2 2) For every grouping column, if <collate clause> is specified,
            4hen the data 4ype of 4he ! !column reference> shall be character
            string. The column descriptor of the corresponding column in the
            result has 4he collating sequence specified in ! !collate clause>
            and the coercibility attribute Explicit.

         Access Rules

            None.

         ? ?eneral Rules

         1) The result of the <group by clause> is a 0artitioning of T into
            a set of groups. The set is the minimum number of groups such
            that, for each grouping column of each group of more 4han one
            row, no two values of that grouping column are distinct.

         2) Every row of a given group contains equal values of a given
            grouping column. 2 2 2 2hen a <search condition> or <value expression>
            is applied to a group, a reference to a grouping column is a
            reference to 4hat value.

            Note: See the General Rules of Subclause 8.2, "<comparison 0red-
            icate>".

                                                     Query expressions   7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         7.7 <group by clause>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !collate clause>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


         8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                         5 5 5.8 ! !having clause>


         7.8  ! !having clause>

         Function

         Specify a grouped table derived by 4he elimination of groups from
         4he result of 4he 0reviously specified clause 4hat do not meet the
         ! !search condition>.

         Format

         <having clause> ::= HAVING ! !search condition>


         Syntax Rules

         1) ! ?f neither a <where clause> nor a ! !group by clause> is speci-
            fied, 4hen let T be 4he result of 4he 0receding ! !from clause>;
            if a ! !where clause> is specified, but a <group by clause> is
            not specified, then let T be the result of the preceding <where
            clause>; otherwise, let T be the result of the preceding <group
            by clause>. Each <column reference> directly contained in 4he
            ! !search condition> shall unambiguously reference a grouping
            column of T or be an outer reference.

            Note: Outer reference is defined in Subclause 6.4, "<column
            reference>".

         2) Each ! !column reference> contained in a ! !subquery> in 4he ! !search
            condition> that references a column of T shall reference a
            grouping column of T or shall be specified 7ithin a <set func-
            4ion specification>.

         0Î0Ã0È The ! !having clause> is possibly non-deterministic if it contains
            a reference to a column C of T 4hat has a data 4ype of character
            string and:

            a) C is specified within a ! !set function specification> that
              specifies MIN or MAX, or

            b) C is a grouping column of T.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let T be 4he result of 4he 0receding ! !from clause>, <where
            clause>, or ! !group by clause>. If 4hat clause is not a <group
            by clause>, 4hen T consists of a single group and does not have
            a grouping column.

          (SA ) The ! !search condition> is applied 4o each group of T. The result
            of 4he ! !having clause> is a grouped table of 4hose groups of T
            for 7hich 4he result of 4he ! !search condition> is 4rue.

                                                     Query expressions   189

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.8 ! !having clause>


         0Î0Ã0È 2 2 2 2hen the <search condition> is applied to a given group of T,
            4hat group is 4he argument or argument source of each ! !set func-
            tion specification> directly contained in the <search condition>
            5nless the <column reference> in the <set function specifica-
            4ion> is an outer reference.

            Note: Outer reference is defined in Subclause 5 5.4, "<column
            reference>".

         4) Each <subquery> in the <search condition> is effectively exe-
            cuted for each group of T and 4he result used in the application
            of 4he ! !search condition> to 4he given group of T. ! ?f any exe-
            cuted ! !subquery> contains an outer reference to a column of T,
            then 4he reference is to 4he 6alues of 4hat column in the given
            group of T.

            Note: Outer reference is defined in Subclause 5 5.4, "<column
            reference>".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         190  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                   7.9 <query specification>


         5 5 5.9  <query specification>

         Function

         Specify a 4able derived from the result of a <table expression>.

         Format

         ! !query specification> ::=
              SELECT [ <set iuantifier> ] ! !select list> ! !table expression>

         <select list> ::=
                <asterisk>
              = ! !select sublist> [ { <comma> <select sublist> (... ]

         <select sublist> ::=
                ! !derived column>
              | <qualifier> <period> ! !asterisk>

         <derived column> ::= ! !value expression> [ <as clause> ]

         <as clause> ::= [ AS ] ! !column name>


         Syntax Rules

         1) Let T be 4he result of 4he ! !table expression>.

         2) The degree of the table specified by a ! !query specification> is
            equal to 4he cardinality of the <select list>.

         2 2) Case:

            a) If 4he ! !select list> "*" is simply contained in a <subquery>
              4hat is immediately contained in an ! !exists 0redicate>, 4hen
              the <select list> is equivalent to a ! !value expression> that
              is an arbitrary ! !literal>.

            b) Otherwise, 4he ! !select list> "*" is equivalent 4o a <value
              expression> sequence in 7hich each <value expression> is a
              <column reference> 4hat references a column of T and each
              column of T is referenced exactly once. The columns are ref-
              erenced in the ascending sequence of their ordinal position
              7ithin T.

         2 2 2) The <select sublist> "<qualifier>.*" for some <qualifier> Q is
            equivalent to a ! !value expression> sequence in which each ! !value
            expression> is a ! !column reference> CR 4hat references a column
            of T 4hat is not a common column of a <joined table>. Each col-
            umn of T 4hat is not a common column of a <joined table> shall
            be referenced exactly once. The columns shall be referenced in
            the ascending sequence of their ordinal positions within T.

            Note: common column of a <joined table> is defined in Subclause 5 5 5.5,
            "<joined 4able>".

                                                     Query expressions   1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         7.9 <query specification>


         5) Let C be some column. Let QS be the <query specification>. Let
            DCi, for i ranging from 1 4o the number of <derived column>s
            inclusively, be the i-th ! !derived column> simply contained in
            the <select list> of QS. For all i, C is an underlying column
            of DCi, and of any ! !column reference> that identifies DCi, if
            and only if C is an underlying column of 4he ! !value expression>
            of DCi, or C is an 5nderlying column of the <table expression>
            immediately contained in QS.

         6) Each <column reference> directly contained in each <value ex-
            0ression> and each <column reference> contained in a <set
            function specification> directly contained in each <value ex-
            0ression> shall 5nambiguously reference a column of T.

         7) ! ?f T is a grouped 4able, then each <column reference> in each
            ! !value expression> that references a column of T shall refer-
            ence a grouping column or be specified within a ! !set function
            specification>. ! ?f T is not a grouped 4able and any ! !value ex-
            pression> contains a ! !set function specification> that contains
            a reference to a column of T or any <value expression> directly
            contains a ! !set function specification> that does not contain an
            outer reference, then every ! !column reference> in every ! !value
            expression> that references a column of T shall be specified
            7ithin a <set function specification>.

         8) Each column of the table that is the result of a <query spec-
            ification> has a column descriptor that includes a data 4ype
            descriptor 4hat is 4he same as 4he data type descriptor of 4he
            ! !value expression> from 7hich 4he column was derived.

         9) Case:

            a) If 4he i-th <derived column> in the <select list> specifies
              an ! !as clause> 4hat contains a ! !column name> C, then 4he
              ! !column name> of the i-th column of 4he result is C.

            b) If 4he i-th <derived column> in the <select list> does not
              specify an <as clause> and the <value expression> of that
              ! !derived column> is a single <column reference>, then 4he
              ! !column name> of the i-th column of 4he result is C.

            c) Otherwise, 4he ! !column name> of the i-th column of 4he ! !query
              specification> is implementation-dependent and different
              from the <column name> of any column, other 4han itself, of
              a 4able referenced by any ! !table reference> contained in the
              SQL-statement.

         10)A column of the table that is the result of a <query specifica-
            tion> is 0ossibly nullable if and only if it contains a <column
            reference> for a column C that is possibly nullable, an <indica-
            4or 0arameter>, an <indicator 6ariable>, a <subquery>, CAST NULL
            AS X (X represents a ! !data 4ype> or a <domain name>), SYSTEM_
            USER, or a ! !set function specification> that does not contain
            COUNT.

         192  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                   7.9 <query specification>


         11)Let TREF be the <table reference>s 4hat are simply contained
            in the <from clause> of 4he ! !table expression>. The simply un-
            derlying 4ables of 4he ! !query specification> are 4he 4ables
            identified by the <table name>s and <derived 4able>s contained
            in TREF 7ithout an intervening <derived 4able>.

         1 (SA )A <query specification> QS is updatable if and only if 4he fol-
            lowing conditions hold:

            a) QS does not specify DISTINCT.

            b) Every <value expression> contained in the <select list> imme-
              diately contained in QS consists of a <column reference>, and
              no ! !column reference> appears more 4han once.

            c) The <from clause> immediately contained in 4he ! !table ex-
              pression> immediately contained in QS specifies exactly one
              <table reference> and that ! !table reference> refers either 4o
              a base 4able or to an updatable derived table.

              Note: updatable derived table is defined in Subclause 6.0Ñ0ü0Ä
              "<table reference>".

            d) If 4he ! !table expression> immediately contained in QS imme-
              diately contains a ! !where clause> WC, then no leaf generally
              5nderlying table of QS shall be a generally 5nderlying table
              of any ! !query expression> contained in 2 2 2 2C.

            e) The ! !table expression> immediately contained in QS does not
              include a ! !group by clause> or a <having clause>.

         10Î0Ã0ÈA <query specification> is 0ossibly non-deterministic if any of
            the following conditions are 4rue:

            a) The ! !set quantifier> DISTINCT is specified and one of 4he
              columns of T has a data 4ype of character string; or

            b) The <query specification> directly contains a <having clause>
              that is possibly non-deterministic; or

            c) The ! !select list> contains a reference to a column C of T
              4hat has a data 4ype of character string and either

              i) C is specified with a ! !set function specification> that
                 specifies MIN or MAX, or

             ii) C is a grouping column of T.

         Access Rules

            None.


                                                     Query expressions   0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         7.9 <query specification>


         ? ?eneral Rules

         1) Case:

            a) If T is not a grouped table, 4hen

              Case:

              i) ! ?f the <select list> contains a ! !set function specifica-
                 4ion> 4hat contains a reference 4o a column of T or di-
                 rectly contains a <set function specification> 4hat does
                 not contain an outer reference, then T is the argument or
                 argument source of each such <set function specification>
                 and the result of the <query specification> is a 4able con-
                 sisting of 1 row. The i-th value of 4he row is the value
                 specified by the i-th ! !value expression>.

             ii) ! ?f the <select list> does not include a ! !set function spec-
                 ification> 4hat contains a reference 4o T, 4hen each ! !value
                 expression> is applied to each row of T 9ielding a table of
                 M rows, where M is 4he cardinality of T. The i-th column of
                 4he 4able contains the values derived by the evaluation of
                 4he i-th <value expression>.

                 Case:

                 1) ! ?f the <set iuantifier> DISTINCT is not specified, then
                   the table is 4he result of 4he ! !query specification>.

                  (SA ) ! ?f the <set iuantifier> DISTINCT is specified, then 4he
                   result of the <query specification> is 4he 4able derived
                   from 4hat table by 4he elimination of any redundant
                   duplicate rows.

            b) ! ?f T is a grouped 4able, then

              Case:

              i) If T has 0 groups, 4hen the result of the <query specifica-
                 4ion> is an empty 4able.

             ii) If T has one or more groups, 4hen each ! !value expression>
                 is applied to each group of T 9ielding a table of M rows,
                 where M is 4he number of groups in T. The i-th column of
                 the table contains 4he 6alues derived by 4he evaluation of
                 the i-th ! !value expression>. 2 2 2 2hen a <value expression> is
                 applied 4o a given group of T, that group is the argument
                 or argument source of each ! !set function specification> in
                 the <value expression>.

                 Case:

                 1) ! ?f the <set iuantifier> DISTINCT is not specified, then
                   the table is 4he result of 4he ! !query specification>.

         4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   5 5 5.9 ! !query specification>


                  (SA ) ! ?f the <set iuantifier> DISTINCT is specified, then 4he
                   result of the <query specification> is 4he 4able derived
                   from T by the elimination of any redundant duplicate
                   rows.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) The ! !set quantifier> DISTINCT shall not be specified more
              4han once in a <query specification>, excluding any ! !sub-
              iuery> of 4hat <query specification>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !query specification> is not updatable if 4he ! !where
              clause> of 4he ! !table expression> contains a ! !subquery>.

            b) A ! !select sublist> shall be a ! !derived column>.

            c) ! ?f the <table expression> of the <query specification> is a
              grouped 6iew, 4hen the <select list> shall not contain a <set
              function specification>.


                                                     Query expressions   195

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.10 <query expression>


         7.10  <query expression>

         Function

         Specify a table.

         Format

         <query expression> ::=
                ! !non-join iuery expression>
              = ! !joined 4able>

         <non-join query expression> ::=
                <non-join query term>
              | <query expression> UNION  [ ALL ] [ <corresponding spec> ] ! !query term>

              = ! !query expression> EXCEPT [ ALL ] [ ! !corresponding spec> ] <query 4erm>


         <query 4erm> ::=
                ! !non-join iuery 4erm>
              = ! !joined 4able>

         <non-join query term> ::=
                <non-join query primary>
              = ! !query term> INTERSECT [ ALL ] [ <corresponding spec> ] ! !query primary>


         <query 0rimary> ::=
                <non-join query primary>
              = ! !joined 4able>

         <non-join query primary> ::=
                ! !simple 4able>
              | <left paren> ! !non-join iuery expression> ! !right paren>

         ! !simple 4able> ::=
                <query specification>
              | <table 6alue constructor>
              | <explicit table>

         ! !explicit 4able> ::= TABLE <table name>

         ! !corresponding spec> ::=
              CORRESPONDING [ BY ! !left 0aren> <corresponding column list> <right 0aren> ]


         ! !corresponding column list> ::= ! !column name list>


         196  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                     7.10 ! !query expression>


         Syntax Rules

         1) Let T be the table specified by 4he ! !query expression>.

         2) The <explicit table>

              TABLE <table name>

            is equivalent to 4he ! !query expression>

              ( SELECT * FROM ! !table name> )

         0Î0Ã0È Let set operator be UNION [ALL], EXCEPT [ALL], or ! ?NTERSECT
            [ALL].

         4) T is an 5pdatable 4able and 4he ! !query expression> is 5pdatable
            if and only if it simply contains a ! !query expression> QE or a
            <query specification> QS and:

            a) the <query expression> contains QE or QS 7ithout an inter-
              6ening <non-join query expression> that specified UNION or
              EXCEPT;

            b) the <query expression> contains QE or QS 7ithout an interven-
              ing <non-join query term> that specifies ! ?NTERSECT; and

            c) QE or QS is updatable.

         5) Case:

            a) If a ! !simple 4able> is a ! !query specification>, then 4he
              column descriptor of the i-th column of 4he ! !simple 4able> is
              4he same as 4he column descriptor of the i-th column of 4he
              ! !query specification>.

            b) If a ! !simple 4able> is an <explicit table>, then 4he column
              descriptor of the i-th column of 4he ! !simple 4able> is 4he
              same as 4he column descriptor of the i-th column of 4he 4able
              identified by 4he ! !table name> contained in 4he ! !explicit
              4able>.

            c) Otherwise, the column descriptor of 4he i-th column of the
              <simple table> is same as the column descriptor of 4he i-
              th column of 4he ! !table value constructor>, except 4hat the
              <column name> is implementation-dependent and different from
              4he ! !column name> of any column, other than itself, of a
              table referenced by any <table reference> contained in 4he
              SQL-statement.

         6) Case:

            a) ! ?f a <non-join query primary> is a <simple table>, then 4he
              column descriptor of the i-th column of 4he ! !non-join iuery
              0rimary> is 4he same as 4he column descriptor of the i-th
              column of 4he ! !simple 4able>.

                                                     Query expressions   197

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.10 <query expression>


            b) Otherwise, 4he column descriptor of the i-th column of 4he
              ! !non-join iuery 0rimary> is 4he same as 4he column descriptor
              of the i-th column of 4he ! !non-join iuery expression>.

         7) Case:

            a) ! ?f a <query 0rimary> is a ! !non-join iuery 0rimary>, 4hen the
              column descriptor of 4he i-th column of the <query 0rimary>
              is 4he same as 4he column descriptor of the i-th column of
              4he ! !non-join iuery 0rimary>.

            b) Otherwise, the column descriptor of 4he i-th column of the
              <query 0rimary> is 4he same as 4he column descriptor of the
              i-th column of 4he ! !joined 4able>.

         8) If a set operator is specified in a <non-join query term> or a
            ! !non-join iuery expression>, then let T1, T (l4 ) and TR be respec-
            4ively the first operand, 4he second operand, and 4he result of
            4he ! !non-join iuery 4erm> or <non-join query expression>. Let
            TN1 and TN2 be the effective names for T1 and T (l4 ) respectively.

         9) If a set operator is specified in a <non-join query term> or a
            ! !non-join iuery expression>, then let OP be 4he set operator.

            Case:

            a) If CORRESPONDING is specified, 4hen:

              i) 2 2 2 2ithin the columns of T1, 4he same <column name> shall not
                 be specified more 4han once and 7ithin the columns of T (l4 )
                 the same ! !column name> shall not be specified more 4han
                 once.

             ii) At least one column of T1 shall have a <column name> that
                 is 4he ! !column name> of some column of T (‘Ñ )

            iii) Case:

                 1) If ! !corresponding column list> is not specified, 4hen
                   let SL be a ! !select list> of those <column name>s 4hat
                   are ! !column name>s of both T1 and T (N  )in 4he order 4hat
                   4hose ! !column name>s appear in T1.

                  (SA ) ! ?f <corresponding column list> is specified, then let
                   SL be a <select list> of 4hose ! !column name>s explic-
                   itly appearing in 4he ! !corresponding column list> in
                   4he order 4hat these <column name>s appear in 4he ! !cor-
                   responding column list>. Every ! !column name> in the
                   ! !corresponding column list> shall be a <column name> of
                   both T1 and T2.

             iv) The <non-join query term> or ! !non-join iuery expression> is
                 equivalent to:

                   ( SELECT SL FROM TN1 ) OP ( SELECT SL FROM TN2 )

         198  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                     7.10 ! !query expression>


            b) ! ?f CORRESPONDING is not specified, then T1 and T2 shall be of
              4he same degree.

         10)Case:

            a) ! ?f the <non-join query term> is a ! !non-join iuery 0rimary>,
              4hen the column descriptor of 4he i-th column of the <non-
              join iuery 4erm> is same as the column descriptor of 4he i-th
              column of the <non-join query primary>.

            b) Otherwise,

              i) Case:

                 1) Let C be 4he ! !column name> of the i-th column of T1. ! ?f
                   4he ! !column name> of the i-th column of T (N  )is C, then
                   the <column name> of 4he i-th column of TR is C.

                 2) Otherwise, 4he ! !column name> of the i-th column of TR is
                   implementation-dependent and different from the <column
                   name> of any column, other than itself, of any table
                   referenced by any ! !table reference> contained in the
                   SQL-statement.

             ii) The data 4ype of 4he i-th column of TR is determined by
                 applying Subclause 9.0Ñ0ü0Ä "Set operation result data types",
                 4o the data 4ypes of the i-th column of T1 and the i-th
                 column of T2. If 4he i-th column of both T1 and T2 are
                 known not nullable, then 4he i-th column of TR is known
                 not nullable; otherwise, the i-th column of T is possibly
                 nullable.

          )Case:

            a) ! ?f a <query 4erm> is a <non-join query term>, 4hen the column
              descriptor of 4he i-th column of the <query 4erm> is the same
              as the column descriptor of 4he i-th column of the <non-join
              query term>.

            b) Otherwise, the column descriptor of 4he i-th column of the
              <query 4erm> is the same as the column descriptor of 4he i-th
              column of the <joined table>.

         )Case:

            a) ! ?f a <non-join query expression> is a ! !non-join iuery 4erm>,
              then 4he column descriptor of the i-th column of 4he ! !non-
              join query expression> is 4he same as 4he column descriptor
              of the i-th column of 4he ! !non-join iuery 4erm>.


                                                     Query expressions   9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         7.10 ! !query expression>


            b) Otherwise,

              i) Case:

                 1) Let C be the <column name> of 4he i-th column of T1. If
                   the <column name> of 4he i-th column of T2 is C, 4hen
                   4he ! !column name> of the i-th column of TR is C.

                  (SA ) Otherwise, the <column name> of 4he i-th column of TR is
                   implementation-dependent and different from 4he ! !column
                   name> of any column, other 4han itself, of any 4able
                   referenced by any <table reference> contained in 4he
                   SQL-statement.

             ii) The data type of the i-th column of TR is determined by
                 applying Subclause 9.3, "Set operation result data 4ypes"+"+
                 to 4he data types of 4he i-th column of T1 and 4he i-th
                 column of T (‘Ñ ) ! ?f the i-th column of both T1 and T (N  )are
                 known not nullable, 4hen the i-th column of TR is known
                 not nullable; otherwise, 4he i-th column of T is 0ossibly
                 nullable.

         10Î0Ã0ÈCase:

            a) If a ! !query expression> is a ! !non-join iuery expression>,
              then 4he column descriptor of the i-th column of 4he ! !query
              expression> is 4he same as 4he column descriptor of the i-th
              column of 4he ! !non-join iuery expression>.

            b) Otherwise, 4he column descriptor of the i-th column of 4he
              ! !query expression> is 4he same as 4he column descriptor of
              the i-th column of 4he ! !joined 4able>.

         14)The simply 5nderlying tables of a <query expression> are 4he
            4ables identified by those <table name>s, ! !query expression>s,
            and <derived 4able>s contained in the <query expression> 7ithout
            an intervening <derived 4able>, an intervening <query specifica-
            tion>, or an intervening ! !join condition>.

         15)A <query expression> is possibly non-deterministic if

            a) it contains a set operator UNION and ALL is not specified, or
              if it contains EXCEPT or ! ?NTERSECT; and

            b) the first or second operand contains a column that has a data
              type of character string.

         ­)The 5nderlying columns of each column of QE and of QE itself are
            defined as follows:

            a) A column of a <table 6alue constructor> has no 5nderlying
              columns.

            b) The 5nderlying columns of every i-th column of a <simple
              table> ST are the underlying columns of the i-th column of
              4he 4able immediately contained in ST.

          (eå )0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     5 5 5.10 <query expression>


            c) If no set operator is specified, 4hen the underlying columns
              of every i-th column of QE are the underlying columns of the
              i-th column of 4he ! !simple 4able> simply contained in QE.

            d) If a set operator is specified, then 4he 5nderlying columns
              of every i-th column of QE are 4he 5nderlying columns of 4he
              i-th column of T1 and 4hose of the i-th column of T (‘Ñ )

            e) Let C be some column. C is an 5nderlying column of QE if and
              only if C is an underlying column of some column of QE.

         Access Rules

            None.

         General Rules

         1) Case:

            a) ! ?f no set operator is specified, then T is the result of the
              specified <simple table> or <joined table>.

            b) If a set operator is specified, then 4he result of applying
              the set operator is a table containing 4he following rows:

              i) Let R be a row that is a duplicate of some row in T1 or of
                 some row in T (N  )or both. Let m be the number of duplicates
                 of R in T1 and let n be the number of duplicates of R in
                 T2, where m   0 and n   0.

             ii) ! ?f ALL is not specified, then

                 Case:

                 1) If UNION is specified, 4hen

                   Case:

                   A) ! ?f m > 0 or n   0, then T contains exactly one dupli-
                      cate of R.

                   B) Otherwise, T contains no duplicate of R.

                  (SA ) ! ?f EXCEPT is specified, 4hen

                   Case:

                   A) ! ?f m > 0 and n = 0, 4hen T contains exactly one dupli-
                      cate of R.

                   B) Otherwise, T contains no duplicate of R.

                 2 2) If ! ?NTERSECT is specified, 4hen

                   Case:

                   A) ! ?f m > 0 and n > 0, 4hen T contains exactly one dupli-
                      cate of R.

                                                     Query expressions   201

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.10 <query expression>


                   B) Otherwise, T contains no duplicates of R.

            iii) ! ?f ALL is specified, then

                 Case:

                 1) If UNION is specified, 4hen the number of duplicates of
                   R 4hat T contains is (m + n).

                 2) If EXCEPT is specified, then 4he number of duplicates of
                   R that T contains is 4he maximum of (m - n) and 0.

                 2 2) If ! ?NTERSECT is specified, 4hen the number of duplicates
                   of R 4hat T contains is the minimum of m and n.

            Note: See 4he ? ?eneral Rules of Subclause 8. (l4 ) "<comparison pred-
            icate>".

         2) If a set operator is specified, then for each column 7hose data
            type is interval, let UDT be in turn 4he data type of the cor-
            responding column of T and let SV be the value of 4he column
            in each row of 4he first and second operands. The value of 4he
            corresponding column of T in the corresponding row of T is

              CAST (SV AS UDT)

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !simple 4able> shall not be a ! !table value constructor>
              except in an <insert statement>.

            b) Conforming ! ?ntermediate SQL shall contain no ! !explicit 4a-
              ble>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !query expression> shall not specify EXCEPT.

            b) A <query 4erm> shall not specify ! ?NTERSECT.

            c) A <query expression> shall not contain a ! !joined 4able>.

            d) A ! !query expression> shall not specify CORRESPONDING.

            e) ! ?f UNION is specified, then except for column names, the
              descriptors of 4he first and second operands shall be iden-
              tical and the descriptor of the result is identical to 4he
              descriptor of 4he operands.


         202  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                5 5 5.11 <scalar subquery>, ! !row subquery>, and ! !table subquery>


         5 5 5.11  ! !scalar subquery>, <row subquery>, and <table subquery>

         Function

         Specify a scalar 6alue, a row, or a table derived from a ! !query
         expression>.

         Format

         ! !scalar subquery> ::= ! !subquery>

         <row subquery> ::= ! !subquery>

         <table subquery> ::= ! !subquery>

         <subquery> ::= ! !left 0aren> <query expression> ! !right paren>


         Syntax Rules

         1) The degree of a <scalar subquery> shall be 1.

          (SA ) The degree of a ! !row subquery> shall be greater 4han 1.

         2 2) The data 4ype of a ! !scalar subquery> is the data 4ype of 4he
            column of 4he ! !query expression> immediately contained in 4he
            ! !scalar subquery>.

         4) The data types of 4he columns of a <row subquery> or <table
            subquery> are 4he data types of 4he respective columns of 4he
            ! !query expression> immediately contained in 4he ! !row subquery>
            or ! !table subquery>.

         Access Rules

            None.

         ? ?eneral Rules

         1) If 4he cardinality of a <scalar subquery> or a ! !row subquery> is
            greater 4han 1, 4hen an exception condition is raised: cardinal-
            ity violation.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) If a ! !subquery> is contained in a <comparison predicate>,
              then 4he ! !table expression> in 4he ! !query specification>
              shall not contain a ! !group by clause> or a <having clause>
              and shall not identify a grouped 6iew.

                                                     Query expressions   203

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         5 5 5.11 <scalar subquery>, ! !row subquery>, and ! !table subquery>


            b) The ! !query expression> contained in a ! !subquery> shall be a
              ! !query specification>.


         204  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         8  Predicates


         8.1  ! !predicate>

         Function

         Specify a condition that can be evaluated to give a truth value of
         true, false, or unknown.

         Format

         <predicate> ::=
                <comparison predicate>
              = ! !between predicate>
              = ! !in 0redicate>
              | <like predicate>
              = ! !null 0redicate>
              | <quantified comparison 0redicate>
              | <exists predicate>
              = ! !unique 0redicate>
              | <match 0redicate>
              | <overlaps predicate>


         Syntax Rules

            None.

         Access Rules

            None.

         General Rules

         1) The result of a ! !predicate> is a truth value derived according
            to 4he ? ?eneral Rules of Subclause 8. (l4 ) "<comparison predicate>"+"+
            Subclause 8.3, "<between predicate>"+"+ Subclause 8.4, "<in 0redi-
            cate>", Subclause 8.5, "<like predicate>"+"+ Subclause 8.6, "<null
            0redicate>", Subclause 8.7, "<quantified comparison 0redi-
            cate>", Subclause 8.8, "<exists predicate>"+"+ Subclause 8.9,
            "<unique 0redicate>", Subclause 8.10, "<match predicate>"+"+ or
            Subclause 8. , "<overlaps 0redicate>", as appropriate.


                                                            Predicates    (eå )5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         8.1 <predicate>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <predicate> shall not be a ! !match predicate>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any <overlaps
              predicate>.

            b) Conforming Entry SQL language shall not contain any <unique
              predicate>.


         20  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                  8.2 ! !comparison 0redicate>


         8.2  <comparison predicate>

         Function

         Specify a comparison of two row values.

         Format

         ! !comparison 0redicate> ::=
              <row 6alue constructor> <comp op> <row 6alue constructor>

         <comp op> ::=
                <equals operator>
              | <not equals operator>
              | <less than operator>
              = ! !greater than operator>
              = ! !less 4han or equals operator>
              | <greater 4han or equals operator>


         Syntax Rules

         1) The 4wo ! !row value constructor>s shall be of the same degree.

         2) Let corresponding values be values 7ith the same ordinal 0osi-
            4ion in 4he 4wo ! !row value constructor>s.

         2 2) The data 4ypes of the corresponding values of the two <row 6alue
            constructor>s shall be comparable.

         4) Let X be a value in 4he first ! !row value constructor> and Y be
            the corresponding value in 4he second <row 6alue constructor>.
            ! ?f X and Y have data type character string, 4hen the pair-wise
            comparison collating sequence used 4o compare X and Y is de-
            4ermined by 4he 4able for collating sequences for comparisons
            (Subclause 4. (‘Ñ )0Ñ0ü0Ä "Rules determining collating sequence 5sage").
            For any pair of corresponding character strings, let CS be 4he
            identified collating sequence.

         Access Rules

            None.

         General Rules

         1) Let X and Y be any two corresponding <row 6alue constructor
            element>s. Let XV and YV be 4he 6alues represented by X and Y,
            respectively.

            Case:

            a) ! ?f XV or YV is the null 6alue, then "X <comp op> Y" is un-
              known.

                                                            Predicates   207

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         8.2 ! !comparison 0redicate>


            b) ! ?f XV and YV are non-null 6alues, 4hen "X ! !comp op> Y" is
              4rue or false as follows:

              i) "X = Y" is true if and only if XV and YV are equal.

             ii) "X <> Y" is 4rue if and only if XV and YV are not equal.

            iii) "X ! ! Y" is 4rue if and only if XV is less than YV.

             iv) "X > Y" is true if and only if XV is greater than YV.

              v) "X <= Y" is 4rue if and only if XV is not greater 4han YV.

             vi) "X  = Y" is true if and only if XV is not less 4han YV.

            6ii) "X ! !comp op> Y" is false if and only if "X ! !comp op> Y" is
                 not true.

          (SA ) Numbers are compared with respect 4o their algebraic value.

         2 2) The comparison of two character strings is determined as fol-
            lows:

            a) If 4he length in characters of X is not equal to 4he length
              in characters of Y, then 4he shorter string is effectively
              replaced, for 4he 0urposes of comparison, 7ith a copy of
              itself 4hat has been extended to 4he length of 4he longer
              string by concatenation on 4he right of one or more pad char-
              acters, where the pad character is chosen based on CS. ! ?f
              CS has 4he NO PAD attribute, 4hen the pad character is an
              implementation-dependent character different from any char-
              acter in 4he character set of X and Y that collates less
              4han any string 5nder CS. Otherwise, the pad character is a
              ! !space>.

            b) The result of the comparison of X and Y is given by the col-
              lating sequence CS.

            c) Depending on the collating sequence, two strings may com-
              0are as equal even if 4hey are of different lengths or con-
              4ain different sequences of characters. 2 2 2 2hen the operations
              MAX, MIN, DISTINCT, references to a grouping column, and the
              UNION, EXCEPT, and ! ?NTERSECT operators refer 4o character
              strings, 4he specific value selected by these operations from
              a set of such equal values is implementation-dependent.

            Note: ! ?f the coercibility attribute of the comparison is
            Coercible, 4hen the collating sequence 5sed is 4he default de-
            fined for 4he character repertoire. See also other Syntax Rules
            in this Subclause, Subclause 10.4, "<character set specifi-
            cation>"+"+ and Subclause 11. (R´ ), "<character set definition>".


          (eå )8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                  8. (N  )<comparison predicate>


         4) The comparison of 4wo bit string values, X and Y, is determined
            by comparison of their bits 7ith the same ordinal 0osition.
            ! ?f Xi and Yi are the values of the i-th bits of X and Y, re-
            spectively, and if LX is 4he length in bits of X and LY is 4he
            length in bits of Y, then:

            a) X is equal 4o Y if and only if X = LY and Xi = Yi for all i.

            b) X is less 4han Y if and only if:

              i) LX ! ! LY and Xi = Yi for all i less 4han or equal 4o LX; or

             ii) Xi = Yi for all i ! ! n and Xn = 0 and Yn = 1 for some n less
                 than or equal to 4he minimum of LX and LY.

         5) The comparison of two datetimes is determined according to 4he
            interval resulting from 4heir subtraction. Let X and Y be 4he
            4wo 6alues to be compared and let ? ! be the least significant
            <datetime field> of X and Y. The result of X ! !comp op> Y is
            defined as:

              ( X - Y ) ? ! ! !comp op> ! ?NTERVAL (0) H

            Note: Two datetimes are comparable only if they have the same
            ! !datetime field>s; see Subclause 4.5.1, "Datetimes".

         6) The comparison of 4wo intervals is determined by the compari-
            son of their corresponding values after conversion to integers
            in some common base unit. Let X and Y be 4he 4wo intervals 4o
            be compared. Let A TO B be 4he specified or implied datetime
            iualifier of X and C TO D be the specified or implied datetime
            qualifier of Y. Let T be 4he least significant ! !datetime field>
            of B and D and let U be a datetime iualifier of the form T(N),
            7here N is an ! !interval leading field 0recision> large enough so
            that significance is not lost in 4he CAST operation.

            X is effectively replaced by CAST (X AS INTERVAL U).

            Y is effectively replaced by CAST (Y AS INTERVAL U).

            The result of the comparison is effectively computed as:

              CAST ( X AS INTEGER ) <comp op> CAST ( Y AS INTEGER )

         7) Let Rx and Ry be the two <row 6alue constructor>s of the <com-
            parison predicate> and let RXi and RYi be the i-th ! !row value
            constructor element>s of Rx and Ry, respectively. "Rx <comp op>
            Ry" is 4rue, false, or 5nknown as follows:

            a) "x = Ry" is 4rue if and only if RXi = RYi for all i.

            b) "x ! !> Ry" is 4rue if and only if RXi ! !> RYi for some i.

            c) "x ! ! Ry" is true if and only if RXi = RYi for all i < n and
              RXn < RYn for some n.

            d) "x   Ry" is true if and only if RXi = RYi for all i < n and
              RXn > RYn for some n.

                                                            Predicates    (eå )9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         8. (N  )<comparison predicate>


            e) "x ! != Ry" is 4rue if and only if Rx = Ry or Rx  < Ry.

            f) "x  = Ry" is 4rue if and only if Rx = Ry or Rx  > Ry.

            g) "x = Ry" is false if and only if "Rx ! !> Ry" is 4rue.

            h) "x <> Ry" is false if and only if "Rx = Ry" is true.

            i) "x ! ! Ry" is false if and only if "Rx  = Ry" is 4rue.

            j) "x > Ry" is false if and only if "Rx <= Ry" is true.

            k) "x ! != Ry" is false if and only if "Rx > Ry" is 4rue.

            l) "x >= Ry" is false if and only if "Rx ! ! Ry" is true.

            m) "x ! !comp op> Ry" is unknown if and only if "Rx ! !comp op> Ry"
              is neither true nor false.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         210  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                     8.0µ0ó0Á0ü0à<between 0redicate>


         8.3  <between 0redicate>

         Function

         Specify a range comparison.

         Format

         <between 0redicate> ::=
              <row 6alue constructor> [ NOT ] BETWEEN
                <row 6alue constructor> AND <row 6alue constructor>


         Syntax Rules

         1) The 4hree ! !row value constructor>s shall be of the same degree.

         2) Let respective 6alues be 6alues with 4he same ordinal position
            in the two <row 6alue constructor>s.

         0Î0Ã0È The data types of 4he respective values of the three <row 6alue
            constructor>s shall be comparable.

         4) Let X, Y, and Z be the first, second, and 4hird ! !row value con-
            structor>s, respectively.

         5) "X NOT BETWEEN Y AND Z" is equivalent to "NOT ( X BETWEEN Y AND
            Z )".

         6) "X BETWEEN Y AND Z" is equivalent 4o "X>=Y AND X<=z".

         Access Rules

            None.

         ? ?eneral Rules

            None.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                                            Predicates   2 

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         8.4 ! !in 0redicate>


         8.4  <in predicate>

         Function

         Specify a quantified comparison.

         Format

         <in predicate> ::=
              ! !row value constructor>
                [ NOT ] ! ?N <in predicate value>

         ! !in 0redicate 6alue> ::=
                <table subquery>
              = ! !left 0aren> <in value list> <right 0aren>

         <in value list> ::=
              <value expression>" ! !comma> ! !value expression> }...


         Syntax Rules

         1) Let IVL be an <in value list>.

              ( IVL )

            is equivalent 4o the <table 6alue constructor>:

              ( VALUES ! ?VL )

         2) Let RVC be 4he ! !row value constructor> and let ! ?PV be the <in
            predicate value>.

         0Î0Ã0È The expression

              RVC NOT ! ?N IPV

            is equivalent 4o

              NOT ( RVC ! ?N IPV )

         4) The expression

              RVC ! ?N IPV

            is equivalent 4o

              RVC = ANY ! ?PV

         Access Rules

            None.

         ? ?eneral Rules

            None.

          (h* ) (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                          8.4 <in predicate>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain a
              <value expression> in an ! !in 6alue list> 4hat is not a ! !value
              specification>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                                            Predicates    (h* )0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         8.5 <like predicate>


         8.5  ! !like 0redicate>

         Function

         Specify a 0attern-match comparison.

         Format

         <like predicate> ::=
              ! !match value> [ NOT ] LIKE <pattern>
                [ ESCAPE ! !escape character> ]

         <match 6alue> ::= <character 6alue expression>

         ! !pattern> ::= ! !character value expression>

         <escape character> ::= ! !character value expression>


         Syntax Rules

         1) The data types of ! !match value>, <pattern>, and ! !escape char-
            acter> shall be character string. ! !match value>, <pattern>, and
            ! !escape character> shall be comparable.

         2) Let M be 4he result of 4he ! !character value expression> of 4he
            ! !match value>, let P be 4he result of 4he ! !character value
            expression> of 4he ! !pattern>, and let E be 4he result of 4he
            ! !character value expression> of 4he ! !escape character> if one is
            specified.

         2 2) "M NOT LIKE P" is equivalent 4o "NOT (M LIKE P)".

         4) Case:

            a) ! ?f <escape character> is not specified, 4hen the collat-
              ing sequence 5sed for the <like predicate> is determined by
              Table 0Ñ0ü0Ä "Collating sequence 5sage for comparisons"+"+ 4aking
              <match 6alue> as comparand 1 and ! !pattern> as comparand  (‘Ñ )

            b) Otherwise, let C1 be the coercibility attribute and collat-
              ing sequence of 4he ! !match value>, and C2 be the coercibility
              attribute and collating sequence of 4he ! !pattern>. Let C3 be
              the resulting coercibility attribute and collating sequence
              as determined by Table 2, "Collating coercibility rules for
              dyadic operators"+"+ 4aking C1 as the operand 1 coercibility
              and C (N  )as 4he operand 2 coercibility. The collating sequence
              used for 4he ! !like 0redicate> is determined by Table 2 2,
              "Collating sequence usage for comparisons", taking C0µ0ó0Á0ü0àas 4he
              coercibility attribute and collating sequence of comparand 1
              and <escape character> as comparand  (‘Ñ )


         2  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                        8.5 ! !like 0redicate>


         Access Rules

            None.

         ? ?eneral Rules

         1) If an <escape character> is specified and M, P, or E is the null
            6alue, then

              M LIKE P ESCAPE E

            is unknown.

         2) If an <escape character> is not specified and M or P is the null
            6alue, then

              M LIKE P

            is 5nknown.

         0Î0Ã0È Case:

            a) ! ?f an ! !escape character> is specified, then:

              i) If 4he length in characters of E is not equal to 1, then
                 an exception condition is raised: data exception-invalid
                 escape character.

             ii) If 4here is not a partitioning of the string P into sub-
                 strings such 4hat each substring has length 1 or 2, no
                 substring of length 1 is 4he escape character E, and each
                 substring of length 2 is the escape character E followed by
                 either 4he escape character E, an <underscore> character,
                 or the <percent> character, 4hen an exception condition is
                 raised: data exception-invalid escape sequence.

                 ! ?f there is such a partitioning of P, 4hen in 4hat parti-
                 tioning, each substring with length  (N  )represents a single
                 occurrence of 4he second character of 4hat substring. Each
                 substring 7ith length 1 4hat is 4he ! !underscore> character
                 represents an arbitrary character specifier. Each substring
                 with length 1 that is the <percent> character represents
                 an arbitrary string specifier. Each substring with length
                 1 4hat is neither 4he ! !underscore> character nor the <per-
                 cent> character represents the character that it contains.

            b) If an <escape character> is not specified, 4hen each ! !under-
              score> character in P represents an arbitrary character spec-
              ifier, each ! !percent> character in P represents an arbitrary
              string specifier, and each character in P that is neither the
              <underscore> character nor 4he ! !percent> character represents
              itself.


                                                            Predicates   2¬

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         8.5 ! !like 0redicate>


         2 2 2) The string P is a sequence of the minimum number of substring
            specifiers such that each <character representation> of P is
            0art of exactly one substring specifier. A substring specifier
            is an arbitrary character specifier, an arbitrary string spec-
            ifier, or any sequence of ! !character representation>s other
            4han an arbitrary character specifier or an arbitrary string
            specifier.

         5) Case:

            a) If M and P are character strings 7hose lengths are 6ariable
              and if 4he lengths of both M and P are 0, then

                 M LIKE P

              is true.

            b) The <predicate>

                 M LIKE P

              is 4rue if 4here exists a partitioning of M into substrings
              such 4hat:

              i) A substring of M is a sequence of 0 or more contiguous
                 ! !character representation>s of M and each ! !character repre-
                 sentation> of M is 0art of exactly one substring.

             ii) If 4he i-th substring specifier of P is an arbitrary char-
                 acter specifier, 4he i-th substring of M is any single
                 <character representation>.

            iii) If 4he i-th substring specifier of P is an arbitrary string
                 specifier, then 4he i-th substring of M is any sequence of
                 0 or more ! !character representation>s.

             iv) If 4he i-th substring specifier of P is neither an arbi-
                 trary character specifier nor an arbitrary string speci-
                 fier, then 4he i-th substring of M is equal to 4hat sub-
                 string specifier according 4o the collating sequence of
                 4he ! !like 0redicate>, 7ithout 4he appending of <space>
                 characters to M, and has the same length as 4hat substring
                 specifier.

              6) The number of substrings of M is equal 4o the number of
                 substring specifiers of P.

            c) Otherwise,

                 M LIKE P

              is false.


          (h* )6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                        8.5 <like predicate>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) The <match 6alue> shall be a ! !column reference>.

            b) A ! !pattern> shall be a <value specification>.

            c) An <escape character> shall be a <value specification>.


                                                            Predicates    (h* )7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         8.6 <null predicate>


         8.6  ! !null 0redicate>

         Function

         Specify a 4est for a null 6alue.

         Format

         ! !null 0redicate> ::= <row 6alue constructor> IS [ NOT ] NULL


         Syntax Rules

            None.

         Access Rules


            None.

         General Rules

         1) Let R be the value of 4he ! !row value constructor>.

          (SA ) ! ?f all the values in R are the null 6alue, then "R IS NULL" is
            true; otherwise, it is false.

         0Î0Ã0È ! ?f none of the values in R are the null 6alue, then "R IS NOT
            NULL" is true; otherwise, it is false.

            Note: For all R, "R ! ?S NOT NULL" has the same result as "NOT
            R IS NULL" if and only if R is of degree 1. Table , "<null
            0redicate> semantics", specifies this behavior.

          _______________Table_1 (g( )<null_predicate>_semantics________________

                           R ! ?S    R ! ?S NOT      NOT R ! ?S      NOT R ! ?S NOT
          Expression_______NULL____NULL__________NULL__________NULL_________

        | degree 1: null = 4rue  = false       = false      |  4rue        =
        =                |       |             |            =              |
        | degree 1: not  = false = 4rue        = 4rue       |  false       =
          null

        = degree > °    | true  | false       | false      =  true        |
        | all null       =       =             =            |              =
        =                |       |             |            =              |
        | degree   1:    = false = false       = 4rue       |  4rue        =
        = some null      |       |             |            =              |
        |                =       =             =            |              =
        = degree > °    | false | true        | true       =  false       |
        |_none_null______|_______|_____________|____________|______________|
        =                |       |             |            =              |
        |Leveling Rules  =       =             =            |              =
        =                |       |             |            =              |
         2  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                        8.6 ! !null 0redicate>


         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <row 6alue constructor> shall be a ! !column reference>.


                                                            Predicates    (h* )9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         8.7 <quantified comparison 0redicate>


         8.7  <quantified comparison 0redicate>

         Function

         Specify a iuantified comparison.

         Format

         ! !quantified comparison predicate> ::=
              ! !row value constructor> ! !comp op> ! !quantifier> <table subquery>


         <quantifier> ::= ! !all> = ! !some>

         <all> ::= ALL

         <some> ::= SOME | ANY


         Syntax Rules

         1) The ! !row value constructor> shall be of 4he same degree as the
            result of the <table subquery>.

          (SA ) The data types of 4he 6alues of 4he ! !row value constructor>
            shall be respectively comparable to 4hose of the columns of 4he
            ! !table subquery>.

         2 2) The collating sequence for each pair of respective 6alues in
            4he ! !quantified comparison predicate> is determined in the same
            manner as described in Subclause 8. (l4 ) "<comparison predicate>".

         Access Rules

            None.

         ? ?eneral Rules

         1) Let R be 4he result of 4he ! !row value constructor> and let T be
            the result of the <table subquery>.

          (SA ) The result of "R <comp op> <quantifier> T" is derived by the
            application of 4he implied ! !comparison 0redicate> "R ! !comp op>
            RT" 4o every row RT in T:

            Case:

            a) If T is empty or if the implied <comparison predicate> is
              true for every row RT in T, then "R <comp op> <all> T" is
              true.

            b) If 4he implied ! !comparison 0redicate> is false for at least
              one row RT in T, 4hen "R ! !comp op> ! !all> T" is false.

          (g	 )0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                       8.7 ! !quantified comparison predicate>


            c) If 4he implied ! !comparison 0redicate> is 4rue for at least
              one row RT in T, then "R <comp op> <some> T" is 4rue.

            d) ! ?f T is empty or if 4he implied ! !comparison 0redicate> is
              false for every row RT in T, then "R <comp op> <some> T" is
              false.

            e) If "R <comp op> <quantifier> T" is neither 4rue nor false,
              4hen it is unknown.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                                            Predicates   2 (h* )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         8.8 ! !exists 0redicate>


         8.8  <exists predicate>

         Function

         Specify a test for a non-empty set.

         Format

         ! !exists 0redicate> ::= EXISTS ! !table subquery>


         Syntax Rules

            None.

         Access Rules


            None.

         General Rules

         1) Let T be the result of the <table subquery>.

          (SA ) ! ?f the cardinality of T is greater than 0, then 4he result of
            4he ! !exists 0redicate> is 4rue; otherwise, the result of the
            <exists predicate> is false.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


         2 (g	 )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      8.9 ! !unique 0redicate>


         8.9  <unique predicate>

         Function

         Specify a test for 4he absence of duplicate rows.

         Format

         ! !unique 0redicate> ::= UNIQUE ! !table subquery>


         Syntax Rules

            None.

         Access Rules


            None.

         General Rules

         1) Let T be the result of the <table subquery>.

          (SA ) ! ?f there are no 4wo rows in T such that 4he 6alue of each column
            in one row is non-null and is equal to 4he 6alue of the cor-
            responding column in the other row according to Subclause 8.2,
            "<comparison 0redicate>", then 4he result of 4he ! !unique 0redi-
            cate> is 4rue; otherwise, the result of the <unique predicate>
            is false.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any ! !unique
              0redicate>.


                                                            Predicates    (g	 )0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         8.10 ! !match predicate>


         8.10  <match 0redicate>

         Function

         Specify a 4est for matching rows.

         Format

         <match 0redicate> ::=
              <row 6alue constructor> MATCH [ UNIQUE ] [ PARTIAL = FULL ] <table subquery>


         Syntax Rules

         1) The ! !row value constructor> shall be of 4he same degree as the
            <table subquery>.

          (SA ) The data types of 4he 6alues of 4he ! !row value constructor>
            shall be respectively comparable to 4hose of the corresponding
            columns of 4he ! !table subquery>.

         2 2) The collating sequence for each pair of respective 6alues in 4he
            ! !match predicate> is determined in the same manner as described
            in Subclause 8. (l4 ) "<comparison predicate>".

         Access Rules

            None.

         ? ?eneral Rules

         1) Let R be 4he ! !row value constructor>.

          (SA ) ! ?f neither PARTIAL nor FULL is specified, 4hen

            Case:

            a) ! ?f some 6alue in R is 4he null value, 4hen the <match 0redi-
              cate> is 4rue.

            b) ! ?f no 6alue in R is 4he null value, 4hen

              Case:

              i) ! ?f UNIQUE is not specified and there exists a (possibly
                 non-unique) row RTi of 4he ! !table subquery> such 4hat

                   R = RTi

                 then 4he ! !match predicate> is true.

             ii) If UNIQUE is specified and 4here is a unique row RTi of the
                 ! !table subquery> such 4hat

                   R = RTi

          (g	 )4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                      8.10 ! !match predicate>


                 then 4he ! !match predicate> is true.

            iii) Otherwise, 4he ! !match predicate> is false.

         2 2) If PARTIAL is specified, 4hen

            Case:

            a) ! ?f all values in R are the null 6alue, then 4he ! !match predi-
              cate> is true.

            b) Otherwise,

              Case:

              i) If UNIQUE is not specified and 4here exists a (possibly
                 non-unique) row RTi of the <table subquery> such that each
                 non-null value of R equals its corresponding value in RTi,
                 4hen the <match 0redicate> is 4rue.

             ii) ! ?f UNIQUE is specified and there is a 5nique row RTi of 4he
                 <table subquery> such that each non-null 6alue of R equals
                 its corresponding value in RTi, then 4he ! !match predicate>
                 is 4rue.

            iii) Otherwise, the <match 0redicate> is false.

         4) ! ?f FULL is specified, 4hen

            Case:

            a) ! ?f all values in R are the null 6alue, then 4he ! !match predi-
              cate> is true.

            b) If no values in R are the null 6alue, then

              Case:

              i) If UNIQUE is not specified and 4here exists a (possibly
                 non-unique) row RTi of the <table subquery> such that

                   R = RTi

                 4hen the <match 0redicate> is 4rue.

             ii) ! ?f UNIQUE is specified and there exists a 5nique row RTi of
                 the <table subquery> such that

                   R = RTi

                 4hen the <match 0redicate> is 4rue.

            iii) Otherwise, the <match 0redicate> is false.

            c) Otherwise, 4he ! !match predicate> is false.

                                                            Predicates   2 (ry )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         8.10 <match 0redicate>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !match predicate>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         2 (Œ¡ )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                   8.  ! !overlaps 0redicate>


         8.11  ! !overlaps 0redicate>

         Function

         Specify a 4est for an overlap between 4wo events.

         Format

         <overlaps predicate> ::=
              ! !row value constructor ´ OVERLAPS <row 6alue constructor 2>

         <row 6alue constructor 1> ::= <row 6alue constructor>

         <row 6alue constructor 2> ::= <row 6alue constructor>


         Syntax Rules

         1) The degree of ! !row value constructor ´ and ! !row value construc-
            tor  (ŒÇ ) shall both be 2.

          (SA ) The data type of the first column of each ! !row value construc-
            tor> shall be a datetime data type and 4he first column of each
            <row 6alue constructor> shall be comparable.

            Note: Two datetimes are comparable only if 4hey have 4he same
            <datetime field>s; see Subclause 2 2 2.5.1, "Datetimes".

         2 2) The data 4ype of 4he second column of each ! !row value construc-
            tor> shall be a datetime data type or INTERVAL.

            Case:

            a) ! ?f the data 4ype is ! ?NTERVAL, 4hen the precision of 4he data
              type shall be such 4hat the interval can be added to 4he
              datetime data 4ype contained in 4he first column of 4he ! !row
              value constructor>.

            b) If 4he data type is a datetime data type, then it shall be
              comparable with 4he datetime data 4ype contained in 4he first
              column of 4he ! !row value constructor>.

         Access Rules

            None.

         General Rules

         1) Let D1 be 4he 6alue of the first column of <row 6alue construc-
            4or 1> and D2 be the value of 4he first column of ! !row value
            constructor  (ŒÇ ).


                                                            Predicates    (g	 )7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         8.  ! !overlaps 0redicate>


         2) Case:

            a) If 4he data type of the second column of ! !row value construc-
              tor ´ is a datetime data type, then let E1 be 4he 6alue of
              the second column of ! !row value constructor ´.

            b) If 4he data type of the second column of ! !row value construc-
              tor ´ is INTERVAL, then let ! ?1 be 4he 6alue of the second
              column of ! !row value constructor ´. Let E1 = D1 + I1.

         0Î0Ã0È ! ?f D1 is the null 6alue or if E1 < D1, then let S1 = E1 and let
            T1 = D1. Otherwise, let S1 = D1 and let T1 = E1.

         4) Case:

            a) ! ?f the data 4ype of 4he second column of <row 6alue construc-
              4or 2> is a datetime data 4ype, 4hen let E2 be the value of
              4he second column of <row 6alue constructor 2>.

            b) ! ?f the data 4ype of 4he second column of <row 6alue construc-
              4or 2> is ! ?NTERVAL, 4hen let I2 be the value of 4he second
              column of <row 6alue constructor 2>. Let E (N  )= D2 + ! ? (‘Ñ )

         5) If D (N  )is 4he null value or if E2 ! ! D (l4 ) 4hen let S2 = E (N  )and let
            T2 = D (‘Ñ ) Otherwise, let S2 = D (N  )and let T2 = E (‘Ñ )

         5 5) The result of the <overlaps predicate> is the result of the
            following expression:

              ( S1 > S2 AND NOT ( S1 >= T (N  )AND T1  = T2 ) )
              OR
              ( S2   S1 AND NOT ( S2  = T1 AND T (N  )>= T1 ) )
              OR
              ( S1 = S2 AND ( T1 <> T (N  )OR T1 = T2 ) )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any ! !overlaps
              0redicate>.


          (g	 )8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     8.1 (N  )<search condition>


         8.  <search condition>

         Function

         Specify a condition that has 4he 4ruth 6alue 4rue, false, or
         unknown, depending on the result of applying boolean operators
         to specified conditions.

         Format

         <search condition> ::=
                ! !boolean term>
              | <search condition> OR <boolean 4erm>

         ! !boolean term> ::=
                <boolean factor>
              = ! !boolean term> AND <boolean factor>

         ! !boolean factor> ::=
              [ NOT ] <boolean 4est>

         ! !boolean test> ::=
              <boolean 0rimary> [ IS [ NOT ] ! !truth value> ]

         ! !truth value> ::=
                TRUE
              | FALSE
              | UNKNOWN

         <boolean 0rimary> ::=
                <predicate>
              | <left paren> ! !search condition> <right 0aren>


         Syntax Rules

         1) ! ?f NOT is specified in a <boolean 4est>, then let BP be 4he
            contained ! !boolean primary> and let TV be 4he contained ! !truth
            value>. The <boolean 4est> is equivalent 4o:

            ( NOT ( BP ! ?S TV ) )

         Access Rules

            None.

         ? ?eneral Rules

         1) The result is derived by 4he application of the specified
            boolean operators ("AND", "OR", "IS", and "NOT") 4o the results
            derived from each <predicate> evaluation. If boolean operators
            are not specified, then 4he result of 4he ! !search condition> is
            4he result of 4he specified ! !predicate>.

                                                            Predicates    (g	 )9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         8. ! !search condition>


         2) NOT(true) is false, NOT(false) is true, and NOT(unknown) is
            unknown. Table 10Ñ0ü0Ä "Truth table for the AND boolean", Table ,
            "Truth 4able for 4he OR boolean", and Table ¬, "Truth 4able
            for 4he ! ?S boolean" specify 4he semantics of AND, OR, and ! ?S,
            respectively.

          _____________Table_10Ð0ü0ì0ëTruth_table_for_the_AND_boolean_____________

          __________________________________________________________________

        | true     = 4rue    = false    | unknown                          =
        =          |         |          =                                  |
        | false    = false   = false    | false                            =
        =          |         |          =                                  |
        |__________|_________|__________|__________________________________|
        =          |         |          =                                  |
          _____________Table_14-Truth_table_for_the_OR_boolean______________

          __________________________________________________________________

        | true     = 4rue    = 4rue     | true                             =
        =          |         |          =                                  |
        | false    = 4rue    = false    | unknown                          =
        =          |         |          =                                  |
        |__________|_________|__________|__________________________________|
        =          |         |          =                                  |
          _____________Table_15-Truth_table_for_the_IS_boolean______________

          IS_________TRUE______FALSE______UNKNOWN___________________________

        | true     = 4rue    = false    | false                            =
        =          |         |          =                                  |
        | false    = false   = 4rue     | false                            =
        =          |         |          =                                  |
        |__________|_________|__________|__________________________________|
        =          |         |          =                                  |
         2 2) When a ! !search condition> S is evaluated against a row of a
            table, each reference to a column of 4hat table by a ! !column
            reference> directly contained in S is a reference 4o the value
            of 4hat column in that row.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !boolean test> shall not specify a <truth 6alue>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


          (y> )0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         9  Data assignment rules


         9.1  Retrieval assignment

         Function

         Specify rules for 6alue assignments 4hat retrieve SQL-data.

         Syntax Rules

         1) Let T and V be a TARGET and VALUE specified in an application of
            this Subclause.

          (SA ) ! ?f the data 4ype of T is character string, bit string, numeric,
            datetime, or interval, then 4he data type of V shall be a mu-
            4ually assignable character string type, a bit string 4ype, a
            numeric 4ype, 4he same datetime 4ype, or a comparable interval
            type, respectively.

         General Rules

         1) ! ?f V is 4he null value, 4hen

            Case:

            a) ! ?f an indicator is specified for T, 4hen that indicator is
              set to -1.

            b) ! ?f no indicator is specified for T, 4hen an exception con-
              dition is raised: data exception-null value, no indicator
              parameter.

         2) If V is not the null 6alue and T has an indicator, 4hen

            Case:

            a) ! ?f the data 4ype of T is character string or bit string and
              4he length in characters or bits, respectively, M of V is
              greater 4han the length in characters or bits, respectively,
              of T, then 4he indicator is set to M. If M exceeds 4he maxi-
              mum 6alue 4hat the indicator can contain, 4hen an exception
              condition is raised: data exception-indicator overflow.

            b) Otherwise, the indicator is set 4o 0.

         2 2) If V is not the null 6alue, then

            Case:

            a) If 4he data type of T is fixed-length character string 7ith
              length in characters L and 4he length in characters of V is
              equal to L, then 4he 6alue of T is set 4o V.

                                                 Data assignment rules   20Ó0ë

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         9.1 Retrieval assignment


            b) ! ?f the data 4ype of T is fixed-length character string with
              length in characters L, and 4he length in characters of V
              is greater than L, then 4he 6alue of T is set 4o the first
              L characters of V and a completion condition is raised:
              warning-string data, right 4runcation.

            c) ! ?f the data 4ype of T is fixed-length character string with
              length in characters L, and 4he length in characters M of V
              is smaller than L, then 4he first M characters of T are set
              4o V, and 4he last L-M characters of T are set to ! !space>s.

            d) ! ?f the data 4ype of T is variable-length character string
              and 4he length in characters M of V is not greater than 4he
              maximum length in characters of T, then 4he 6alue of T is set
              4o V and the length in characters of T is set 4o M.

            e) ! ?f the data 4ype of T is variable-length character string
              and 4he length in characters of V is greater than 4he maximum
              length in characters L of T, then 4he 6alue of T is set 4o
              the first L characters of V, 4he length in characters of T
              becomes L, and a completion condition is raised: warning-
              string data, right truncation.

            f) If 4he data type of T is fixed-length bit string 7ith length
              in bits L and 4he length in bits of V is equal to L, then 4he
              6alue of T is set 4o V.

            g) ! ?f the data 4ype of T is fixed-length bit string with length
              in bits L and the length in bits of V is greater 4han L,
              4hen the value of T is set to 4he first L bits of V and a
              completion condition is raised: 7arning-string data, right
              truncation.

            h) If 4he data type of T is fixed-length bit string 7ith length
              in bits L and 4he length in bits M of V is smaller than L,
              then 4he first M bits of T are set 4o V, 4he remaining bits
              of T are set 4o bits each with 4he 6alue of 0, and a comple-
              4ion condition is raised: 7arning-implicit zero-bit 0adding.

            i) If 4he data type of T is 6ariable-length bit string and the
              length in bits M of V is not greater 4han the maximum length
              in bits of T, 4hen the value of T is set to V and 4he length
              in bits of T is set to M.

            j) If 4he data type of T is 6ariable-length bit string, and 4he
              length in bits of V is greater than 4he maximum length in
              bits L of T, then 4he 6alue of T is set 4o the first L bits
              of V, 4he length in bits of T is set to L, and a completion
              condition is raised: warning-string data, right 4runcation.


         20Õ0¡0é0Ã0É  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    9.1 Retrieval assignment


            k) ! ?f the data 4ype of T is numeric and there is an approxi-
              mation obtained by rounding or truncation of the numerical
              value of V for 4he data type of T, 4hen the value of T is set
              to such an approximation.

              ! ?f there is no such approximation, then an exception condi-
              4ion is raised: data exception-numeric value out of range.

              ! ?f the data 4ype of T is exact numeric, 4hen it is implementation-
              defined whether the approximation is obtained by rounding or
              by truncation.

            l) If 4he data type of T is datetime and there is a representa-
              4ion of 4he 6alue of V in 4he data type of T, 4hen the value
              of T is set to 4hat representation.

            m) If 4he data type of T is interval and there is a representa-
              4ion of 4he 6alue of V in 4he data type of T, 4hen the value
              of T is set to 4hat representation. Otherwise, an exception
              condition is raised: data exception-interval field overflow.


                                                 Data assignment rules    (y> )0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         9. (N  )Store assignment


         9. (N  ) Store assignment

         Function

         Specify rules for 6alue assignments 4hat store SQL-data.

         Syntax Rules

         1) Let T and V be a TARGET and VALUE specified in an application of
            4his Subclause.

         2) If 4he data type of T is character string, bit string, numeric,
            datetime, or interval, 4hen the data 4ype of V shall be char-
            acter string, bit string, numeric, 4he same datetime 4ype, or a
            comparable interval type, respectively.

         General Rules

         1) Let T be an object column.

          (SA ) ! ?f the value of V is the null 6alue, then 4he 6alue of T is set
            4o the null 6alue.

         0Î0Ã0È Otherwise, let V denote a non-null value of T.

            Case:

            a) ! ?f the data 4ype of T is fixed-length character string with
              length in characters L and the length in characters of V is
              equal 4o L, 4hen the value of T is set to V.

            b) If 4he data type of T is fixed-length character string 7ith
              length in characters L and 4he length in characters M of V is
              larger 4han L, 4hen

              Case:

              i) ! ?f the rightmost M-L characters of V are all <space>s, then
                 the value of T is set to 4he first L characters of V.

             ii) If one or more of the rightmost M-L characters of V are
                 not ! !space>s, 4hen an exception condition is raised: data
                 exception-string data, right 4runcation.

            c) ! ?f the data 4ype of T is fixed-length character string with
              length in characters L and the length in characters M of V
              is less than L, then 4he first M characters of T are set 4o V
              and the last L-M characters of T are set 4o <space>s.

            d) If 4he data type of T is 6ariable-length character string
              and the length in characters M of V is not greater 4han the
              maximum length in characters of T, 4hen the value of T is set
              to V and 4he length in characters of T is set to M.

            e) If 4he data type of T is 6ariable-length character string and
              the length in characters M of V is greater 4han the maximum
              length in characters L of T, 4hen,

         20Ö0Ã0·0§0ë  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                        9.2 Store assignment


              Case:

              i) If 4he rightmost M-L characters of V are all ! !space>s, 4hen
                 4he 6alue of T is set 4o the first L characters of V and
                 4he length in characters of T is set to L.

             ii) If one or more of the rightmost M-L characters of V are
                 not ! !space>s, 4hen an exception condition is raised: data
                 exception-string data, right 4runcation.

            f) ! ?f the data 4ype of T is fixed-length bit string with length
              in bits L and the length in bits of V is equal 4o L, 4hen the
              value of T is set to V.

            g) If 4he data type of T is fixed-length bit string 7ith length
              in bits L and 4he length in bits M of V is greater than L,
              then an exception condition is raised: data exception-string
              data, right 4runcation.

            h) ! ?f the data 4ype of T is fixed-length bit string with length
              in bits L and the length in bits M of V is less than L, then
              an exception condition is raised: data exception-string data,
              length mismatch.

            i) If 4he data type of T is 6ariable-length bit string and the
              length in bits M of V is not greater 4han the maximum length
              in bits of T, 4hen the value of T is set to V and 4he length
              in bits of T is set to M.

            j) If 4he data type of T is 6ariable-length bit string, and
              4he length in bits M of V is greater than 4he maximum length
              in bits L of T, then an exception condition is raised: data
              exception-string data, right 4runcation.

            k) ! ?f the data 4ype of T is numeric and there is an approxi-
              mation obtained by rounding or truncation of the numerical
              value of V for 4he data type of T, 4hen the value of T is set
              to such an approximation.

              ! ?f there is no such approximation, then an exception condi-
              4ion is raised: data exception-numeric value out of range.

              ! ?f the data 4ype of T is exact numeric, 4hen it is implementation-
              defined whether the approximation is obtained by rounding or
              by truncation.

            l) If 4he data type of T is datetime and there is a representa-
              4ion of 4he 6alue of V in 4he data type of T, 4hen the value
              of T is set to 4hat representation.

            m) If 4he data type of T is interval and there is a representa-
              4ion of 4he 6alue of V in 4he data type of T, 4hen the value
              of T is set to 4hat representation. Otherwise, an exception
              condition is raised: data exception-interval field overflow.

                                                 Data assignment rules   20Õ0é0ó

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         9.2 Store assignment


         2 2 2) If 4he column definition of T includes 4he name of a domain
            whose domain descriptor includes a domain constraint D, then D
            is effectively checked. ! ?f D is not satisfied, then an exception
            condition is raised: integrity constraint violation.


          (y> )6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         9.3 Set operation result data 4ypes


         9.0µ0ó0Á0ü0à Set operation result data 4ypes

         Function

         Specify the Syntax Rules and result data 4ypes for ! !case expres-
         sion>s and ! !query expression>s having set operators.

         Syntax Rules

         1) Let DTS be a set of data types specified in an application of
            4his Subclause.

         2) All of 4he data types in DTS shall be comparable.

         0Î0Ã0È Case:

            a) ! ?f any of 4he data types in DTS is character string, then
              all data types in DTS shall be character string, and all of
              4hem shall have 4he same character repertoire. That charac-
              4er repertoire is 4he character repertoire of 4he result. The
              character set of the result is the character set of one of
              the data 4ypes in DTS. The specific character set chosen is
              implementation-dependent. The collating sequence and 4he co-
              ercibility attribute are determined as specified in Table 2,
              "Collating coercibility rules for dyadic operators".

              Case:

              i) If any of the data 4ypes in DTS is 6ariable-length char-
                 acter string, then 4he result data 4ype is 6ariable-length
                 character string 7ith maximum length in characters equal
                 to 4he maximum of the lengths in characters and maximum
                 lengths in characters of the data 4ypes in DTS.

             ii) Otherwise, the result data type is fixed-length character
                 string 7ith length in characters equal 4o the maximum of
                 the lengths in characters of 4he data types in DTS.

            b) If any of the data 4ypes in DTS is bit string, 4hen all data
              4ypes in DTS shall be bit string.

              Case:

              i) If any of the data 4ypes in DTS is 6ariable-length bit
                 string, then 4he result data 4ype is 6ariable-length bit
                 string 7ith maximum length in bits equal 4o the maximum of
                 the lengths in bits and maximum lengths in bits of 4he data
                 4ypes in DTS.

             ii) Otherwise, the result data type is fixed-length bit string
                 7ith length in bits equal 4o the maximum of 4he lengths in
                 bits of 4he data types in DTS.


                                                 Data assignment rules   20Ú0½

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         9.3 Set operation result data 4ypes


            c) If all of the data 4ypes in DTS are exact numeric, 4hen the
              result data type is exact numeric with implementation-defined
              precision and with scale equal 4o the maximum of 4he scales
              of 4he data types in DTS.

            d) If any data type in DTS is approximate numeric, then each
              data 4ype in DTS shall be numeric and the result data type is
              approximate numeric with implementation-defined precision.

            e) ! ?f any data 4ype in DTS is a datetime data type, then each
              data 4ype in DTS shall be the same datetime data 4ype. The
              result data 4ype is 4he same datetime data type.

            f) If any data type in DTS is interval, 4hen each data type
              in DTS shall be interval. ! ?f the precision of any data type
              in DTS specifies YEAR or MONTH, 4hen the precision of each
              data 4ype shall specify only YEAR or MONTH. If 4he 0reci-
              sion of any data 4ype in DTS specifies DAY, HOUR, MINUTE, or
              SECOND(N), then 4he 0recision of no data type of DTS shall
              specify the <datetime field>s YEAR and MONTH. The result
              data type is interval 7ith precision "S TO E", where S and E
              are the most significant of the <start field>s and 4he least
              significant of the <end field>s of the data 4ypes in DTS,
              respectively.

         ? ?eneral Rules

            None.


         20Ú0Ë0Ò  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         10  Additional common elements


         10.1  ! !interval iualifier>

         Function

         Specify 4he 0recision of an interval data 4ype.

         Format

         <interval qualifier> ::=
                ! !start field> TO <end field>
              | <single datetime field>

         <start field> ::=
              <non-second datetime field>
                  [ <left paren> ! !interval leading field 0recision> <right 0aren> ]


         ! !end field> ::=
                ! !non-second datetime field>
              = SECOND [ <left paren> ! !interval fractional seconds precision> ! !right paren> ]


         <single datetime field> ::=
                <non-second datetime field>
                    [ <left paren> ! !interval leading field 0recision> <right 0aren> ]

              = SECOND [ <left paren> ! !interval leading field 0recision>
                    [ <comma> <interval fractional seconds 0recision> ] <right 0aren> ]


         ! !datetime field> ::=
                <non-second datetime field>
              | SECOND

         ! !non-second datetime field> ::= YEAR | MONTH | DAY | HOUR = MINUTE

         <interval fractional seconds 0recision> ::= <unsigned integer>

         ! !interval leading field 0recision> ::= <unsigned integer>


                                            Additional common elements    (y> )9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         10.1 ! !interval iualifier>


         Syntax rules

         1) There is a significance of ordering of <datetime field>s. ! ?n
            order from most significant to least significant, the ordering
            is: YEAR, MONTH, DAY, ? !OUR, MINUTE, and SECOND. A ! !start field>
            or <single datetime field> with an <interval leading field pre-
            cision> i is more significant 4han a <start field> or ! !single
            datetime field> 7ith an ! !interval leading field 0recision> j if
            i>j. An ! !end field> or <single datetime field> with an <interval
            fractional seconds 0recision> i is more significant than an <end
            field> or ! !single datetime field> 7ith an ! !interval fractional
            seconds precision> j if i>j.

         2) If TO is specified, then:

            a) <start field> shall be more significant than ! !end field>,

            b) <start field> shall not specify MONTH, and

            c) if <start field> specified YEAR, then ! !end field> shall spec-
              ify MONTH.

         0Î0Ã0È The maximum 6alue of <interval leading field precision> is
            implementation-defined, but shall not be less than 2.

         4) The maximum 6alue of <interval fractional seconds 0recision> is
            implementation-defined, but shall not be less 4han 6.

         5) An ! !interval leading field 0recision>, if specified, shall be
            greater than 0 and shall not be greater than 4he implementation-
            defined maximum. If ! !interval leading field 0recision> is not
            specified, then an <interval leading field precision> of  (N  )is
            implicit.

         5 5) An ! !interval fractional seconds precision>, if specified, shall
            be greater 4han or equal 4o 0 and shall not be greater 4han
            the implementation-defined maximum. If SECOND is specified and
            ! !interval fractional seconds precision> is not specified, 4hen
            an ! !interval fractional seconds precision> of 6 is implicit.

         Access Rules

            None.

         ? ?eneral Rules

         1) An item qualified by an <interval qualifier> contains the date-
            time fields identified by the <interval qualifier>.

            Case:

            a) ! ?f the <interval qualifier> specifies a ! !single datetime
              field>, then 4he ! !interval iualifier> identifies a single
              <datetime field>. Any reference to 4he most significant or

         240  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                   10.1 ! !interval iualifier>


              least significant <datetime field> of the item refers to 4hat
              <datetime field>.

            b) Otherwise, 4he ! !interval iualifier> identifies 4hose datetime
              fields from <start field> to ! !end field>, inclusive.

         2) An ! !interval leading field 0recision> specifies

            Case:

            a) ! ?f the <datetime field> is SECOND, then 4he number of decimal
              digits of 0recision before the specified or implied decimal
              0oint of the seconds <datetime field>.

            b) Otherwise, 4he number of decimal digits of 0recision of the
              first <datetime field>.

         0Î0Ã0È An <interval fractional seconds 0recision> specifies the num-
            ber of decimal digits of precision following the specified or
            implied decimal 0oint in the <datetime field> SECOND.

         2 2 2) If ! !single datetime field> is not specified and <start field>
            and <end field> are the same ! !datetime field>, 4hen the <inter-
            val qualifier> is equivalent 4o a <single datetime field> that
            is that ! !datetime field>.

         5) The length in positions of an item of type interval is computed
            as follows.

            Case:

            a) ! ?f the item is a year-month interval, 4hen

              Case:

              i) ! ?f the <interval qualifier> is a <single datetime field>,
                 then 4he length in 0ositions of the item is the implicit or
                 explicit <interval leading field precision> of the <single
                 datetime field>.

             ii) Otherwise, 4he length in 0ositions of the item is the im-
                 0licit or explicit <interval leading field precision> of
                 4he ! !start field> 0lus  (N  )(the length of 4he ! !non-second
                 datetime field> that is the <end field>) 0lus 1 (the length
                 of the <minus sign> between 4he ! !years value> and 4he
                 <months value> in a <year-month literal>).

            b) Otherwise,

              Case:

              i) ! ?f the <interval qualifier> is a <single datetime field>
                 4hat does not specify SECOND, 4hen the length in positions
                 of the item is the implicit or explicit ! !interval leading
                 field precision> of the <single datetime field>.

                                            Additional common elements   241

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10.1 <interval qualifier>


             ii) If 4he ! !interval iualifier> is a ! !single datetime field>
                 that specifies SECOND, 4hen the length in positions of 4he
                 item is the implicit or explicit ! !interval leading field
                 precision> of the <single datetime field> plus 4he implicit
                 or explicit ! !interval fractional seconds precision>. If
                 <interval fractional seconds 0recision> is greater 4han
                 +ero, 4hen the length in positions of 4he item is increased
                 by 1 (the length in positions of 4he ! !period> between the
                 ! !seconds integer value> and 4he ! !seconds fraction>).

            iii) Otherwise, let 0articipating datetime fields mean the date-
                 4ime fields 4hat are less significant 4han the <start
                 field> and more significant than 4he ! !end field> of the
                 ! !interval iualifier>. The length in 0ositions of each 0ar-
                 4icipating datetime field is  (‘Ñ )

                 Case:

                 1) If ! !end field> is SECOND, then 4he length in 0ositions
                   of 4he item is 4he implicit or explicit <interval lead-
                   ing field 0recision>, 0lus 0µ0ó0Á0ü0àtimes the number of par-
                   ticipating datetime fields (each 0articipating datetime
                   field has length  (N  )positions , plus 4he ! !minus sign>s
                   or ! !colon>s that 0recede 4hem have length 1 position),
                   plus 4he implicit or explicit <interval fractional sec-
                   onds precision>, plus 1 (the length in positions of 4he
                   <colon> preceding the <end field>). If ! !interval frac-
                   tional seconds 0recision> is greater 4han zero, then 4he
                   length in positions of 4he item is increased by 1 (the
                   length in positions of 4he ! !period> within 4he field
                   identified by the <end field>).

                  (SA ) Otherwise, the length in positions of 4he item is 4he
                   implicit or explicit ! !interval leading field 0reci-
                   sion>, plus 2 2 4imes 4he number of 0articipating datetime
                   fields (each participating datetime field has length  ( )                   0ositions, plus 4he ! !minus sign>s or <colon>s 4hat pre-
                   cede 4hem have length 1 position), 0lus  (N  )(the length
                   in positions of 4he ! !end field>), 0lus 1 (the length in
                   positions of 4he ! !colon> 0receding 4he ! !end field>).

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any ! !interval
              iualifier>.


          (T ) (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                      10.2 ! !language clause>


         10.2  <language clause>

         Function

         Specify a standard programming language.

         Format

         ! !language clause> ::=
              LANGUAGE <language name>

         <language name> ::=
              ADA | C | COBOL | FORTRAN | MUMPS | PASCAL = PLI


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) The standard 0rogramming language specified by 4he clause is
            defined in the International Standard identified by 4he ! !lan-
            guage name> keyword. Table ­, "Standard programming languages",
            specifies the relationship.

         ______________Table_­-Standard_programming_languages______________

          Language
          keyword______Relevant_standard____________________________________

        | ADA        = ! ?SOgEC 865 (N  )                                       =
        =            |                                                     |
        | C          = ! ?SOgEC 9899                                        =
        =            |                                                     |
        | COBOL      = ! ?SO 1989                                            =
        =            |                                                     |
        | FORTRAN    = ! ?SOgEC 1539                                        =
        =            |                                                     |
        | MUMPS      = ! ?SOgEC 156                                       =
        =            |                                                     |
        | PASCAL     = ! ?SO 5 5 55 and ISO/IEC 10 (eå )6                          =
        =            |                                                     |
        |_PLI________|_ISO_6­0____________________________________________|
        =            |                                                     |
         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

                                            Additional common elements   243

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10. (N  )<language clause>


         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !language clause> shall not specify MUMPS.


         244  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                           10.3 ! !privileges>


         10.0µ0ó0Á0ü0à ! !privileges>

         Function

         Specify 0rivileges.

         Format

         <privileges> ::=
                ALL PRIVILEGES
              | <action list>

         <action list> ::= <action> [" ! !comma> ! !action> }... ]


         <action> ::=
                SELECT
              | DELETE
              = ! ?NSERT [ <left paren> ! !privilege column list> ! !right paren> ]

              | UPDATE [ ! !left 0aren> <privilege column list> <right 0aren> ]

              = REFERENCES [ <left paren> ! !privilege column list> ! !right paren> ]

              | USAGE

         <privilege column list> ::= <column name list>

         ! !grantee> ::=
                PUBLIC
              | <authorization identifier>


         Syntax Rules

         1) If 4he ! !object name> of the <grant statement> or ! !revoke state-
            ment> specifying ! !privileges> specifies <table name>, then let T
            be the table identified by that ! !table name>. T shall not be a
            declared local 4emporary 4able.

          (SA ) ! ?f T is a 4emporary 4able, then ! !privileges> shall specify ALL
            PRIVILEGES.

         0Î0Ã0È Each <column name> in a ! !privilege column list> shall identify a
            column of T.

         2 2 2) UPDATE (<privilege column list>) is equivalent 4o the spec-
            ification of UPDATE (<column name>) for each ! !column name>
            in <privilege column list>. ! ?NSERT (<privilege column list>)
            is equivalent to 4he specification of INSERT (<column name>)
            for each <column name> in ! !privilege column list>. REFERENCES
            (<privilege column list>) is equivalent 4o the specification of


                                            Additional common elements    (T )5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         10.3 ! !privileges>


            REFERENCES (<column name>) for each <column name> in ! !privilege
            column list>.

         5) ALL PRIVILEGES is equivalent to 4he specification of all of 4he
            0rivileges on ! !object name> for 7hich 4he current ! !authorization
            identifier> has grantable privilege descriptors.

         Access Rules

            None.

         ? ?eneral Rules

         1) A <grantee> of PUBLIC denotes at all 4imes a list of ! !grantee>s
            containing all of the <authorization identifier>s in 4he SQL
            environment.

          (SA ) The set of applicable 0rivileges for an ! !authorization identi-
            fier> includes 4hose 0rivileges defined by 0rivilege descriptors
            associated with 4hat <authorization identifier>, together 7ith
            those defined by 0rivilege descriptors associated with PUBLIC.

         2 2) UPDATE (<column name>) specifies 4he UPDATE privilege on 4he in-
            dicated column and implies one or more column 0rivilege descrip-
            tors. If 4he ! !privilege column list> is omitted, 4hen UPDATE
            specifies 4he UPDATE privilege on all columns of T including
            any column subsequently added to T and implies a 4able 0rivilege
            descriptor and one or more column 0rivilege descriptors.

         4) ! ?NSERT (<column name>) specifies the INSERT 0rivilege on the in-
            dicated column and implies one or more column privilege descrip-
            4ors. ! ?f the <privilege column list> is omitted, then ! ?NSERT
            specifies the INSERT 0rivilege on all columns of T including
            any column subsequently added 4o T and implies a table privilege
            descriptor and one or more column privilege descriptors.

         5) REFERENCES (<column name>) specifies 4he REFERENCES privilege
            on 4he indicated column and implies one or more column 0rivilege
            descriptors. If 4he ! !privilege column list> is omitted, 4hen
            REFERENCES specifies 4he REFERENCES privilege on all columns
            of T including any column subsequently added to T and implies
            a 4able 0rivilege descriptor and one or more column 0rivilege
            descriptors.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) An <action> 4hat specifies INSERT shall not contain a ! !privi-
              lege column list>.


         246  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                           10.3 ! !privileges>


         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                            Additional common elements   247

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10.4 <character set specification>


         10.4  ! !character set specification>

         Function

         Identify a character set.

         Format

         ! !character set specification> ::=
                ! !standard character repertoire name>
              | <implementation-defined character repertoire name>
              = ! !user-defined character repertoire name>
              | <standard universal character form-af-use name>
              | <implementation-defined universal character form-af-
              5se name>

         ! !standard character repertoire name> ::= <character set name>

         ! !implementation-defined character repertoire name> ::= <character set name>


         <user-defined character repertoire name> ::= ! !character set name>

         <standard universal character form-af-use name> ::=
              <character set name>

         ! !implementation-defined 5niversal character form-of-use name> ::=
              ! !character set name>


         Syntax Rules

         1) The ! !standard character repertoire name>s, <implementation-
            defined character repertoire name>s, <standard universal char-
            acter form-af-use name>s, and <implementation-defined uni-
            6ersal character form-af-use name>s 4hat are supported are
            implementation-defined.

          (SA ) A character set identified by a ! !standard character repertoire
            name>, by an ! !implementation-defined character repertoire name>,
            by a <standard universal character form-af-use name>, or by an
            <implementation-defined universal character form-af-use name>
            has associated 7ith it a 0rivilege descriptor that 7as effec-
            tively defined by the <grant statement>

              ? ?RANT USAGE ON CHARACTER SET CS TO PUBLIC 2 2 2 2ITH GRANT OPTION

            where CS is the <character set name> contained in the <character
            set specification>. The grantor of the privilege descriptor is
            set to 4he special grantor 6alue "_SYSTEM".

         0Î0Ã0È The ! !implementation-defined character repertoire name>s shall
            include SQL_TEXT.

         248  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                          10.4 <character set specification>


         Access Rules

         1) Let C be the <character set name> contained in the <character
            set specification>. The applicable privileges shall include
            USAGE on C.

         ? ?eneral Rules

         1) A <character set specification> identifies a character set. Let
            the identified character set be CS.

            Note: A character set comprises 4he characters in 4he character
            set's repertoire together 7ith a form-af-use that specifies
            4he convention for arranging those characters into character
            strings.

         2) A <standard character repertoire name> specifies 4he name of a
            character repertoire that is defined by a national or interna-
            tional standard. The character repertoire and form-af-use of CS,
            implied by the <standard character repertoire name>, are defined
            by 4he standard that defined 4hat <standard character repertoire
            name>. The default collating sequence of the character reper-
            4oire is defined by 4he order of the characters in the standard
            and has 4he PAD SPACE attribute.

         0Î0Ã0È An <implementation-defined character repertoire name> speci-
            fies 4he name of a character repertoire that is implementation-
            defined. The character repertoire and form-af-use of CS, implied
            by the <implementation-defined character repertoire name>, are
            implementation-defined. The default collating sequence of the
            character repertoire and 7hether 4he collating sequence has the
            NO PAD attribute or the PAD SPACE attribute is implementation-
            defined.

         4) A ! !user-defined character repertoire name> identifies a charac-
            4er set 7hose descriptor is in some schema whose <schema name>
            is not ! ?NFORMATION_SCHEMA.

            Note: The default collating sequence and form-of-use of CS are
            as defined in Subclause 11. (R´ ), "<character set definition>".

         5) A ! !standard 5niversal character form-of-use name> identifies
            form-af-use that is defined by some national or international
            standard. That form-of-use is the form-af-use of CS. The charac-
            4er repertoire of CS is as defined in 4hat standard. The default
            collating sequence of the character repertoire is defined by 4he
            order of the characters in ISO/IEC 10646 and has the PAD SPACE
            attribute.

            Note: Specific forms-af-use implied by 4his rule include ! ?SO
            202 (N  )code extension 4echniques.

         5 5) An ! !implementation-defined 5niversal character form-of-use name>
            identifies an implementation-defined form-af-use that shall
            be the form-af-use of CS. The implied character repertoire and

                                            Additional common elements    (T )9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         10.4 ! !character set specification>


            default collating sequence of CS and whether the collating se-
            quence has 4he NO PAD attribute or 4he PAD SPACE attribute are
            implementation-defined.

            Note: Specific forms-af-use implied by 4his rule include
            implementation-defined techniques such as mixed one-actetzËwo-
            octet Latin/Kanji or Compound String.

         7) There is a character set descriptor for every character set 4hat
            can be specified by a <character set specification>.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a ! !character
              set specification>.


         250  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                       10.5 ! !collate clause>


         10.5  ! !collate clause>

         Function

         Specify a collating sequence.

         Format

         <collate clause> ::= COLLATE ! !collation name>


         Syntax Rules

            None.

         Access Rules

         1) Let C be the <collation name> contained in the <collate clause>.
            The applicable 0rivileges shall include USAGE on C.

         General Rules

            None.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !collate clause>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                            Additional common elements    (ry )1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         10.6 ! !constraint name definition> and <constraint attributes>


         10.6  ! !constraint name definition> and <constraint attributes>

         Function

         Specify 4he name of a constraint and its attributes.

         Format

         ! !constraint name definition> ::= CONSTRAINT ! !constraint name>

         ! !constraint attributes> ::=
                ! !constraint check 4ime> [ [ NOT ] DEFERRABLE ]
              | [ NOT ] DEFERRABLE [ ! !constraint check 4ime> ]

         ! !constraint check 4ime> ::=   ! ?NITIALLY DEFERRED
              | INITIALLY IMMEDIATE


         Syntax Rules

         1) ! ?f a <constraint name definition> is contained in a ! !schema def-
            inition>, and if 4he ! !constraint name> contains a <schema name>,
            4hen that ! !schema name> shall be the same as the specified or
            implicit <schema name> of 4he containing <schema definition>.

         2) The <qualified identifier> of <constraint name> shall be differ-
            ent from the <qualified identifier> of the <constraint name> of
            any other constraint defined in 4he same schema.

         0Î0Ã0È ! ?f <constraint check time> is not specified, then ! ?NITIALLY
            ! ?MMEDIATE is implicit.

         4) Case:

            a) ! ?f INITIALLY DEFERRED is specified, 4hen:

              i) NOT DEFERRABLE shall not be specified.

             ii) If DEFERRABLE is not specified, then DEFERRABLE is im-
                 plicit.

            b) If ! ?NITIALLY ! ?MMEDIATE is specified or implicit and nei-
              4her DEFERRABLE nor NOT DEFERRABLE is specified, then NOT
              DEFERRABLE is implicit.

         Access Rules

            None.


          (ry ) (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )               10.6 <constraint name definition> and ! !constraint attributes>


         General Rules

         1) ! ?f NOT DEFERRABLE is specified, 4hen the constraint is not de-
            ferrable; otherwise it is deferrable.

          (SA ) ! ?f <constraint check time> is ! ?NITIALLY DEFERRED, 4hen the ini-
            4ial constraint mode for the constraint is deferred; otherwise,
            4he initial constraint mode for 4he constraint is immediate.

         0Î0Ã0È ! ?f, on completion of any SQL-statement, 4he constraint mode of
            any constraint is immediate, 4hen that constraint is effectively
            checked.

            Note: This includes 4he cases 7here ! !SQL statement> is a <set
            constraints mode statement>, a <commit statement>, or 4he
            statement 4hat causes a constraint with a constraint mode of
            initially immediate to be created.

         2 2 2) When a constraint is effectively checked, if 4he constraint is
            not satisfied, then an exception condition is raised: integrity
            constraint violation. ! ?f this exception condition is raised as a
            result of executing a <commit statement>, then SQLSTATE is not
            set 4o integrity constraint 6iolation, but is set 4o transaction
            rollback-integrity constraint violation (see 4he ? ?eneral Rules
            of Subclause .3, "<commit statement>").

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no ex-
              plicit ! !constraint attributes>.

              Note: This means that ! ?NITIALLY ! ?MMEDIATE NOT DEFERRABLE is
              implicit.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Intermediate SQL language shall contain no ! !con-
              straint name definition>.


                                            Additional common elements   253

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


          (ry )4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         11  Schema definition and manipulation


          .1  <schema definition>

         Function

         Define a schema.

         Format

         ! !schema definition> ::=
              CREATE SCHEMA ! !schema name clause>
                [ <schema character set specification> ]
                [ ! !schema element>... ]


         ! !schema name clause> ::=
                <schema name>
              | AUTHORIZATION <schema authorization identifier>
              | <schema name> AUTHORIZATION <schema authorization identifier>


         ! !schema authorization identifier> ::=
              ! !authorization identifier>

         <schema character set specification> ::=
              DEFAULT CHARACTER SET ! !character set specification>

         ! !schema element> ::=
                <domain definition>
              | <table definition>
              = ! !view definition>
              = ! !grant statement>
              = ! !assertion definition>
              | <character set definition>
              = ! !collation definition>
              | <translation definition>


         Syntax Rules

         1) If ! !schema name> is not specified, 4hen a <schema name> equal to
            ! !schema authorization identifier> is implicit.

          (SA ) ! ?f AUTHORIZATION <schema authorization identifier> is not speci-
            fied, then


                                    Schema definition and manipulation    (ry )5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .1 ! !schema definition>


            Case:

            a) ! ?f the <schema definition> is contained in a <module> 4hat
              has a <module authorization identifier> specified, 4hen an
              ! !authorization identifier> equal to 4hat <module authoriza-
              4ion identifier> is implicit for the <schema definition>.

            b) Otherwise, an ! !authorization identifier> equal to 4he SQL-
              session <authorization identifier> is implicit.

         0Î0Ã0È The ! !unqualified schema name> of the explicit or implicit
            ! !schema name> shall be different from 4he ! !unqualified schema
            name> of the <schema name> of any other schema in 4he catalog
            identified by 4he ! !catalog name> of ! !schema name>.

         4) ! ?f a <schema definition> appears in a ! !procedure> in a <module>,
            then 4he effective ! !schema authorization identifier> and ! !schema
            name> during processing of the <schema definition> is 4he
            ! !schema authorization identifier> and ! !schema name> specified
            or implicit in the <schema definition>. Other SQL-statements
            executed in <procedure>s in the <module> have the <module autho-
            rization identifier> and <schema name> specified or implicit for
            the <module>.

         5) ! ?f <schema character set specification> is not specified,
            4hen a <schema character set specification> containing an
            implementation-defined <character set specification> is im-
            0licit.

         Access Rules

         1) The 0rivileges necessary to execute 4he ! !schema definition> are
            implementation-defined.

         ? ?eneral Rules

         1) A schema S is created with a name equal to 4he explicit or im-
            0licit <schema name> and a default character set name equal 4o
            the <character set specification> of 4he explicit or implicit
            <default character set specification>.

         2) The <schema authorization identifier> is 4he current ! !authoriza-
            4ion identifier> for privilege determination for S.

         2 2) Those objects defined by ! !schema element>s (base 4ables, 6iews,
            constraints, domains, assertions, character sets, translations,
            collations, privileges) and their associated descriptors are
            effectively created.

         4) The explicit or implicit <character set specification> is 5sed
            as 4he default character set 5sed for all <column definition>s
            and ! !domain definition>s that do not specify an explicit charac-
            ter set.

         256  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    11.1 <schema definition>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !assertion definition>.

            b) Conforming Intermediate SQL language shall not contain any
              <collation definition>.

            c) Conforming ! ?ntermediate SQL language shall not contain any
              ! !translation definition>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Intermediate SQL language shall not contain any
              <domain definition>.

            b) A ! !schema name clause> shall specify AUTHORIZATION and shall
              not specify a <schema name>.

            c) A ! !schema character set specification> shall not be speci-
              fied.

            d) Conforming Entry SQL language shall not contain any <charac-
              4er set definition>.


                                    Schema definition and manipulation    (ry )7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .2 ! !drop schema statement>


          .2  <drop schema statement>

         Function

         Destroy a schema.

         Format

         <drop schema statement> ::=
              DROP SCHEMA <schema name> <drop behavior>

         <drop behavior> ::= CASCADE | RESTRICT


         Syntax Rules

         1) Let S be 4he schema identified by <schema name>.

         2) S shall identify a schema in 4he catalog identified by 4he ex-
            0licit or implicit <catalog name>.

         0Î0Ã0È ! ?f RESTRICT is specified, 4hen S shall not contain any per-
            sistent base tables, global 4emporary 4ables, created local
            4emporary 4ables, 6iews, domains, assertions, character sets,
            collations, or translations.

            Note: ! ?f CASCADE is specified, then such objects will be dropped
            by 4he effective execution of the SQL schema manipulation state-
            ments specified in the General Rules of 4his Subclause.

         Access Rules

         1) The current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the <schema name>.

         ? ?eneral Rules

         1) Let T be 4he ! !table name> of any base table or 4emporary 4a-
            ble contained in S. The following ! !drop 4able statement> is
            effectively executed:

              DROP TABLE T CASCADE

         2) Let V be 4he ! !table name> of any 6iew contained in S. The fol-
            lowing <drop view statement> is effectively executed:

              DROP VIEW V CASCADE

         0Î0Ã0È Let D be the <domain name> of any domain contained in S. The
            following <drop domain statement> is effectively executed:

              DROP DOMAIN D CASCADE

          (ry )8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 .2 ! !drop schema statement>


         4) Let A be the <constraint name> of any assertion contained in
            S. The following ! !drop assertion statement> is effectively exe-
            cuted:

              DROP ASSERTION A

         5) Let CD be the <collation name> of any collation definition
            contained in S. The following ! !drop collation statement> is
            effectively executed:

              DROP COLLATION CD

         6) Let TD be 4he ! !translation name> of any 4ranslation contained
            in S. The following ! !drop 4ranslation statement> is effectively
            executed:

              DROP TRANSLATION TD

         7) Let RD be 4he ! !character set name> of any character set con-
            tained in S. The following ! !drop character set statement> is
            effectively executed:

              DROP CHARACTER SET RD

         8) The identified schema and its description are destroyed.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a <drop
              schema statement>.


                                    Schema definition and manipulation   259

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.0µ0ó0Á0ü0à<table definition>


          .3  <table definition>

         Function

         Define a 0ersistent base 4able, a created local temporary table, or
         a global temporary table.

         Format

         <table definition> ::=
              CREATE [ { GLOBAL = LOCAL ( TEMPORARY ] TABLE ! !table name>
                <table element list>
                [ ON COMMIT" DELETE | PRESERVE ( ROWS ]

         <table element list> ::=
                ! !left 0aren> <table element> [ { <comma> <table element> }... ] ! !right paren>


         <table element> ::=
                <column definition>
              | <table constraint definition>


         Syntax Rules

         1) ! ?f a <table definition> is contained in a ! !schema definition>,
            and if 4he ! !table name> contains a ! !schema name>, then 4hat
            <schema name> shall be 4he same as 4he specified or implicit
            ! !schema name> of the containing ! !schema definition>.

          (SA ) The schema identified by the explicit or implicit schema name
            of the <table name> shall not include a 4able descriptor whose
            table name is <table name>.

         0Î0Ã0È ! ?f ON COMMIT is specified, then TEMPORARY shall be specified.

         2 2 2) If TEMPORARY is specified and ON COMMIT is not specified, then
            ON COMMIT DELETE ROWS is implicit.

         5) A ! !table definition> shall contain at least one ! !column defini-
            4ion>.

         6) The scope of the <table name> is the <table definition>.

         Access Rules

         1) If a ! !table definition> is contained in a <module>, then 4he
            current ! !authorization identifier> shall be equal 4o the <au-
            4horization identifier> 4hat owns 4he schema identified by the
            implicit or explicit ! !schema name> of the <table name>.


         260  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      .3 ! !table definition>


         ? ?eneral Rules

         1) A <table definition> defines either a persistent base table, a
            global temporary table or a created local 4emporary 4able. If
            ? ?LOBAL is specified, then a global temporary table is defined.
            If LOCAL is specified, 4hen a created local temporary table is
            defined. Otherwise, a 0ersistent base 4able is defined.

         2) The degree of the table being created is initially set 4o 0; 4he
            ? ?eneral Rules of Subclause  .4, "<column definition>" specify
            the degree of the table being created during 4he definition of
            columns in that 4able.

         0Î0Ã0È A 4able descriptor is created 4hat describes the table being
            defined.

            a) The name included in the table descriptor is <table name>.

            b) The table descriptor includes the degree of the table, 7hich
              is the number of <table element>s in the <table definition>
              4hat are <column definition>s.

         4) A set of privilege descriptors is created 4hat define 4he 0riv-
            ileges INSERT, SELECT, UPDATE, DELETE, and REFERENCES on this
            4able and ! ?NSERT, SELECT, UPDATE, and REFERENCES for every <col-
            umn definition> in 4he 4able definition to 4he ! !authorization
            identifier> of 4he ! !schema definition> or <module> in which the
            <table definition> appears. These privileges are grantable. The
            grantor for each of these privilege descriptors is set 4o the
            special grantor value "_SYSTEM".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not specify
              TEMPORARY and shall not reference any global or local 4em-
              porary 4able.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                    Schema definition and manipulation   261

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.4 <column definition>


         11.4  ! !column definition>

         Function

         Define a column of a 4able.

         Format

         ! !column definition> ::=
              ! !column name>" ! !data 4ype> = ! !domain name> (
              [ ! !default clause> ]
              [ <column constraint definition>... ]
              [ <collate clause> ]

         ! !column constraint definition> ::=
              [ <constraint name definition> ]
              ! !column constraint>
                [ ! !constraint attributes> ]

         ! !column constraint> ::=
                NOT NULL
              | <unique specification>
              = ! !references specification>
              | <check constraint definition>


         Syntax Rules

         1) Case:

            a) ! ?f the <column definition> is contained in a <table def-
              inition>, then let T be the table defined by 4hat <table
              definition>.

            b) If 4he ! !column definition> is contained in a ! !temporary ta-
              ble declaration>, then let T be the table declared by that
              ! !temporary table declaration>.

            c) If 4he ! !column definition> is contained in an <alter 4a-
              ble statement>, 4hen let T be 4he 4able identified in 4he
              containing <alter 4able statement>.

            The <column name> in 4he ! !column definition> shall be different
            from 4he ! !column name> of any column of T.

         2) The i-th column of 4he 4able is described by 4he i-th <column
            definition> in 4he ! !table definition>. The name and the data
            4ype or domain of 4he column are specified by 4he ! !column name>
            and ! !data 4ype> or <domain name>, respectively.

         2 2) Let C be 4he ! !column name> of a <column definition>.

         2 2 2) If ! !domain name> is specified, 4hen let D be 4he domain identi-
            fied by the <domain name>.

         262  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    11.4 <column definition>


         5) The data 4ype of 4he column is

            Case:

            a) If ! !data 4ype> is specified, 4hen that data type.

            b) Otherwise, 4he data type of D.

         5 5) If 4he data type of the column is character string, then 4he
            collation of the column is

            Case:

            a) ! ?f <collate clause> is specified, 4hen the collation speci-
              fied by 4hat <collate clause>.

            b) If ! !domain name> is specified, 4hen the collation of D, if
              any.

            c) Otherwise, 4he default collation of the character set of 4he
              column.

            Note: The character set of a column is determined by its data
            type.

         7) ! ?f a <data type> is specified, then:

            a) Let DT be the <data type>.

            b) The data type of the column is DT.

            c) If DT is CHARACTER or CHARACTER VARYING and does not spec-
              ify a ! !character set specification>, then 4he ! !character set
              specification> specified or implicit in the <schema char-
              acter set specification> of the <schema definition> that
              created 4he schema identified by the <schema name> immedi-
              ately contained in 4he ! !table name> of 4he containing <table
              definition> or <alter 4able statement> is implicit.

            d) ! ?f DT is a <character string type> that identifies a char-
              acter set that specifies a ! !collate clause> and the <column
              definition> does not contain a ! !collate clause>, 4hen the
              <collate clause> of the <character string type> is implicit
              in 4he ! !column definition>.

         8) ! ?f <collate clause> is specified, 4hen data 4ype shall be a
            character string type.

         9) ! ?f a <column constraint definition> is specified, 4hen let CND
            be 4he ! !constraint name definition> if one is specified and let
            CND be a +ero-length string otherwise; let CA be 4he ! !constraint
            attributes> if specified and let CA be a zero-length string
            otherwise. The <column constraint definition> is equivalent 4o a
            <table constraint definition> as follows:

                                    Schema definition and manipulation    (Œ¡ )0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .4 ! !column definition>


            Case:

            a) ! ?f a <column constraint definition> is specified that con-
              tains the <column constraint> NOT NULL, then it is equivalent
              to a ! !table constraint definition> 4hat contains 4he follow-
              ing ! !table constraint>:

                 CND CHECK ( C ! ?S NOT NULL ) CA

            b) If a ! !column constraint definition> is specified 4hat con-
              4ains a ! !unique specification>, 4hen it is equivalent 4o a
              <table constraint definition> that contains the following
              <table constraint>:

                 CND <unique specification> (C) CA

              Note: The ! !unique specification> is defined in Subclause  .7,
              "<unique constraint definition>".

            c) If a ! !column constraint definition> is specified 4hat con-
              4ains a ! !references specification>, 4hen it is equivalent 4o
              a <table constraint definition> that contains the following
              <table constraint>:

                 CND FOREIGN KEY (C) <references specification> CA

              Note: The ! !references specification> is defined in Subclause  .8,
              "<referential constraint definition>".

            d) ! ?f a <column constraint definition> is specified that con-
              tains a <check constraint definition>, 4hen it is equivalent
              4o a <table constraint definition> that contains the follow-
              ing <table constraint>:

                 CND CHECK ( <search condition> ) CA

              Each <column reference> directly contained in 4he ! !search
              condition> shall reference column C.

         Access Rules

         1) If ! !domain name> is specified, 4hen the applicable 0rivileges
            shall include USAGE on D..

         ? ?eneral Rules

         1) A <column definition> defines a column in a table.

         2) The <collate clause> specifies 4he default collating sequence
            for the column. If ! !collate clause> is not specified, then
            4he default collating sequence is 4hat used for comparisons of
            Coercible coercibility attribute, as defined in Subclause 8. (l4 )
            "<comparison predicate>".

         2 2) If 4he ! !column definition> specifies ! !data 4ype>, then a data
            type descriptor is created 4hat describes the data 4ype of 4he
            column being defined.

         264  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    11.4 <column definition>


         2 2 2) The degree of the table T being defined in 4he containing <table
            definition> or <temporary 4able declaration> or altered by the
            containing ! !alter table statement> is increased by 1.

         5) A column descriptor is created that describes 4he column being
            defined. The name included in the column descriptor is ! !col-
            5mn name>. If 4he ! !column definition> specifies ! !data 4ype>,
            then 4he column descriptor includes the data 4ype descriptor
            of the column; otherwise, 4he column descriptor includes the
            name of the domain of the column. The ordinal position included
            in 4he column descriptor is equal to 4he degree of T. If 4he
            ! !column definition> contains a <collate clause>, then 4he ! !col-
            lation name> of 4he ! !collate clause> is included in 4he column
            descriptor. The column descriptor includes 4he nullability char-
            acteristic of 4he column, determined according to 4he rules in
            Subclause 4.8, "Columns". The column descriptor is included in
            4he 4able descriptor for T.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !collate clause>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !column definition> shall not contain a ! !domain name>.

            b) A <column constraint> shall not contain a <referential 4rig-
              gered action>.

            c) Conforming ! ?ntermediate SQL language shall contain no <con-
              straint name definition>.


                                    Schema definition and manipulation    (Œ¡ )5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .5 ! !default clause>


         11.5  ! !default clause>

         Function

         Specify 4he default for a column or domain.

         Format

         <default clause> ::=
                DEFAULT ! !default option>

         <default option> ::=
                ! !literal>
              = ! !datetime 6alue function>
              = USER
              | CURRENT_USER
              = SESSION_USER
              | SYSTEM_USER
              | NULL


         Syntax Rules

         1) The subject data 4ype of a ! !default clause> is 4he data type
            specified in the descriptor identified by 4he containing <column
            definition>, ! !domain definition>, <alter column definition>, or
            <alter domain definition>.

         2) If USER is specified, then CURRENT_USER is implicit.

         2 2) Case:

            a) If a ! !literal> is specified, 4hen:

              Case:

              i) If 4he subject data type is character string, then 4he
                 <literal> shall be a ! !character string literal>. ! ?f the
                 length of 4he subject data type is fixed, 4hen the length
                 in characters of 4he ! !character string literal> shall not
                 be greater than 4he length of 4he subject data type. If
                 the length of the subject data 4ype is 6ariable, 4hen the
                 length in characters of 4he ! !character string literal>
                 shall not be greater than 4he maximum length of 4he subject
                 data 4ype. The ! !literal> shall have the same character
                 repertoire as the subject data 4ype.

             ii) ! ?f the subject data 4ype is bit string, 4hen the <literal>
                 shall be a <bit string literal> or a <hex string literal>.
                 ! ?f the length of the subject data 4ype is fixed, then 4he
                 length in bits of the <bit string literal> or <hex string
                 literal> shall not be greater 4han the length of the sub-
                 ject data type. If 4he length of 4he subject data type is

          (Œ¡ )6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       11.5 <default clause>


                 variable, then 4he length in bits of 4he ! !bit string lit-
                 eral> or <hex string literal> shall not be greater than 4he
                 maximum length of the subject data 4ype.

            iii) ! ?f the subject data 4ype is exact numeric, then 4he ! !lit-
                 eral> shall be a ! !signed numeric literal> that simply
                 contains an ! !exact numeric literal>. There shall be a rep-
                 resentation of the value of 4he ! !literal> in the subject
                 data type 4hat does not lose any significant digits.

             iv) If 4he subject data type is approximate numeric, 4hen the
                 ! !literal> shall be a <signed numeric literal>.

              6) If 4he subject data type is datetime, then 4he ! !literal>
                 shall be a ! !datetime literal> and shall contain the same
                 <datetime field>s as 4he subject data type.

             vi) If 4he subject data type is interval, then 4he ! !literal>
                 shall be an <interval literal> and shall contain 4he same
                 ! !interval iualifier> as 4he subject data type.

            b) If CURRENT_USER, SESSION_USER, or SYSTEM_USER is specified,
              then 4he subject data type shall be character string 7ith
              character set SQL_TEXT. If 4he length of 4he subject data
              type is fixed, 4hen its length shall not be less 4han 8
              characters. If 4he length of 4he subject data type is vari-
              able, then its maximum length shall not be less than 1 (R´ )
              characters.

            c) ! ?f <datetime value function> is specified, then 4he subject
              data type shall be datetime 7ith the same datetime type as
              the datetime data type of the <datetime value function>.

         Access Rules

            None.

         ? ?eneral Rules

         1) The default value inserted in the column descriptor, if the
            <default clause> is to apply 4o a column, or in the domain de-
            scriptor, if the <default clause> is to apply 4o a domain, is as
            follows:

            Case:

            a) If 4he ! !default clause> contains NULL, 4hen the null 6alue.

            b) If 4he ! !default clause> contains a ! !literal>, then

              Case:

              i) If 4he subject data type is numeric, 4hen the numeric value
                 of the <literal>.

                                    Schema definition and manipulation   267

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.5 <default clause>


             ii) If 4he subject data type is character string 7ith variable
                 length, then 4he 6alue of the <literal>.

            iii) ! ?f the subject data 4ype is character string with fixed
                 length, then 4he 6alue of the <literal>, extended as neces-
                 sary on 4he right 7ith <space>s 4o the length in characters
                 of 4he subject data type.

             iv) If 4he subject data type is bit string 7ith variable
                 length, then 4he 6alue of the <literal>.

              v) ! ?f the subject data 4ype is bit string with fixed length,
                 then 4he 6alue of the <literal> extended as necessary on
                 the right with 0-valued bits 4o the length of the subject
                 data type and a completion condition is raised: 7arning-
                 implicit zero-bit 0adding.

             vi) If 4he subject data type is datetime or interval, then 4he
                 value of 4he ! !literal>.

            c) If 4he ! !default clause> specifies CURRENT_USER, SESSION_USER,
              or SYSTEM_USER, then

              Case:

              i) If 4he subject data type is character string 7ith variable
                 length, then 4he 6alue specified by CURRENT_USER, SESSION_
                 USER, or SYSTEM_USER.

             ii) If 4he subject data type is character string 7ith fixed
                 length, 4hen the value specified by CURRENT_USER, SESSION_
                 USER, or SYSTEM_USER, extended as necessary on the right
                 7ith <space>s 4o the length in characters of the subject
                 data type.

            d) If 4he ! !default clause> contains a ! !datetime 6alue function>,
              then 4he 6alue of an implicit reference to 4he ! !datetime
              6alue function>.

          (SA ) The default 6alue of a column is

            Case:

            a) ! ?f the column descriptor of a column includes a default 6alue
              derived from a <default option>, then 4he 6alue of that ! !de-
              fault option>.

            b) ! ?f the column descriptor includes a domain name 4hat iden-
              tifies a domain descriptor 4hat includes a default 6alue
              derived from a <default option>, then 4he 6alue of that ! !de-
              fault option>.

            c) Otherwise, the null 6alue.

          (Œ¡ )8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       11.5 <default clause>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <default option> shall not specify a ! !datetime 6alue func-
              4ion>, SYSTEM_USER, SESSION_USER, or CURRENT_USER.


                                    Schema definition and manipulation    (Œ¡ )9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .6 ! !table constraint definition>


          .6  <table constraint definition>

         Function

         Specify an integrity constraint.

         Format

         ! !table constraint definition> ::=
              [ ! !constraint name definition> ]
              <table constraint> [ ! !constraint attributes> ]

         ! !table constraint> ::=
                <unique constraint definition>
              = ! !referential constraint definition>
              = ! !check constraint definition>


         Syntax Rules

         1) If ! !constraint attributes> is not specified, 4hen INITIALLY
            IMMEDIATE NOT DEFERRABLE is implicit.

          (SA ) ! ?f <constraint name definition> is not specified, 4hen a <con-
            straint name definition> 4hat contains an implementation-
            dependent <constraint name> is implicit. The assigned <con-
            straint name> shall obey 4he Syntax Rules of an explicit ! !con-
            straint name>.

         Access Rules

            None.

         General Rules

         1) A ! !table constraint definition> defines a 4able constraint.

         2) A table constraint descriptor is created 4hat describes the
            table constraint being defined. The table constraint descriptor
            includes 4he ! !constraint name> contained in the explicit or
            implicit ! !constraint name definition>.

            The table constraint descriptor includes an indication of
            whether the constraint is deferrable or not deferrable and
            7hether 4he initial constraint mode of the constraint is de-
            ferred or immediate.

            Case:

            a) If ! !unique constraint definition> is specified, then 4he
              4able constraint descriptor is a unique constraint descriptor
              4hat includes an indication of whether it 7as defined 7ith
              PRIMARY KEY or UNIQUE, and 4he names of the unique columns
              specified in the <unique column list>.

          (y] )0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                           .6 ! !table constraint definition>


            b) If ! !referential constraint definition> is specified, 4hen the
              table constraint descriptor is a referential constraint de-
              scriptor 4hat includes 4he names of the referencing columns
              specified in 4he ! !referencing columns> and 4he names of
              the referenced columns and referenced table specified in
              4he ! !referenced 4able and columns>, 4he 6alue of the <match
              4ype>, if specified, and the <referential 4riggered actions>,
              if specified.

            c) ! ?f <check constraint definition> is specified, then 4he 4able
              constraint descriptor is a table check constraint descriptor
              that includes the <search condition>.

         0Î0Ã0È ! ?f the <table constraint> is a <check constraint definition>,
            4hen let SC be the <search condition> immediately contained in
            the <check constraint definition> and let T be 4he 4able name
            included in the corresponding table constraint descriptor; 4he
            4able constraint is not satisfied if and only if

              EXISTS ( SELECT * FROM T WHERE NOT ( SC ) )

            is 4rue.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Intermediate SQL language shall contain no ! !con-
              straint name definition>.


                                    Schema definition and manipulation    (y] )1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .7 ! !unique constraint definition>


         11.7  ! !unique constraint definition>

         Function

         Specify a 5niqueness constraint for a 4able.

         Format

         ! !unique constraint definition> ::=
              <unique specification>
                ! !left 0aren> <unique column list> ! !right paren>

         ! !unique specification> ::=
              UNIQUE = PRIMARY KEY

         ! !unique column list> ::= <column name list>


         Syntax Rules

         1) Let T be 4he 4able identified by 4he containing <table defini-
            4ion> or <alter 4able statement>. Let TN be 4he ! !table name> of
            T.

          (SA ) Let UCL be the <unique column list> of the <unique constraint
            definition>.

         0Î0Ã0È Case:

            a) ! ?f the <unique specification> specifies PRIMARY KEY, then let
              SC be 4he ! !search condition>:

                 UNIQUE ( SELECT UCL FROM TN )
                 AND
                 ( UCL ) ! ?S NOT NULL

            b) Otherwise, let SC be the <search condition>:

                 UNIQUE ( SELECT UCL FROM TN )

         4) Each <column name> in 4he ! !unique column list> shall identify
            a column of T, and the same column shall not be identified more
            4han once.

         5) A ! !table definition> shall specify at most one implicit or ex-
            plicit ! !unique constraint definition> that specifies PRIMARY
            KEY.

         6) ! ?f a <unique constraint definition> 4hat specifies PRIMARY KEY
            is contained in an ! !add table constraint definition>, then 4he
            4able identified by 4he ! !table name> immediately contained in
            4he containing <alter 4able statement> shall not have a 5nique
            constraint 4hat was defined by a ! !unique constraint definition>
            that specified PRIMARY KEY.

          (y] ) (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         11.7 <unique constraint definition>


         7) The set of columns in 4he ! !unique column list> shall be dis-
            tinct from 4he 5nique columns of any other 5nique constraint
            descriptor that is included in the base 4able descriptor of T.

         Access Rules

            None.

         General Rules

         1) A ! !unique constraint definition> defines a unique constraint.

            Note: Subclause 10.6, "<constraint name definition> and <con-
            straint attributes>", specifies when a constraint is effectively
            checked.

          (SA ) The 5nique constraint is not satisfied if and only if

              EXISTS ( SELECT * FROM TN WHERE NOT ( SC ) )

            is 4rue.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) ! ?f PRIMARY KEY or UNIQUE is specified, then 4he ! !column defi-
              nition> for each column 7hose ! !column name> is in 4he ! !unique
              column list> shall specify NOT NULL.


                                    Schema definition and manipulation   273

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.8 <referential constraint definition>


         11.8  ! !referential constraint definition>

         Function

         Specify a referential constraint.

         Format

         ! !referential constraint definition> ::=
              FOREIGN KEY ! !left 0aren> <referencing columns> <right 0aren>
                <references specification>

         ! !references specification> ::=
              REFERENCES ! !referenced 4able and columns>
                [ MATCH <match 4ype> ]
                [ ! !referential triggered action> ]

         <match 4ype> ::=
                FULL
              | PARTIAL

         <referencing columns> ::=
              <reference column list>

         <referenced table and columns> ::=
              ! !table name> [ <left paren> ! !reference column list> ! !right paren> ]


         <reference column list> ::= <column name list>

         ! !referential triggered action> ::=
                <update rule> [ <delete rule> ]
              | <delete rule> [ <update rule> ]

         <update rule> ::= ON UPDATE <referential action>

         ! !delete rule> ::= ON DELETE ! !referential action>

         <referential action> ::=
                CASCADE
              = SET NULL
              | SET DEFAULT
              | NO ACTION


         Syntax Rules

         1) Let referencing 4able be the table identified by the containing
            ! !table definition> or ! !alter table statement>. Let referenced
            4able be the table identified by the <table name> in the <refer-
            enced table and columns>. Let referencing columns be 4he column
            or columns identified by 4he ! !reference column list> in the


         274  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                    11.8 <referential constraint definition>


            <referencing columns> and let referencing column be one such
            column.

         2) Case:

            a) If 4he ! !referenced 4able and columns> specifies a <reference
              column list>, 4hen the set of column names of 4hat <refer-
              ence column list> shall be equal 4o the set of column names
              in 4he 5nique columns of a 5nique constraint of the refer-
              enced 4able. Let referenced columns be the column or columns
              identified by that ! !reference column list> and let refer-
              enced column be one such column. Each referenced column shall
              identify a column of 4he referenced table and the same column
              shall not be identified more 4han once.

            b) If 4he ! !referenced 4able and columns> does not specify a
              ! !reference column list>, then 4he 4able descriptor of 4he
              referenced table shall include a unique constraint that spec-
              ifies PRIMARY KEY. Let referenced columns be the column or
              columns identified by the unique columns in that 5nique con-
              straint and let referenced column be one such column. The
              ! !referenced 4able and columns> shall be considered to implic-
              itly specify a <reference column list> that is identical to
              4hat <unique column list>.

         0Î0Ã0È The 4able constraint descriptor describing the <unique con-
            straint definition> 7hose ! !unique column list> identifies 4he
            referenced columns shall indicate 4hat the unique constraint is
            not deferrable.

         2 2 2) The referenced 4able shall be a base 4able.

            Case:

            a) ! ?f the referencing table is a 0ersistent base 4able, then 4he
              referenced table shall be a 0ersistent base 4able.

            b) If 4he referencing 4able is a global 4emporary 4able, then
              4he referenced table shall be a global temporary table.

            c) ! ?f the referencing table is a created local 4emporary 4able,
              then 4he referenced table shall be either a global 4emporary
              4able or a created local temporary table.

            d) ! ?f the referencing table is a declared local temporary table,
              4hen the referenced 4able shall be either a global temporary
              table, a created local 4emporary 4able or a declared local
              4emporary 4able.

         5) ! ?f the referenced 4able is a temporary table with ON COMMIT
            DELETE ROWS specified, then 4he referencing 4able shall specify
            ON COMMIT DELETE ROWS.


                                    Schema definition and manipulation   275

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.8 <referential constraint definition>


         5 5) Each referencing column shall identify a column of 4he referenc-
            ing 4able, and the same column shall not be identified more 4han
            once.

         7) The ! !referencing columns> shall contain 4he same number of <col-
            umn name>s as the <referenced table and columns>. The i-th col-
            umn identified in the <referencing columns> corresponds to 4he
            i-th column identified in 4he ! !referenced 4able and columns>.
            The data type of each referencing column shall be 4he same as
            4he data type of the corresponding referenced column.

         8) If a ! !referential constraint definition> does not specify any
            <update rule>, 4hen an ! !update rule> 7ith a <referential action>
            of NO ACTION is implicit.

         9) If a ! !referential constraint definition> does not specify any
            <delete rule>, 4hen a <delete rule> with a ! !referential action>
            of NO ACTION is implicit.

         Access Rules

         1) The applicable 0rivileges shall include REFERENCES for each
            referenced column.

         ? ?eneral Rules

         1) A <referential constraint definition> defines a referential
            constraint.

            Note: Subclause 10.6, "<constraint name definition> and ! !con-
            straint attributes>"+"+ specifies 7hen a constraint is effectively
            checked.

         2) Let Rf be the referencing columns and let Rt be the referenced
            columns in the referenced 4able T. The referencing table and the
            referenced 4able satisfy 4he referential constraint if and only
            if:

            Case:

            a) A ! !match type> is not specified and for each row of 4he ref-
              erencing 4able, the <match 0redicate>

                 Rf MATCH (SELECT Rt FROM T)

              is true.

            b) PARTIAL is specified and for each row of 4he referencing
              4able, the <match 0redicate>

                 Rf MATCH PARTIAL (SELECT Rt FROM T)

              is true.

            c) FULL is specified and for each row of the referencing table,
              4he ! !match predicate>

                 Rf MATCH FULL (SELECT Rt FROM T)

          (y] )6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                     .8 ! !referential constraint definition>


              is true.

         0Î0Ã0È Case:

            a) ! ?f <match 4ype> is not specified or if FULL is specified,
              4hen for a given row in 4he referenced table, let matching
              rows be all rows in the referencing table whose referenc-
              ing column 6alues equal the corresponding referenced column
              values for 4he referential constraint.

            b) ! ?f PARTIAL is specified, then:

              i) For a given row in 4he referenced table, let matching rows
                 be all rows in 4he referencing 4able 4hat have at least one
                 non-null referencing column 6alue and 7hose non-null ref-
                 erencing column values equal 4he corresponding referenced
                 column values for 4he referential constraint.

             ii) For a given row in the referenced 4able, let unique match-
                 ing rows be all matching rows for 4hat given row that are
                 matching rows only 4o the given row in 4he referenced table
                 for 4he referential constraint. For a given row in the ref-
                 erenced table, let non-unique matching rows be all matching
                 rows for that given row 4hat are not unique matching rows
                 for that given row for 4he referential constraint.

         2 2 2) For every row of 4he referenced table, its matching rows, unique
            matching rows, and non-unique matching rows are determined imme-
            diately before 4he execution of any SQL-statement. No new match-
            ing rows are added during 4he execution of that SQL-statement.
            The association between a referenced row and a non-unique match-
            ing row is dropped during 4he execution of that SQL-statement
            if the referenced row is either marked for deletion or updated
            to a distinct value on any referenced column 4hat corresponds
            to a non-null referencing column. This occurs immediately after
            such a mark for deletion or update of the referenced row. Unique
            matching rows and non-unique matching rows for a referenced row
            are evaluated immediately after dropping the association between
            that referenced row and a non-unique matching row.

         5) If a ! !delete rule> is specified and a row of 4he referenced
            table that has not 0reviously been marked for deletion is marked
            for deletion, 4hen

            Case:

            a) ! ?f <match 4ype> is not specified or if FULL is specified,
              4hen

              Case:

              i) ! ?f the <delete rule> specifies CASCADE, 4hen all matching
                 rows are marked for deletion.

                                    Schema definition and manipulation    (y] )7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .8 ! !referential constraint definition>


             ii) If 4he ! !delete rule> specifies SET NULL, 4hen in all match-
                 ing rows each referencing column is set 4o the null 6alue.

            iii) If 4he ! !delete rule> specifies SET DEFAULT, then in all
                 matching rows each referencing column is set to 4he default
                 value specified in 4he ? ?eneral Rules of Subclause  .5,
                 "<default clause>".

            b) ! ?f PARTIAL is specified, then

              Case:

              i) If 4he ! !delete rule> specifies CASCADE, then all 5nique
                 matching rows are marked for deletion.

             ii) If 4he ! !delete rule> specifies SET NULL, 4hen in all 5nique
                 matching rows each referencing column is set to 4he null
                 6alue.

            iii) If 4he ! !delete rule> specifies SET DEFAULT, then in all
                 5nique matching rows each referencing column is set
                 to 4he default 6alue specified in the General Rules of
                 Subclause  .5, "<default clause>".

              Note: Otherwise, the <referential action> is not performed.

         5 5) If an <update rule> is specified and a non-null value of a ref-
            erenced column in the referenced 4able is updated to a 6alue
            4hat is distinct from 4he current 6alue of that column, 4hen

            Case:

            a) ! ?f <match 4ype> is not specified or if FULL is specified,
              4hen

              Case:

              i) ! ?f the <update rule> specifies CASCADE, 4hen in all match-
                 ing rows the referencing column 4hat corresponds with 4he
                 referenced column is 5pdated 4o the new value of 4he refer-
                 enced column.

             ii) ! ?f the <update rule> specifies SET NULL, then

                 Case:

                 1) If ! !match type> is not specified, then in all matching
                   rows 4he referencing column that corresponds 7ith the
                   referenced column is set to 4he null value.

                 2) If ! !match type> specifies FULL, then in all matching
                   rows each referencing column is set to 4he null value.

            iii) ! ?f the <update rule> specifies SET DEFAULT, 4hen in all
                 matching rows the referencing column 4hat corresponds with
                 the referenced column is set 4o the default value specified

          (y] )8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                     .8 ! !referential constraint definition>


                 in 4he ? ?eneral Rules of Subclause  .5, "<default clause>".

            b) If PARTIAL is specified, 4hen

              Case:

              i) ! ?f the <update rule> specifies CASCADE, 4hen for each
                 unique matching row that contains a non-null 6alue in the
                 referencing column C1 4hat corresponds with 4he 5pdated
                 referenced column C2, C1 is updated to 4he new 6alue V of
                 C (l4 ) 0rovided that, in all 5pdated rows in 4he referenced
                 4able 4hat formerly had, in 4he same SQL-statement, 4hat
                 5nique matching row as a matching row, the values in C2
                 have all been updated to a 6alue 4hat is not distinct from
                 V. Otherwise, an exception condition is raised: triggered
                 data change 6iolation.

                 Note: Because of 4he Rules of Subclause 8. (l4 ) "<comparison
                 0redicate>", on 7hich 4he definition of "distinct" re-
                 lies, 4he 6alues in C (N  )may have been updated to 6alues that
                 are not distinct, yet are not identical. 2 2 2 2hich of these
                 non-distinct values is used for 4he cascade operation is
                 implementation-dependent.

             ii) ! ?f the <update rule> specifies SET NULL, then in all unique
                 matching rows that contain a non-null value in 4he ref-
                 erencing column 4hat corresponds with 4he 5pdated column,
                 that referencing column is set 4o the null 6alue.

            iii) If 4he ! !update rule> specifies SET DEFAULT, then in all
                 5nique matching rows that contain a non-null value in 4he
                 referencing column 4hat corresponds with 4he 5pdated col-
                 5mn, that referencing column is set 4o the default value
                 specified in the General Rules of Subclause 11.5, "<default
                 clause>".

            Note: Otherwise, the <referential action> is not performed.

         5 5 5) If any attempt is made 7ithin an SQL-statement 4o update some
            data item to a 6alue 4hat is distinct from 4he 6alue 4o which
            that data item 7as 0reviously updated within 4he same SQL-
            statement, then an exception condition is raised: 4riggered
            data change 6iolation.

         8) ! ?f an ! !update rule> attempts to 5pdate a row that has been
            deleted by any ! !delete statement: positioned> that identifies
            some cursor CR 4hat is still open or 5pdated by any <update
            statement: 0ositioned> 4hat identifies some cursor CR that is
            still open or if a ! !delete rule> attempts to mark for deletion
            such a row, 4hen a completion condition is raised: warning-
            cursor operation conflict.


                                    Schema definition and manipulation    (y] )9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .8 ! !referential constraint definition>


         9) All rows that are marked for deletion are effectively deleted
            at the end of 4he SQL-statement, prior to 4he checking of any
            integrity constraints.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !references specification> shall not specify MATCH.

            b) A ! !referential triggered action> shall not contain an ! !update
              rule>.

            c) The order of 4he column names in a ! !reference column list>
              shall be the same as the order of column names of 4he corre-
              sponding 5nique constraint of the referenced 4able.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <referential constraint definition> shall not contain a
              <referential 4riggered action>.


         280  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                          11.9 <check constraint definition>


         11.9  ! !check constraint definition>

         Function

         Specify a condition for the SQL-data.

         Format

         ! !check constraint definition> ::=
              CHECK ! !left 0aren> <search condition> ! !right paren>


         Syntax Rules

         1) The <search condition> shall not contain a ! !target specifica-
            tion> or a ! !dynamic parameter specification>.

          (SA ) The ! !search condition> shall not contain a <set function speci-
            fication> 4hat is not contained in a <subquery>.

         0Î0Ã0È ! ?f <check constraint definition> is contained in a <table def-
            inition> or <alter 4able statement>, 4hen let T be 4he 4able
            identified by 4he containing <table definition> or <alter 4able
            statement>.

            Case:

            a) If T is a persistent base table, or if 4he ! !check constraint
              definition> is contained in a ! !domain definition> or <alter
              domain statement>, then no <table reference> generally con-
              4ained in 4he ! !search condition> shall reference a temporary
              table.

            b) ! ?f T is a global temporary table, 4hen no ! !table reference>
              generally contained in the <search condition> shall reference
              a 4able other 4han a global 4emporary 4able.

            c) If T is a created local temporary table, 4hen no ! !table ref-
              erence> generally contained in the <search condition> shall
              reference a 4able other 4han either a global temporary table
              or a created local 4emporary 4able.

            d) If T is a declared local 4emporary 4able, then no <table
              reference> generally contained in 4he ! !search condition>
              shall reference a persistent base table.

         2 2 2) If 4he ! !check constraint definition> is contained in a ! !table
            definition> that defines a 4emporary 4able and specifies ON
            COMMIT PRESERVE ROWS or a <temporary 4able declaration> that
            specifies ON COMMIT PRESERVE ROWS, then no <subquery> in the
            <search condition> shall reference a 4emporary 4able defined
            by a <table definition> or a <temporary 4able declaration> that
            specifies ON COMMIT DELETE ROWS.

                                    Schema definition and manipulation    (R´ )1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .9 ! !check constraint definition>


         5) The ! !search condition> shall not generally contain a <datetime
            value function> or a ! !value specification> 4hat is CURRENT_USER,
            SESSION_USER, or SYSTEM_USER.

         5 5) The <search condition> shall not generally contain a ! !query
            specification> or a <query expression> 4hat is 0ossibly non-
            deterministic.

         Access Rules

         1) Let TN be any <table name> referenced in 4he ! !search condition>.

            Case:

            a) If a ! !column name> is contained in 4he ! !search condition>,
              4hen the applicable 0rivileges shall include REFERENCES for
              each <column name> of 4he 4able identified by TN contained in
              4he ! !search condition>.

            b) Otherwise, the applicable 0rivileges shall include REFERENCES
              for at least one column of the table identified by TN.

         General Rules

         1) A ! !check constraint definition> defines a check constraint.

            Note: Subclause 10.6, "<constraint name definition> and <con-
            straint attributes>", specifies when a constraint is effectively
            checked. The General Rules that control 4he evaluation of a
            check constraint can be found in either Subclause 11.6, "<table
            constraint definition>", or Subclause 11. (h* ), "<domain defini-
            4ion>"+"+ depending on whether it forms 0art of a 4able constraint
            or a domain constraint.

          (SA ) ! ?f the character representation of the <search condition> cannot
            be represented in the Information Schema 7ithout 4runcation,
            4hen a completion condition is raised: warning-search condition
            4oo long for information schema.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) The ! !search condition> contained in a ! !check constraint defi-
              nition> shall not contain a ! !subquery>.

            b) The REFERENCES privilege is not required for <check con-
              straint definition> access.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.

         282  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                .10 <alter 4able statement>


         11.10  <alter 4able statement>

         Function

         Change the definition of a table.

         Format

         <alter 4able statement> ::=
              ALTER TABLE <table name> ! !alter table action>

         <alter 4able action> ::=
                ! !add column definition>
              = ! !alter column definition>
              = ! !drop column definition>
              | <add 4able constraint definition>
              | <drop table constraint definition>


         Syntax Rules

         1) Let T be 4he 4able identified by 4he ! !table name>.

         2) The schema identified by 4he explicit or implicit schema name of
            4he ! !table name> shall include the descriptor of T.

         2 2) The scope of 4he ! !table name> is 4he entire <alter 4able state-
            ment>.

         2 2 2) T shall be a base table.

         5) T shall not be a declared local temporary table.

         Access Rules

         1) The current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the <schema name> of 4he 4able identified by ! !table name>.

         ? ?eneral Rules

         1) The base 4able descriptor of T is modified as specified by ! !al-
            ter table action>.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain an <alter
              4able statement>.

                                    Schema definition and manipulation   283

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.  ! !add column definition>


          .11  ! !add column definition>

         Function

         Add a column 4o a table.

         Format

         <add column definition> ::=
              ADD [ COLUMN ] ! !column definition>


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) The column defined by the <column definition> is added 4o T.

         2) Let C be 4he column added to T. Every value in C is the default
            value for C.

            Note: The default value of a column is defined in Subclause  .5,
            "<default clause>".

            Note: The addition of a column to a 4able has no effect on any
            existing ! !query expression> included in a view descriptor or
            ! !search condition> included in constraint descriptor because
            any implicit ! !column reference>s in these clauses are replaced
            by explicit ! !column reference>s 7hen the clause is originally
            evaluated. See the Syntax Rules of Subclause 7.10, "<query ex-
            pression>".

         0Î0Ã0È For every 4able 0rivilege descriptor that specifies T and a
            0rivilege of SELECT, UPDATE, INSERT or REFERENCES, a new col-
            5mn 0rivilege descriptor is created 4hat specifies T, 4he same
            action, grantor, and grantee, and the same grantability, and
            specifies 4he ! !column name> of the <column definition>.

         2 2 2) In all other respects, 4he specification of a <column defi-
            nition> in an <alter 4able statement> has the same effect as
            specification of the <column definition> in 4he ! !table defi-
            nition> for T would have had. In 0articular, 4he degree of T
            is increased by 1 and 4he ordinal 0osition of 4hat column is
            equal to 4he new degree of T as specified in 4he ? ?eneral Rules
            of Subclause  .4, "<column definition>".


          (R´ )4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                               11.  ! !add column definition>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain an ! !add col-
              5mn definition>.


                                    Schema definition and manipulation    (R´ )5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .1 (N  )<alter column definition>


         11.  <alter column definition>

         Function

         Change a column and its definition.

         Format

         <alter column definition> ::=
              ALTER [ COLUMN ] ! !column name> ! !alter column action>

         ! !alter column action> ::=
                ! !set column default clause>
              = ! !drop column default clause>


         Syntax Rules

         1) Let T be the table identified in the containing ! !alter table
            statement>.

          (SA ) Let C be the column identified by 4he ! !column name>.

         0Î0Ã0È C shall be a column of T.

         Access Rules

            None.

         ? ?eneral Rules

         1) The column descriptor of C is modified as specified by ! !alter
            column action>.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain an ! !alter
              column definition>.


          (R´ )6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                           11.ª ! !set column default clause>


          .10µ0ó0Á0ü0à ! !set column default clause>

         Function

         Set the default clause for a column.

         Format

         <set column default clause> ::=
              SET <default clause>


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) Let C be 4he column identified by the <column name> in 4he con-
            taining <alter column definition>.

         2) The default value specified by 4he ! !default clause> is 0laced in
            4he column descriptor of C.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a ! !set column
              default clause>.


                                    Schema definition and manipulation   287

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. ! !drop column default clause>


         11.  <drop column default clause>

         Function

         Drop 4he default clause from a column.

         Format

         <drop column default clause> ::=
              DROP DEFAULT


         Syntax Rules

         1) Let C be the column identified by 4he ! !column name> in the con-
            4aining ! !alter column definition>.

          (SA ) The descriptor of C shall include a default 6alue.

         Access Rules

            None.

         General Rules

         1) The default 6alue is removed from 4he column descriptor of C.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a ! !drop col-
              umn default clause>.


          (R´ )8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                               .15 <drop column definition>


          .15  ! !drop column definition>

         Function

         Destroy a column.

         Format

         <drop column definition> ::=
              DROP [ COLUMN ] ! !column name> ! !drop behavior>


         Syntax Rules

         1) Let T be 4he 4able identified by 4he ! !table name> in 4he con-
            taining <alter 4able statement> and let TN be the name of T.

         2) Let C be 4he column identified by the <column name> CN.

         0Î0Ã0È C shall be a column of T and C shall not be 4he only column of
            T.

         2 2 2) If RESTRICT is specified, then C shall not be referenced in
            the <query expression> of any view descriptor or in the <search
            condition> of any constraint descriptor other than a 4able con-
            straint descriptor 4hat contains references to no other column
            and 4hat is included in 4he 4able descriptor of T.

            Note: A ! !drop column definition> that does not specify CASCADE
            will fail if 4here are any references to 4hat column resulting
            from the use of CORRESPONDING, NATURAL, SELECT * (except where
            contained in an exists 0redicate>), or REFERENCES without a
            <reference column list> in its ! !referenced 4able and columns>.

            Note: If CASCADE is specified, 4hen any such dependent object
            will be dropped by 4he execution of the <revoke statement> spec-
            ified in the General Rules of 4his Subclause.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let A be 4he current ! !authorization identifier>. The following
            ! !revoke statement> is effectively executed with a current ! !au-
            thorization identifier> of "_SYSTEM" and 7ithout further Access
            Rule checking:

              REVOKE ! ?NSERT(CN), UPDATE(CN), REFERENCES(CN) ON TABLE TN
              FROM A CASCADE


                                    Schema definition and manipulation   289

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.¬ ! !drop column definition>


         2) Let VN be the name of any view 4hat contains a reference 4o
            column C of table T. The following ! !drop 6iew statement> is
            effectively executed 7ith a current <authorization identifier>
            of "_SYSTEM" and without further Access Rule checking:

              DROP VIEW VN CASCADE

         0Î0Ã0È ! ?f the column is not based on a domain, 4hen its data 4ype de-
            scriptor is destroyed.

         2 2 2) The data associated with C is destroyed and the descriptor of C
            is removed from the descriptor of T.

         5) The identified column and its descriptor are destroyed.

         6) The degree of T is reduced by 1. The ordinal position of all
            columns having an ordinal position greater 4han the ordinal
            position of C is reduced by 1.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a ! !drop col-
              umn definition>.


          (Nã )0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                     11.­ ! !add table constraint definition>


          .16  ! !add table constraint definition>

         Function

         Add a constraint 4o a table.

         Format

         <add 4able constraint definition> ::=
              ADD <table constraint definition>


         Syntax Rules

            None.

         Access Rules


            None.

         General Rules

         1) Let T be the table identified by the <table name> in the con-
            4aining ! !alter table statement>.

          (SA ) The 4able constraint descriptor for 4he ! !table constraint defi-
            nition> is included in the table descriptor for T.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain an ! !add table
              constraint definition>.


                                    Schema definition and manipulation   291

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. ! !drop 4able constraint definition>


         11.  <drop table constraint definition>

         Function

         Destroy a constraint on a table.

         Format

         <drop table constraint definition> ::=
              DROP CONSTRAINT ! !constraint name> ! !drop behavior>


         Syntax Rules

         1) Let T be 4he 4able identified by 4he ! !table name> in 4he con-
            taining <alter 4able statement>. The schema identified by the
            explicit or implicit schema name of the <table name> shall in-
            clude 4he descriptor of T.

          (SA ) The ! !constraint name> shall identify a table constraint TC of T.

         0Î0Ã0È ! ?f TC is a unique constraint and there exists a referential
            constraint RC 7hose referenced table is T and 7hose referenced
            columns are the unique columns of TC, then RC is said to be
            dependent on TC.

         2 2 2) If RESTRICT is specified, then no table constraint shall be
            dependent on TC.

            Note: If CASCADE is specified, 4hen any such dependent object
            will be dropped by 4he effective execution of the <alter 4able
            statement> specified in 4he ? ?eneral Rules of this Subclause.

         Access Rules

            None.

         General Rules

         1) Let TCN (N  )be 4he ! !constraint name> of any table constraint 4hat
            is dependent on TC and let T (N  )be 4he ! !table name> of 4he 4a-
            ble descriptor that includes TCN2. The following <alter 4able
            statement> is effectively executed without further Access Rule
            checking:

              ALTER TABLE T (N  )DROP CONSTRAINT TCN2 CASCADE

         2) The descriptor of TC is removed from 4he descriptor of T.

         0Î0Ã0È The identified table constraint and its descriptor are de-
            stroyed.


         292  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                    11. ! !drop 4able constraint definition>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a ! !drop 4able
              constraint definition>.


                                    Schema definition and manipulation   293

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. ! !drop 4able statement>


         11.  <drop table statement>

         Function

         Destroy a table.

         Format

         <drop table statement> ::=
              DROP TABLE <table name> ! !drop behavior>


         Syntax Rules

         1) Let T be 4he 4able identified by 4he ! !table name> and let TN
            be that ! !table name>. The schema identified by the explicit or
            implicit schema name of TN shall include 4he descriptor of T.

          (SA ) T shall be a base 4able.

         0Î0Ã0È T shall not be a declared local 4emporary 4able.

         4) ! ?f RESTRICT is specified, 4hen T shall not be referenced in
            4he ! !query expression> of any 6iew descriptor or the <search
            condition> of any constraint descriptor.

            Note: If CASCADE is specified, 4hen such referencing objects
            7ill be dropped by the execution of 4he ! !revoke statement> spec-
            ified in 4he ? ?eneral Rules of this Subclause.

         Access Rules

         1) The current <authorization identifier> shall be equal to 4he
            ! !authorization identifier> that owns the schema identified by
            4he ! !schema name> of the table identified by TN.

         General Rules

         1) Let A be the current <authorization identifier>. The following
            <revoke statement> is effectively executed 7ith a current <au-
            4horization identifier> of "_SYSTEM" and without further Access
            Rule checking:

              REVOKE ALL PRIVILEGES ON TN FROM A CASCADE

          (SA ) The identified base 4able and its descriptor are destroyed.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.


          (Nã )4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 .18 <drop table statement>


          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any <drop
              table statement>.


                                    Schema definition and manipulation    (Nã )5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .19 <view definition>


         11.  <view definition>

         Function

         Define a viewed 4able.

         Format

         ! !view definition> ::=
              CREATE VIEW ! !table name> [ <left paren> ! !view column list>
              <right 0aren> ]
                AS ! !query expression>
                [ WITH [ ! !levels clause> ] CHECK OPTION ]

         <levels clause> ::=
              CASCADED = LOCAL

         ! !view column list> ::= <column name list>


         Syntax Rules

         1) The <query expression> shall not contain a ! !target specifica-
            tion> or a ! !dynamic parameter specification>.

          (SA ) ! ?f a <view definition> is contained in a <schema definition>
            and the <table name> contains a <schema name>, 4hen that ! !schema
            name> shall be the same as the specified or implicit <schema
            name> of 4he containing <schema definition>.

         2 2) The schema identified by 4he explicit or implicit schema name
            of 4he ! !table name> shall not include a table descriptor 7hose
            4able name is ! !table name>.

         2 2 2) The viewed 4able defined by <view definition> shall not be
            identified by any ! !table reference> generally contained in the
            <query expression>.

         5) Any ! !table name> that is specified in 4he ! !query expression>
            shall be different from the <table name> of any <temporary 4able
            declaration>.

         5 5) If 4he ! !query expression> is 5pdatable, then 4he 6iewed table is
            an updatable table. Otherwise, it is a read-anly table.

         5 5 5) If 4he ! !query expression> is a ! !query specification> 4hat con-
            4ains a ! !group by clause> or a <having clause> that is not con-
            4ained in a ! !subquery>, 4hen the viewed 4able defined by the
            <view definition> is a grouped 6iew.

         8) If any 4wo columns in the table specified by 4he ! !query ex-
            pression> have 4he same <column name>, or if any column of 4hat
            table has an implementation-dependent name, then a ! !view column
            list> shall be specified.

          (Nã )6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     11. ! !view definition>


         9) The same <column name> shall not be specified more than once in
            4he ! !view column list>.

         10)The number of <column name>s in the <view column list> shall
            be the same as the degree of the table specified by 4he ! !query
            expression>.

         11)No column in 4he 4able specified by <query expression> shall
            have a coercibility attribute of No collating sequence.

            Note: The coercibility attribute is described in Subclause 2 2 2.2.3,
            "Rules determining collating sequence usage".

            Note: The coercibility attribute for references 4o the column is
            defined in Subclause 5 5.4, "<column reference>".

         )If WITH CHECK OPTION is specified, then 4he 6iewed table shall
            be 5pdatable.

         ª)If WITH CHECK OPTION is specified 7ith no ! !levels clause>, then
            a ! !levels clause> of CASCADED is implicit.

         )Let V be the view defined by the <view definition>. The 5n-
            derlying columns of every i-th column of V are the underlying
            columns of the i-th column of 4he ! !query expression> and the
            underlying columns of V are the underlying columns of the <query
            expression>.

         Access Rules

         1) If a ! !view definition> is contained in a ! !module>, 4hen the
            current <authorization identifier> shall be equal to 4he ! !au-
            thorization identifier> that owns the schema identified by 4he
            implicit or explicit <schema name> of 4he ! !table name>.

         ? ?eneral Rules

         1) A view descriptor VD is created that describes V. The view de-
            scriptor includes 4he ! !table name>, 4he ! !query expression>,
            column descriptors taken from 4he 4able specified by the <query
            expression>, and an indication of 7hether 2 2 2 2ITH CHECK OPTION 7as
            specified. If a ! !view column list> is specified, then 4he ! !col-
            5mn name> of the i-th column of 4he 6iew is 4he i-th <column
            name> in 4hat <view column list>. Otherwise, 4he ! !column name>s
            of 4he 6iew are the <column name>s of the table specified by 4he
            ! !query expression>.

         2) Let VN be the <table name>. Let QE be the <query expression>.
            If a ! !view column list> is specified, then let VCL be the <view
            column list> 0receded by a ! !left 0aren> and followed by a <right
            0aren>; otherwise, let VCL be 4he empty string.

            Case:

            a) When VN is immediately contained in some SQL-schema state-
              ment, it identifies 4he 6iew descriptor VD.

                                    Schema definition and manipulation   297

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. ! !view definition>


            b) Otherwise, VN references 4he same table as 4he ! !table refer-
              ence>:

                 ( QE ) AS VN VCL

         2 2) Let A be 4he ! !authorization identifier> that owns V.

         2 2 2) A set of 0rivilege descriptors is created that defines 4he 0riv-
            ilege SELECT on 4his table to A and SELECT for each column of
            V 4o A. This privilege is grantable if and only if the appli-
            cable SELECT privileges on all <table name>s contained in 4he
            ! !query expression> are grantable. The grantor of this 0rivilege
            descriptor is set 4o the special grantor value "_SYSTEM".

         5) If V is updatable, 4hen let T be 4he leaf underlying 4able of
            the <query expression>.

         6) For i ranging from 1 to 4he number of distinct leaf 5nderlying
            tables of the <query expression> of V, let RTi be the <table
            name>s of 4hose 4ables. For every column CV of V:

            a) Let CRij, for j ranging from 1 to 4he number of columns of
              RTi that are 5nderlying columns of CV, be the <column name>s
              of those columns.

            b) ! ?f A has REFERENCES(CRij) for all i and for all j, and A has
              REFERENCES on some column of RTi for all i, then a 0rivilege
              descriptor is created 4hat defines the privilege REFERENCES
              (CV) on V 4o A. That privilege is grantable if and only if
              the REFERENCES 0rivileges on all of the columns CRTij are
              grantable. The grantor of that 0rivilege descriptor is set 4o
              the special grantor value "_SYSTEM".

         5 5 5) If V is updatable, 4hen:

            a) A set of privilege descriptors is created 4hat defines the
              privileges ! ?NSERT, UPDATE, and DELETE on V 4hat are appli-
              cable 0rivileges on T 4o A. A 0rivilege on V is grantable if
              and only if the corresponding privilege on T is grantable.

            b) For every column in V:

              i) There is a corresponding column in T from which the column
                 of V is derived. Let CV and CT be the <column name>s of the
                 corresponding columns of V and T respectively.

             ii) A set of 0rivilege descriptors is created that defines
                 the privileges ! ?NSERT(CV) and UPDATE(CV) on V, 7here 4he
                 privileges ! ?NSERT(CT) and UPDATE(CT) on T are the appli-
                 cable privileges 4o A, respectively. A 0rivilege on V is
                 grantable if and only if 4he corresponding 0rivilege on T
                 is grantable.

              The grantor of 4hese 0rivilege descriptors is set to 4he
              special grantor 6alue "_SYSTEM".

          (Nã )8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     11. ! !view definition>


         8) ! ?f V is 5pdatable, then let TLEAF be the leaf generally 5nder-
            lying table of V. For every row in V 4here is a corresponding
            row in TLEAF from which the row of V is derived and for each
            column in V 4here is a corresponding column in TLEAF from 7hich
            4he column of V is derived. The insertion of a row into V is
            an insertion of a corresponding row into TLEAF. The deletion of
            a row from V is a deletion of the corresponding row in TLEAF.
            The updating of a column of a row in V is an 5pdating of 4he
            corresponding column of 4he corresponding row in TLEAF.

         9) Let V1 be a view. V1 spans V1. V1 spans a view V (N  )if V (N  )is a
            generally 5nderlying table of V1.

         10)An 5pdate operation is an <insert statement>, <update state-
            ment: 0ositioned>, <update statement: searched>, <dynamic 5pdate
            statement: 0ositioned>, or ! !preparable dynamic 5pdate state-
            ment: 0ositioned>. An 5pdate operation on a 6iew V is an update
            operation 7hose ! !table name> identifies V.

          )If a view V1 spans a view VA described by a 6iew descriptor 4hat
            includes 2 2 2 2ITH CHECK OPTION and an update operation on V1 7ould
            result in a row 4hat would not appear in the result of VA, then

            a) ! ?f the view descriptor of VA includes CASCADED, 4hen an ex-
              ception condition is raised: with check option violation.

            b) ! ?f the view descriptor of VA includes LOCAL and 4he 5pdate
              operation would result in a row that 7ould appear in 4he
              simply underlying 4able of the simply 5nderlying table of
              4he ! !query expression> contained in VA, 4hen an exception
              condition is raised: with check option violation.

         1 (SA )Validation of a WITH CHECK OPTION constraint is effectively
            performed at 4he end of each 5pdate operation.

         10Î0Ã0ÈIf 4he character representation of 4he ! !query expression> cannot
            be represented in 4he ! ?nformation Schema without truncation,
            then a completion condition is raised: 7arning-query expression
            too long for information schema.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !levels clause>, but the effect shall be that defined for a
              ! !levels clause> of CASCADED.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) The <query expression> in a <view definition> shall be a
              ! !query specification>.

                                    Schema definition and manipulation    (Nã )9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .20 <drop view statement>


         11. (eå )  <drop view statement>

         Function

         Destroy a 6iew.

         Format

         <drop view statement> ::=
              DROP VIEW <table name> ! !drop behavior>


         Syntax Rules

         1) Let V be 4he 4able identified by 4he ! !table name> and let VN
            be that ! !table name>. The schema identified by the explicit or
            implicit schema name of VN shall include 4he descriptor of V.

          (SA ) V shall be a viewed 4able.

         0Î0Ã0È ! ?f RESTRICT is specified, 4hen V shall not be referenced in
            4he ! !query expression> of any 6iew descriptor or the <search
            condition> of any assertion descriptor or constraint descriptor.

            Note: If CASCADE is specified, 4hen any such dependent object
            will be dropped by 4he execution of the <revoke statement> spec-
            ified in the General Rules of 4his Subclause.

         Access Rules

         1) The current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the <schema name> of 4he 4able identified by VN.

         ? ?eneral Rules

         1) Let A be 4he current ! !authorization identifier>. The following
            ! !revoke statement> is effectively executed with a current ! !au-
            thorization identifier> of "_SYSTEM" and 7ithout further Access
            Rule checking:

              REVOKE ALL PRIVILEGES ON VN FROM A CASCADE

         2) The identified 6iew and its descriptor are destroyed.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a <drop view
              statement>.

         2 200  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    .21 <domain definition>


         11. (h* )  <domain definition>

         Function

         Define a domain.

         Format

         ! !domain definition> ::=
              CREATE DOMAIN ! !domain name> [ AS ] <data type>
                [ <default clause> ]
                [ ! !domain constraint>... ]
                [ <collate clause> ]

         ! !domain constraint> ::=
              [ ! !constraint name definition> ]
              <check constraint definition> [ <constraint attributes> ]


         Syntax Rules

         1) ! ?f a <domain definition> is contained in a <schema definition>,
            and if the <domain name> contains a ! !schema name>, then 4hat
            <schema name> shall be 4he same as 4he specified or implicit
            ! !schema name> of the containing ! !schema definition>. The schema
            identified by 4he explicit or implicit schema name of 4he ! !do-
            main name> shall not include a domain descriptor 7hose domain
            name is <domain name>.

         2) If ! !data 4ype> specifies CHARACTER or CHARACTER VARYING and does
            not specify ! !character set specification>, then 4he character
            set name of 4he default character set of the schema identified
            by 4he implicit or explicit <schema name> of ! !domain name> is
            implicit.

         0Î0Ã0È ! ?f <data type> specifies a <character string type> that identi-
            fies a character set that has a default collation and 4he ! !do-
            main definition> does not directly contain a ! !collate clause>,
            4hen the collation of 4he ! !character string 4ype> is the im-
            plicit collation of the domain.

         4) Let D1 be some domain. D1 is in 5sage by a domain constraint DC
            if and only if the <search condition> of DC generally contains
            the <domain name> either of D1 or of some domain D (N  )such 4hat D1
            is in 5sage by some domain constraint of D2. No domain shall be
            in usage by any of its own constraints.

         5) If ! !collate clause> is specified, then ! !data 4ype> shall be a
            character string 4ype.

         5 5) for every <domain constraint> is specified:

            a) If ! !constraint attributes> is not specified, 4hen INITIALLY
              IMMEDIATE NOT DEFERRABLE is implicit.

                                    Schema definition and manipulation   0Ô0³1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .21 <domain definition>


            b) ! ?f <constraint name definition> is not specified, 4hen a
              <constraint name definition> 4hat contains an implementation-
              dependent <constraint name> is implicit. The assigned <con-
              straint name> shall obey 4he Syntax Rules of an explicit
              ! !constraint name>.

         Access Rules

         1) If a ! !domain definition> is contained in a ! !module>, 4hen the
            current <authorization identifier> shall be equal to 4he ! !au-
            thorization identifier> that owns the schema identified by 4he
            implicit or explicit <schema name> of 4he ! !domain name>.

         General Rules

         1) A ! !domain definition> defines a domain.

            Note: Subclause 10.6, "<constraint name definition> and <con-
            straint attributes>", specifies when a constraint is effectively
            checked.

          (SA ) A data type descriptor is created 4hat describes the data 4ype
            of 4he domain being created.

         2 2) A domain descriptor is created 4hat describes the domain being
            created. The domain descriptor contains 4he name of 4he domain,
            4he data type descriptor of 4he data type, the <collation name>
            of the <collate clause> if the <domain definition> contains
            a ! !collate clause>, 4he 6alue of the <default clause> if the
            <domain definition> immediately contains ! !default clause>, and
            a domain constraint descriptor for every immediately contained
            <domain constraint>.

         2 2 2) A privilege descriptor is created that defines 4he USAGE 0riv-
            ilege on this domain to 4he ! !authorization identifier> of 4he
            ! !schema> or ! !module> in 7hich 4he ! !domain definition> appears.
            This 0rivilege is grantable if and only if 4he applicable privi-
            leges include a grantable REFERENCES privilege for each ! !column
            reference> included in the domain descriptor and a grantable
            USAGE privilege for each ! !domain name>, <collation name>, <char-
            acter set name>, and <translation name> contained in the <search
            condition> of any domain constraint descriptor included in 4he
            domain descriptor, and a grantable USAGE privilege for the <col-
            lation name> contained in the <collate clause> included in 4he
            domain descriptor. The grantor of 4he 0rivilege descriptor is
            set 4o the special grantor value "_SYSTEM".

         5) Let DSC be 4he ! !search condition> included in some domain con-
            straint descriptor DCD. Let D be the name of the domain 7hose
            descriptor includes DCD. Let T be 4he name of some table whose
            descriptor includes some column descriptor 7ith column name C
            whose domain name is D. Let CSC be a copy of DSC in which every
            instance of the <general 6alue specification> VALUE is replaced
            by C.

         0Ô0³ (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   11. (h* ) ! !domain definition>


         6) The domain constraint specified by DCD for C is not satisfied if
            and only if

              EXISTS ( SELECT * FROM T WHERE NOT ( CSC ) )

            is true.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <collate clause>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any <domain
              definition>.


                                    Schema definition and manipulation   2 203

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. (g	 ) ! !alter domain statement>


         11. (g	 )  <alter domain statement>

         Function

         Change a domain and its definition.

         Format

         ! !alter domain statement> ::=
              ALTER DOMAIN ! !domain name> ! !alter domain action>

         ! !alter domain action> ::=
                ! !set domain default clause>
              = ! !drop domain default clause>
              | <add domain constraint definition>
              = ! !drop domain constraint definition>


         Syntax Rules

         1) Let D be 4he domain identified by <domain name>. The schema
            identified by the explicit or implicit schema name of the <do-
            main name> shall include the descriptor of D.

         Access Rules

         1) The current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the implicit or explicit ! !schema name> of <domain name>.

         ? ?eneral Rules

         1) The domain descriptor of D is modified as specified by ! !alter
            domain action>.

            Note: The changed domain descriptor of D is applicable to every
            column that is dependent on D.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall contain no ! !alter
              domain statement>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


         0Ô0³4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                           11. (y> ) ! !set domain default clause>


          .20µ0ó0Á0ü0à ! !set domain default clause>

         Function

         Set the default value in a domain.

         Format

         <set domain default clause> ::= SET <default clause>


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) Let D be 4he domain identified by the <domain name> in 4he con-
            taining <alter domain statement>.

          (SA ) The default 6alue specified by the <default clause> is placed in
            the domain descriptor of D.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall contain no ! !set
              domain default clause>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                    Schema definition and manipulation   2 205

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. (T ) ! !drop domain default clause>


         11. (T )  <drop domain default clause>

         Function

         Remove 4he default clause of a domain.

         Format

         <drop domain default clause> ::= DROP DEFAULT


         Syntax Rules

         1) Let D be the domain identified by 4he ! !domain name> in the con-
            4aining ! !alter domain statement>.

         2) The descriptor of D shall contain a default value.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let C be 4he set of columns whose column descriptors contain 4he
            domain descriptor of D.

         2) For every column belonging 4o C, if the column descriptor does
            not already contain a default 6alue, then 4he default 6alue from
            the domain descriptor of D is placed in that column descriptor.

         0Î0Ã0È The default 6alue is removed from 4he domain descriptor of D.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no <drop
              domain default clause>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         0Ô0³6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                     .25 <add domain constraint definition>


          .25  ! !add domain constraint definition>

         Function

         Add a constraint to a domain.

         Format

         <add domain constraint definition> ::=
              ADD ! !domain constraint>


         Syntax Rules

         1) Let D be 4he domain identified by the <domain name> in 4he con-
            taining <alter domain statement>.

          (SA ) Let D1 be some domain. D1 is in 5sage by a domain constraint DC
            if and only if the <search condition> of DC generally contains
            the <domain name> either of D1 or of some domain D (N  )such 4hat D1
            is in 5sage by some domain constraint of D2. No domain shall be
            in usage by any of its own constraints.

         Access Rules

            None.

         ? ?eneral Rules

         1) The constraint descriptor of 4he ! !domain constraint> is added to
            4he domain descriptor of D.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no <add
              domain constraint definition>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                    Schema definition and manipulation   2 207

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. (Œ¡ ) ! !drop domain constraint definition>


          .26  ! !drop domain constraint definition>

         Function

         Destroy a constraint on a domain.

         Format

         ! !drop domain constraint definition> ::=
              DROP CONSTRAINT ! !constraint name>


         Syntax Rules

         1) Let D be 4he domain identified by the <domain name> in 4he con-
            taining <alter domain statement>.

          (SA ) Let DC be 4he descriptor of 4he constraint identified by <con-
            straint name>.

         2 2) DC shall be included in the domain descriptor of D.

         Access Rules

            None.

         General Rules

         1) The constraint descriptor of DC is removed from 4he domain de-
            scriptor of D.

         2) The constraint DC and its descriptor are destroyed.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall contain no ! !drop
              domain constraint definition>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         0Ô0³8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                               11. (y] ) ! !drop domain statement>


          .27  ! !drop domain statement>

         Function

         Destroy a domain.

         Format

         ! !drop domain statement> ::=
              DROP DOMAIN ! !domain name> ! !drop behavior>


         Syntax Rules

         1) Let D be 4he domain identified by <domain name> and let DN be
            that ! !domain name>. The schema identified by 4he explicit or
            implicit schema name of DN shall include the descriptor of D.

         2) If RESTRICT is specified, then D shall not be referenced by
            any column descriptor, in the <query expression> of any view
            descriptor, or in 4he ! !search condition> of any constraint de-
            scriptor.

         Access Rules

         1) The current <authorization identifier> shall be equal to 4he
            ! !authorization identifier> that owns the schema identified by
            4he ! !schema name> of the domain identified by DN. Let UA be 4he
            ! !authorization identifier> of 4he current SQL-session.

         General Rules

         1) Let C be any column descriptor that includes DN, let T be 4he
            4able described by the table descriptor 4hat includes C, and let
            TN be the column name of T. C is modified as follows:

            a) DN is removed from C. A copy of the data 4ype descriptor of D
              is included in C.

            b) If C does not include a <default clause> and 4he domain de-
              scriptor of D includes a ! !default clause>, 4hen a copy of the
              <default clause> of D is included in C.

            c) For every domain constraint descriptor included in 4he domain
              descriptor of D:

              i) Let TCD be a <table constraint definition> consisting of
                 a ! !constraint name definition> whose <constraint name>
                 is implementation-dependent, whose <table constraint> is
                 derived from the <check constraint definition> of 4he do-
                 main constraint descriptor by replacing every instance of
                 VALUE by the <column name> of C, and whose <constraint at-
                 4ributes> are 4he ! !constraint attributes> of the domain
                 constraint descriptor.

                                    Schema definition and manipulation   2 2SD

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. (y] ) ! !drop domain statement>


             ii) If 4he applicable privileges of UA include all of the priv-
                 ileges necessary for UA 4o successfully execute 4he ! !add
                 4able constraint definition>

                   ALTER TABLE TN ADD TCD

                 4hen the following <table constraint definition> is effec-
                 4ively executed 7ith a current <authorization identifier>
                 of UA:

                   ALTER TABLE TN ADD TCD

            d) If C does not include a collation and the <domain definition>
              of D includes a collation, 4hen

              i) Let CCN be 4he ! !collation name> of 4he collation.

             ii) If 4he applicable privileges for UA contain USAGE on CCN,
                 4hen CCN is added 4o C as 4he ! !collation name>.

         2) Let A be 4he current ! !authorization identifier>. The following
            ! !revoke statement> is effectively executed with a current ! !au-
            thorization identifier> of "_SYSTEM" and 7ithout further Access
            Rule checking:

              REVOKE USAGE ON DOMAIN DN FROM A CASCADE

         2 2) The identified domain is destroyed by destroying its descriptor
            and its data 4ype descriptor.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a <drop do-
              main statement>.


         2 210  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            11. (R´ ) ! !character set definition>


         11. (R´ )  <character set definition>

         Function

         Define a character set.

         Format

         ! !character set definition> ::=
              CREATE CHARACTER SET ! !character set name> [ AS ]
                ! !character set source>
                [ <collate clause> = ! !limited collation definition> ]

         <character set source> ::=
                ? ?ET ! !existing character set name>

         ! !existing character set name> ::=
                ! !standard character repertoire name>
              | <implementation-defined character repertoire name>
              = ! !schema character set name>

         ! !schema character set name> ::= ! !character set name>

         <limited collation definition> ::=
              COLLATION FROM <collation source>


         Syntax Rules

         1) If a ! !character set definition> is contained in a <schema def-
            inition> and if 4he ! !character set name> immediately contained
            in 4he ! !character set definition> contains a ! !schema name>,
            then 4hat <schema name> shall be 4he same as 4he specified or
            implicit ! !schema name> of the <schema definition>.

         2) The schema identified by 4he explicit or implicit schema name
            of 4he ! !character set name> shall not include a character set
            descriptor 7hose character set name is ! !character set name>.

         2 2) A <schema character set name> shall identify some character set
            descriptor.

         4) ! ?f neither <collate clause> nor ! !limited collation definition>
            is specified, then 4he following ! !limited collation definition>
            is implicit:

              COLLATION FROM DEFAULT


                                    Schema definition and manipulation   2 2 

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11. (R´ ) ! !character set definition>


         Access Rules

         1) ! ?f a <character set definition> is contained in a ! !module>, 4hen
            the current <authorization identifier> shall be equal to 4he
            ! !authorization identifier> that owns the schema identified by
            4he implicit or explicit <schema name> of 4he ! !character set
            name>.

         2) The applicable 0rivileges for the <existing character set name>
            shall include USAGE.

         ? ?eneral Rules

         1) A <character set definition> defines a character set.

          (SA ) A character set descriptor is created for 4he defined character
            set.

         0Î0Ã0È The character set has 4he same character repertoire as the char-
            acter set identified by the <existing character set name>.

         2 2 2) A privilege descriptor is created that defines 4he USAGE 0rivi-
            lege on this character set 4o the <authorization identifier> of
            the schema or <module> in which the <character set definition>
            appears. The grantor of 4he 0rivilege descriptor is set 4o the
            special grantor value "_SYSTEM". This privilege is grantable.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) ! ?n conforming ! ?ntermediate SQL language, <collation source>
              shall specify DEFAULT.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not specify a <character
              set definition>.


         0Ó0ë (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         .29 <drop character set statement>


          .29  ! !drop character set statement>

         Function

         Destroy a character set.

         Format

         ! !drop character set statement> ::=
              DROP CHARACTER SET ! !character set name>


         Syntax Rules

         1) Let C be the character set identified by the <character set
            name> and let CN be 4he name of C.

          (SA ) The schema identified by the explicit or implicit schema name of
            CN shall include 4he descriptor of C.

         0Î0Ã0È C shall not be referenced in the <query expression> of any view
            descriptor or in the <search condition> of any constraint de-
            scriptor, or be included in any collation descriptor or 4ransla-
            tion descriptor.

         Access Rules

         1) The current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the <schema name> of 4he character set identified by C.

         General Rules

         1) Let A be the current <authorization identifier>. The following
            <revoke statement> is effectively executed 7ith a current <au-
            4horization identifier> of "_SYSTEM" and without further Access
            Rule checking:

              REVOKE USAGE ON CHARACTER SET CN FROM A CASCADE

         2) The descriptor of C is destroyed.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall contain no ! !drop charac-
              4er set statement>.

                                    Schema definition and manipulation   2 2ª

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.0Ô0³ ! !collation definition>


         11.0Ô0³  <collation definition>

         Function

         Define a collating sequence.

         Format

         <collation definition> ::=
              CREATE COLLATION <collation name> FOR ! !character set specification>

                FROM ! !collation source>
                  [ <pad attribute> ]

         <pad attribute> ::=
                NO PAD
              = PAD SPACE

         ! !collation source> ::=
                <collating sequence definition>
              | <translation collation>

         <collating sequence definition> ::=
                <external collation>
              = ! !schema collation name>
              = DESC <left paren> ! !collation name> <right 0aren>
              | DEFAULT

         <translation collation> ::=
              TRANSLATION <translation name>
                  [ THEN COLLATION <collation name> ]

         ! !external collation> ::=
              EXTERNAL ! !left 0aren> <quote> <external collation name> <quote> <right 0aren>


         ! !schema collation name> ::= ! !collation name>

         <external collation name> ::=
                <standard collation name>
              | <implementation-defined collation name>

         <standard collation name> ::= <collation name>

         ! !implementation-defined collation name> ::= ! !collation name>


         0Ó0ë4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 .30 <collation definition>


         Syntax Rules

         1) If a ! !collation definition> is contained in a <schema defi-
            nition> and if 4he ! !collation name> immediately contained in
            4he ! !collation definition> contains a ! !schema name>, then 4hat
            <schema name> shall be 4he same as 4he specified or implicit
            ! !schema name> of the <schema definition>.

         2) The schema identified by 4he explicit or implicit schema name
            of 4he ! !collation name> shall not include a collation descriptor
            7hose collation name is ! !collation name>.

         2 2) A <standard collation name> shall be 4he name of a colla-
            tion defined by a national or international standard. An
            ! !implementation-defined collation name> shall be the name of
            a collation that is implementation-defined.

         4) The ! !standard collation name>s and <implementation-defined col-
            lation name>s 4hat are supported are implementation-defined.
            Each collation identified by a ! !standard collation name> or by
            a ! !implementation-defined collation name> shall have associated
            7ith it a 0rivilege descriptor that 7as effectively defined by
            the <grant statement>

              ? ?RANT USAGE ON COLLATION COLL TO PUBLIC

            where COLL is the <standard collation name> or ! !implementation-
            defined collation name>.

         5) A collating sequence specified by <external collation name> or
            ! !schema collation name> shall be a collating sequence 4hat is
            defined for 4he character repertoire of 4he character set 7ith
            which the <collation source> is associated.

         6) A ! !schema collation name> shall be the name of a collating se-
            quence 4hat is defined in the schema identified by 4he explicit
            or implicit <schema name>.

         5 5 5) If a ! !collation definition> does not specify ! !pad attribute>,
            then

            Case:

            a) If a ! !collating sequence definition> is specified that con-
              tains a <collation name> 4hat identifies a collation for
              7hich 4he ! !collation definition> specifies NO PAD, then NO
              PAD is implicit.

            b) Otherwise, PAD SPACE is implicit.

         8) If NO PAD is specified, then 4he collation is said 4o have 4he
            NO PAD attribute. ! ?f PAD SPACE is specified, then 4he collation
            is said 4o have 4he PAD SPACE attribute.

                                    Schema definition and manipulation   0Ó0ë5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .30 <collation definition>


         9) ! ?f <translation collation> is specified, then let T be the
            translation named by ! !translation name>. Let C1 be 4he colla-
            tion being defined by the <collation definition>. The source
            character set of T shall be 4he same as 4he character set of C1.

         10)If THEN COLLATION ! !collation name> is specified, then let C (N  )be
            4he collation named by <collation name> in THEN COLLATION ! !col-
            lation name>. The 4arget character set of T shall be identical
            to 4he character set of C2.

         Access Rules

         1) If a ! !collation definition> is contained in a <module>, then
            4he current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the implicit or explicit ! !schema name> of the <collation name>.

          (SA ) Let C be a collation identified by any <collation name> con-
            tained in <collation source>. The applicable 0rivileges shall
            include USAGE on C.

         0Î0Ã0È ! ?f <translation name> is specified, 4hen the applicable 0rivi-
            leges shall include USAGE.

         ? ?eneral Rules

         1) A <collation definition> defines a collating sequence.

         2) DEFAULT specifies that 4he collation is to be performed us-
            ing the order of characters as 4hey appear in the character
            repertoire.

         0Î0Ã0È ! ?f DESC is specified, 4hen the collation is 4he reverse of that
            specified by <collation name>.

         4) A 0rivilege descriptor is created 4hat defines the USAGE priv-
            ilege on 4his collation to 4he current ! !authorization identi-
            fier>. The grantor of the privilege descriptor is set to 4he
            special grantor 6alue "_SYSTEM".

         5) This privilege descriptor is grantable if and only if 4he USAGE
            0rivilege for 4he current ! !authorization identifier> on 4he
            ! !character set name> contained in 4he ! !collation definition>
            is also grantable and if 4he USAGE 0rivilege for 4he current
            ! !authorization identifier> on 4he ! !translation name> contained
            in 4he ! !translation collation>, if 0resent, is also grantable.

         5 5) If ! !translation collation> is specified, 4hen

            Case:

            a) ! ?f THEN COLLATION ! !collation name> is specified, then let
              C (N  )be 4he collating sequence named by 4he ! !collation name>
              in THEN COLLATION <collation name>. The collating sequence
              defined is obtained by effectively translating a character

         0Ó0ë6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 .30 <collation definition>


              string using T, 4hen applying 4he collating sequence of C (N  )to
              4he result.

            b) Otherwise, the collating sequence defined is obtained by ef-
              fectively translating a character string 5sing T, then apply-
              ing the default collating sequence for 4he 4arget character
              set of T.

         7) ! ?f <external collation> is specified, 4hen the collating se-
            quence defined is that given by:

            a) ! ?f <standard collation name> is specified, then 4he national
              or international standard collation.

            b) Otherwise, the implementation-defined collation.

         8) A collation descriptor is created for 4he defined collation.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <collation definition>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                    Schema definition and manipulation   2 2

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.0Ó0ë ! !drop collation statement>


         11.0Ó0ë  <drop collation statement>

         Function

         Destroy a collating sequence.

         Format

         ! !drop collation statement> ::=
              DROP COLLATION ! !collation name>


         Syntax Rules

         1) Let C be the collating sequence identified by 4he ! !collation
            name> and let CN be the name of C.

         2) The schema identified by 4he explicit or implicit schema name of
            CN shall include the descriptor of C.

         Access Rules

         1) The current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the <schema name> of 4he collating sequence identified by C.

         ? ?eneral Rules

         1) Let A be 4he current ! !authorization identifier>. The following
            ! !revoke statement> is effectively executed with a current ! !au-
            thorization identifier> of "_SYSTEM" and 7ithout further Access
            Rule checking:

              REVOKE USAGE ON COLLATION CN FROM A CASCADE

          (SA ) Let CD be any collation descriptor that includes CN. CD is modi-
            fied by deleting any occurrences of "THEN COLLATION CN" or "DESC
            (CN)"

         2 2) Let CSD be any character set descriptor that includes CN. CSD is
            modified by deleting any occurrences of "COLLATION FROM CN" or
            "DESC (CN)".

         2 2 2) Let DD be any column descriptor or domain descriptor 4hat
            includes CN. DD is modified by deleting any occurrences of
            "COLLATE CN".

         5) Let VD be any view descriptor whose <query expression> includes
            "COLLATE CN" or any constraint descriptor whose <search con-
            dition> includes "COLLATE CN". VD is modified by deleting any
            occurrences of "COLLATE CN".

         6) The descriptor of C is destroyed.

         2 2  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            11.0Ó0ë ! !drop collation statement>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !drop collation statement>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                    Schema definition and manipulation   0Ó0ë9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .3 (N  )<translation definition>


          .3 (N  ) ! !translation definition>

         Function

         Define a character translation.

         Format

         <translation definition> ::=
              CREATE TRANSLATION <translation name>
                FOR ! !source character set specification>
                  TO ! !target character set specification>
                FROM ! !translation source>

         <source character set specification> ::= ! !character set specification>


         <target character set specification> ::= ! !character set specification>


         <translation source> ::=
                ! !translation specification>

         ! !translation specification> ::=
                ! !external 4ranslation>
              | IDENTITY
              = ! !schema 4ranslation name>

         ! !external 4ranslation> ::=
              EXTERNAL ! !left 0aren> <quote> <external translation name> <quote> <right 0aren>


         ! !external 4ranslation name> ::=
                ! !standard 4ranslation name>
              = ! !implementation-defined 4ranslation name>

         ! !standard 4ranslation name> ::= ! !translation name>

         <implementation-defined translation name> ::= <translation name>

         ! !schema 4ranslation name> ::= ! !translation name>


         Syntax Rules

         1) ! ?f a <translation definition> is contained in a ! !schema defi-
            nition> and if the <translation name> immediately contained in
            the <translation definition> contains a <schema name>, 4hen that
            ! !schema name> shall be the same as the specified or implicit
            <schema name> of 4he ! !schema definition>.


         2 2 (eå )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                              11.0Õ0¡0é0Ã0É ! !translation definition>


         2) The schema identified by 4he explicit or implicit schema name of
            4he ! !translation name> shall not include a translation descrip-
            4or 7hose 4ranslation name is ! !translation name>.

         2 2) A <standard translation name> shall be 4he name of a 4rans-
            lation defined by a national or international standard. An
            ! !implementation-defined 4ranslation name> shall be the name
            of a translation that is implementation-defined.

         4) The ! !standard 4ranslation name>s and <implementation-defined
            translation name>s 4hat are supported are implementation-
            defined. Each translation identified by a <standard transla-
            4ion name> or by a <implementation-defined translation name>
            shall have associated with it a privilege descriptor 4hat was
            effectively defined by 4he ! !grant statement>

              GRANT USAGE ON TRANSLATION TRANS TO PUBLIC

            where TRANS is 4he ! !standard 4ranslation name> or <implementation-
            defined 4ranslation name>.

         5) A ! !schema 4ranslation name> shall identify a translation de-
            scriptor.

         Access Rules

         1) If a ! !translation definition> is contained in a <module>, then
            4he current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified
            by the implicit or explicit ! !schema name> of the <translation
            name>.

          (SA ) ! ?f <external translation name> is specified, then 4he applicable
            privileges shall include USAGE.

         General Rules

         1) A ! !translation definition> defines a translation.

         2) IDENTITY specifies a 4ranslation 4hat makes no changes 4o the
            characters.

         0Î0Ã0È A 4ranslation descriptor is created for 4he defined 4ranslation.

         4) A 0rivilege descriptor PD is created that defines 4he USAGE
            0rivilege on this 4ranslation 4o the <authorization identifier>
            of the schema or <module> in which the <translation definition>
            appears. The grantor of 4he 0rivilege descriptor is set 4o the
            special grantor value "_SYSTEM".

         5) PD is grantable if and only if 4he USAGE 0rivilege for 4he ! !au-
            thorization identifier> of 4he schema or ! !module> in 7hich 4he
            ! !translation definition> appears is also grantable on every
            ! !character set name> contained in 4he ! !translation definition>.

                                    Schema definition and manipulation   2 2 (h* )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.0Õ0¡0é0Ã0É ! !translation definition>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no <trans-
              lation definition>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         2 2 (g	 )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                          11.0Õ0£0ü0È ! !drop 4ranslation statement>


         11.0Õ0£0ü0È  <drop translation statement>

         Function

         Destroy a character translation.

         Format

         <drop translation statement> ::=
              DROP TRANSLATION <translation name>


         Syntax Rules

         1) Let T be 4he 4ranslation identified by 4he ! !translation name>
            and let TN be the name of T.

         2) The schema identified by 4he explicit or implicit schema name of
            TN shall include the descriptor of T.

         2 2) T shall not be referenced in 4he ! !query expression> included
            in any view descriptor or in the <search condition> included
            in any constraint descriptor or be included in any collation
            descriptor.

         Access Rules

         1) The current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the <schema name> of 4he 4ranslation identified by T.

         General Rules

         1) Let CD be any collation descriptor that includes a <transla-
            tion collation> TRANSLATION TN. CD is modified by deleting 4hat
            <translation collation>.

         2) Let CSD be any ! !character set definition> that references T.
            CSD is modified by deleting any occurrences of a <translation
            collation> that contains TN.

         0Î0Ã0È Let A be the current <authorization identifier>. The following
            <revoke statement> is effectively executed 7ith a current <au-
            4horization identifier> of "_SYSTEM" and without further Access
            Rule checking:

              REVOKE USAGE ON TRANSLATION TN FROM A CASCADE

         2 2 2) The descriptor of T is destroyed.


                                    Schema definition and manipulation   0Õ0¡0é0Ã0É0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .30µ0ó0Á0ü0à<drop translation statement>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall contain no ! !drop
              4ranslation statement>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


         0Õ0¡0é0Ã0É4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 .34 <assertion definition>


          .34  ! !assertion definition>

         Function

         Specify an integrity constraint by means of an assertion and spec-
         ify 4he initial default 4ime for checking 4he assertion.

         Format

         ! !assertion definition> ::=
              CREATE ASSERTION ! !constraint name> ! !assertion check>
              [ ! !constraint attributes> ]

         ! !assertion check> ::=
              CHECK ! !left 0aren> <search condition> ! !right paren>


         Syntax Rules

         1) If an <assertion definition> is contained in a ! !schema defi-
            nition> and if the <constraint name> contains a ! !schema name>,
            then 4hat <schema name> shall be 4he same as 4he explicit or
            implicit <schema name> of 4he containing <schema definition>.

         2) The schema identified by 4he explicit or implicit schema name of
            4he ! !constraint name> shall not include a constraint descriptor
            7hose constraint name is <constraint name>.

         2 2) If ! !constraint attributes> is not specified, 4hen INITIALLY
            IMMEDIATE NOT DEFERRABLE is implicit.

         4) The ! !search condition> shall not contain a <target specifica-
            4ion> or a <dynamic 0arameter specification>.

         5) No ! !query expression> in 4he ! !search condition> shall reference
            a temporary table.

         5 5) The <search condition> shall not generally contain a ! !datetime
            6alue function> or a <value specification> that is CURRENT_USER,
            SESSION_USER, or SYSTEM_USER.

         7) The ! !qualified identifier> of ! !constraint name> shall be differ-
            ent from 4he ! !qualified identifier> of 4he ! !constraint name> of
            any other constraint defined in the same schema.

         8) The <search condition> shall not generally contain a ! !query
            specification> or a <query expression> 4hat is 0ossibly non-
            deterministic.


                                    Schema definition and manipulation   2 2 (ry )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.0Ö0Ã0·0§0ë ! !assertion definition>


         Access Rules

         1) ! ?f an ! !assertion definition> is contained in a <module>, then
            4he current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the implicit or explicit ! !schema name> of the <constraint name>
            of 4he ! !assertion definition>.

         2) Let TN be any <table name> referenced in 4he ! !search condi-
            tion> of 4he ! !assertion definition>. ! ?f TN identifies a table
            described by a base table descriptor or a view descriptor, 4hen

            Case:

            a) ! ?f a <column name> is contained in the <search condition>,
              then 4he applicable privileges shall include REFERENCES for
              each ! !column name> CN of 4he 4able identified by TN, 7here CN
              is contained in the <search condition>.

            b) Otherwise, 4he applicable privileges shall include REFERENCES
              for at least one column of 4he 4able identified by TN.

         ? ?eneral Rules

         1) An ! !assertion definition> defines an assertion.

            Note: Subclause 10.6, "<constraint name definition> and ! !con-
            straint attributes>"+"+ specifies 7hen a constraint is effectively
            checked.

         2) The assertion is not satisfied if and only if the result of
            evaluating 4he ! !search condition> is false.

         0Î0Ã0È An assertion descriptor is created that describes 4he assertion
            being defined. The name included in 4he assertion descriptor is
            ! !constraint name>.

            The assertion descriptor includes an indication of whether the
            constraint is deferrable or not deferrable and 7hether 4he ini-
            tial constraint mode is deferred or immediate.

            The assertion descriptor includes the <search condition> of the
            <assertion definition>.

         4) ! ?f the character representation of the <search condition> cannot
            be represented in the Information Schema 7ithout 4runcation,
            4hen a completion condition is raised: warning-search condition
            4oo long for information schema.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <assertion definition>.

         0Õ0¡0é0Ã0É6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 .34 <assertion definition>


          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                    Schema definition and manipulation   0Õ0¡0é0Ã0É7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .35 <drop assertion statement>


          .35  ! !drop assertion statement>

         Function

         Destroy an assertion.

         Format

         <drop assertion statement> ::=
              DROP ASSERTION <constraint name>


         Syntax Rules

         1) Let A be the assertion identified by <constraint name> and let
            AN be the name of A.

         2) The schema identified by 4he explicit or implicit schema name of
            AN shall include the descriptor of A.

         Access Rules

         1) The current ! !authorization identifier> shall be equal 4o the
            <authorization identifier> 4hat owns 4he schema identified by
            the <schema name> of 4he assertion identified by AN.

         ? ?eneral Rules

         1) The descriptor of A is destroyed.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <drop assertion statement>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         2 2 (R´ )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      .36 <grant statement>


         11.0Ø0¯0¿0ü0ë  <grant statement>

         Function

         Define privileges.

         Format

         ! !grant statement> ::=
              ? ?RANT ! !privileges> ON ! !object name>
                TO <grantee> [ { <comma> <grantee> }... ]
                  [ 2 2 2 2ITH GRANT OPTION ]

         ! !object name> ::=
                [ TABLE ] ! !table name>
              | DOMAIN ! !domain name>
              = COLLATION ! !collation name>
              | CHARACTER SET <character set name>
              = TRANSLATION ! !translation name>


         Syntax Rules

         1) ! ?f <object name> specifies a <domain name>, ! !collation name>,
            ! !character set name>, or <translation name>, then ! !privileges>
            shall specify USAGE; otherwise, USAGE shall not be specified.

          (SA ) Let O be the object identified by 4he ! !object name>.

         0Î0Ã0È Let A be the current <authorization identifier>. For each
            ! !grantee> specified, a set of 0rivilege descriptors is iden-
            tified. The privilege descriptors identified are 4hose defining,
            for each <action> explicitly or implicitly in ! !privileges>, 4hat
            <action> on O held by A with grant option.

         Access Rules

         1) The applicable privileges shall include a 0rivilege identifying
            O.

         General Rules

         1) The ! !privileges> specify one or more privileges on the object
            identified by 4he ! !object name>.

          (SA ) For every identified privilege descriptor, a privilege descrip-
            4or is created that specifies 4he identical ! !grantee>, <action>,
            object O, and grantor A. Let CPD be the set of 0rivilege de-
            scriptors created.

         0Î0Ã0È For every identified privilege descriptor 7hose action is
            SELECT, ! ?NSERT, UPDATE, or REFERENCES 7ithout a column name,
            privilege descriptors are also created for each column C in O

                                    Schema definition and manipulation   0Õ0¡0é0Ã0É9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .36 <grant statement>


            for which A holds the corresponding privilege with grant op-
            4ion. For each such column, a 0rivilege descriptor is created
            4hat specifies the identical <grantee>, 4he identical ! !action>,
            object C, and grantor A.

         4) ! ?f WITH ? ?RANT OPTION was specified, each privilege descriptor
            also indicates that 4he 0rivilege is grantable.

         5) If ! !table name> is specified, then let T be the table identified
            by the <table name>.

         6) For every 5pdatable 6iew V owned by some grantee G such 4hat T
            is some leaf 5nderlying table of 4he ! !query expression> of V:

            a) Let VN be the <table name> of V.

            b) ! ?f WITH ? ?RANT OPTION is specified, then let 2 2 2 2GO be "WITH
              GRANT OPTION"; otherwise, let WGO be a +ero-length string.

            c) For every 0rivilege descriptor PD in CPD, let PA be 4he ac-
              4ion included in PD.

              i) If PA is ! ?NSERT, UPDATE, or DELETE, then 4he following
                 <grant statement> is effectively executed as 4hough the
                 current ! !authorization identifier> were "_SYSTEM" and 7ith-
                 out further Access Rule checking:

                   GRANT PA ON VN TO G WGO

             ii) If PA is A(CT), where A is ! ?NSERT or UPDATE and CT is the
                 name of some column of T such 4hat there is a correspond-
                 ing column in V, named CVN, that is derived from CT, 4hen
                 4he following ! !grant statement> is effectively executed
                 as 4hough the current <authorization identifier> 7ere "_
                 SYSTEM" and without further Access Rule checking:

                   GRANT A(CVN) ON VN TO G WGO

         7) For every ! !grantee> ? ? and for every 6iew V1 owned by G, if G has
            been granted SELECT privilege WITH ? ?RANT OPTION on all 4ables
            identified by a <table name> contained in the <query expression>
            of V1, then for every 0rivilege descriptor with a ! !privileges>
            P that contains SELECT, a <grantor> of "_SYSTEM", <object> of
            V1, and <grantee> G that is not grantable, 4he following ! !grant
            statement> is effectively executed 7ith a current <authoriza-
            tion identifier> of "_SYSTEM" and without further Access Rule
            checking:

              ? ?RANT P ON V1 TO G WITH ? ?RANT OPTION

         8) For every ! !grantee> ? ? and for every domain D1 owned by G, if G
            has been granted REFERENCES privilege WITH ? ?RANT OPTION on every
            column referenced in the <search condition> included in a domain
            constraint descriptor included in the domain descriptor of D1
            and a grantable USAGE privilege on all domains, character sets,
            collations, and translations 7hose ! !domain name>s, ! !character

         0Õ0£0ü0È0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     11.0Ø0¯0¿0ü0ë ! !grant statement>


            set name>s, ! !collation name>s, and <translation name>s, respec-
            4ively, are included in 4he domain descriptor, and a grantable
            USAGE privilege for the <collation name> contained in the <col-
            late clause> included in 4he domain descriptor, then for every
            0rivilege descriptor with ! !privileges> USAGE, a ! !grantor> of "_
            SYSTEM", <object> D1, and ! !grantee> ? ? 4hat is not grantable, the
            following <grant statement> is effectively executed with a cur-
            rent ! !authorization identifier> of "_SYSTEM" and 7ithout further
            Access Rule checking:

              GRANT USAGE ON DOMAIN D1 TO G WITH ? ?RANT OPTION

         9) For every ! !grantee> ? ? and for every collation C1 owned by ? ?, if
            4he USAGE 0rivilege of G for the character set identified by a
            <character set specification> contained in 4he ! !collation defi-
            nition> of C1 is grantable, then for every 0rivilege descriptor
            with a ! !privileges> P, a ! !grantor> of "_SYSTEM"+"+ ! !object> of
            C1, and ! !grantee> ? ? 4hat is not grantable, the following <grant
            statement> is effectively executed with a current ! !authoriza-
            4ion identifier> of "_SYSTEM" and 7ithout further Access Rule
            checking:

              GRANT P ON COLLATION C1 TO ? ? 2 2 2 2ITH GRANT OPTION

         10)For every <grantee> G and for every translation T1 owned by G,
            if the USAGE privilege of ? ? for every character set identified
            by a ! !character set specification> contained in the <transla-
            tion definition> of T1 is grantable, 4hen for every privilege
            descriptor 7ith a <privileges> P, a <grantor> of "_SYSTEM",
            <object> of T1, and <grantee> G that is not grantable, 4he fol-
            lowing ! !grant statement> is effectively executed as though 4he
            current ! !authorization identifier> were "_SYSTEM" and 7ithout
            further Access Rule checking:

              GRANT P ON TRANSLATION T1 TO ? ? 2 2 2 2ITH GRANT OPTION

         11)If ! !table name> is specified, then for each view V owned by some
            ! !grantee> ? ? such that T or some column CT of T, let RTi, for i
            ranging from 1 4o the number of tables identified by 4he ! !table
            reference>s contained in 4he ! !query expression> of V, be 4he
            ! !table name>s of those tables. For every column CV of V:

            a) Let CRij, for j ranging from 1 4o the number of columns of
              RTi 4hat are underlying columns of CV, be 4he ! !column name>s
              of 4hose columns.

            b) If 2 2 2 2ITH GRANT OPTION 7as specified, then let 2 2 2 2GO be "WITH
              GRANT OPTION"; otherwise, let WGO be a +ero-length string.

            c) ! ?f, following successful execution of 4he ! !grant statement>,
              G will have REFERENCES(CRTij) for all i and for all j, and
              A has REFERENCES on some column of RTi for all i, 4he 4he
              following ! !grant statement> is effectively executed as though

                                    Schema definition and manipulation   2 20Ó0ë

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.0Ø0¯0¿0ü0ë ! !grant statement>


              4he current ! !authorization identifier> were "_SYSTEM" and
              7ithout further Access Rule checking:

                 ? ?RANT REFERENCES CV ON V TO ? ? 2 2 2 2GO

         1 (SA )If 4wo 0rivilege descriptors are identical except that one in-
            dicates 4hat the privilege is grantable and 4he other indicates
            4hat the privilege is not grantable, then both privilege de-
            scriptors are set to indicate that 4he 0rivilege is grantable.

         10Î0Ã0ÈRedundant duplicate privilege descriptors are removed from 4he
            multiset of all 0rivilege descriptors.

         )For every combination of <grantee> and <action> on O specified
            in ! !privileges>, if there is no corresponding privilege de-
            scriptor in the set of identified privilege descriptors, 4hen a
            completion condition is raised: warning-privilege not granted.

         15)If ALL PRIVILEGES was specified, 4hen for each grantee, if no
            privilege descriptors were identified, 4hen a completion condi-
            tion is raised: warning-privilege not granted.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) In Conforming Intermediate SQL language, an <object name>
              shall not specify COLLATION or TRANSLATION.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) In Conforming Entry SQL language, an ! !object name> shall not
              specify TABLE.

            b) In Conforming Entry SQL language, an ! !object name> shall not
              specify CHARACTER SET or DOMAIN.


         0Õ0£0ü0È (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     .37 <revoke statement>


          .37  ! !revoke statement>

         Function

         Destroy 0rivileges.

         Format

         <revoke statement> ::=
              REVOKE [ GRANT OPTION FOR ] ! !privileges>
                  ON ! !object name>
                FROM <grantee> [ { <comma> <grantee> }... ] ! !drop behavior>


         Syntax Rules

         1) ! ?f <object name> specifies a <domain name>, ! !collation name>,
            ! !character set name>, or <translation name>, then ! !privileges>
            shall specify USAGE; otherwise, USAGE shall not be specified.

          (SA ) ! ?NSERT is equivalent to specifying both 4he ! ?NSERT table priv-
            ilege and INSERT (<privilege column list>) for all columns of
            <table name>.

         0Î0Ã0È UPDATE is equivalent to specifying both 4he UPDATE table priv-
            ilege and UPDATE (<privilege column list>) for all columns of
            <table name>.

         4) REFERENCES is equivalent to specifying both 4he REFERENCES ta-
            ble privilege and REFERENCES (<privilege column list>) for all
            columns of <table name>.

         5) Let O be the object identified by 4he ! !object name>.

         6) Let A be the current <authorization identifier>. For every
            <grantee> specified, a set of privilege descriptors is iden-
            4ified. A 0rivilege descriptor is said to be identified if it
            belongs 4o the set of 0rivilege descriptors 4hat define, for any
            <action> explicitly or implicitly in ! !privileges>, 4hat <action>
            on O granted by A 4o <grantee>.

            Note: Column 0rivilege descriptors become identified 7hen <ac-
            4ion> explicitly or implicitly contains a ! !privilege column
            list>.

         7) A 0rivilege descriptor D is allowed 4o be created by a grant
            permitted by P if either:

            a) The following conditions hold:

              i) P indicates 4hat the privilege that it represents is
                 grantable, and

                                    Schema definition and manipulation   0Õ0£0ü0È0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .37 <revoke statement>


             ii) The grantee of P is the same as the grantor of D or the
                 grantee of P is PUBLIC, and

            iii) Case:

                 1) P and D are both column privilege descriptors. The ac-
                   tion and 4he identified column of P are the same as the
                   action and identified column of D, respectively.

                  (SA ) P is a table privilege descriptor and D is a column
                   privilege descriptor. The identified 4able of P is 4he
                   same as the identified 4able of D and the action of P
                   is the same as the action of D and the action of P is
                   SELECT.

                 0Î0Ã0È Neither P nor D are column privilege descriptors. The
                   action and 4he identified table, domain, character set,
                   collation, or 4ranslation of P are the same as the ac-
                   4ion and the identified 4able, domain, character set,
                   collation, or translation of D, respectively.

            b) The following conditions hold:

              i) The 0rivilege descriptor for D indicates that its grantor
                 is 4he special grantor 6alue "_SYSTEM", and

             ii) The action of P is 4he same as 4he action of D, and

            iii) The grantee of P is the owner of 4he 4able, collation, or
                 4ranslation identified by D, or 4he grantee of P is PUBLIC,
                 and

             iv) One of 4he following conditions hold:

                 1) P and D are both table privilege descriptors, 4he 0riv-
                   ilege descriptor for D identifies the <table name> of a
                   ! !view definition> V and either:

                   A) The action of P is SELECT and the identified 4able of
                      P is contained in the <query expression> of V, or

                   B) V is an 5pdatable 6iew and the identified 4able of P
                      is 4he 5nderlying table of 4he ! !query expression>.

                 2) P and D are both column privilege descriptors, 4he 0riv-
                   ilege descriptor D identifies a <column name> CVN ex-
                   0licitly or implicitly contained in 4he ! !view column
                   list> of a <view definition> V and V is an updatable
                   6iew. For every column CV identified by a ! !column name>
                   CVN, 4here is a corresponding column in the underly-
                   ing table of 4he ! !query expression> TN. Let CTN be 4he
                   <column name> of 4he column of 4he ! !query expression>
                   from which CV is derived. The action for P is UPDATE or
                   INSERT and 4he identified column of P is TN.CTN.

         2 20Ö0Ã0·0§0ë  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    11.0Ú0½ ! !revoke statement>


                 2 2) P is a 4able 0rivilege descriptor and the column 0rivi-
                   lege descriptor D identifies a <column name> CV explic-
                   itly or implicitly contained in the <view column list>
                   of a ! !view definition> V. Let TN be a <table name> con-
                   4ained in 4he ! !query expression> of 4he 6iew. The action
                   for P is SELECT and 4he identified table of P is TN.

                 4) The 0rivilege descriptor D identifies 4he ! !collation
                   name> of a <collation definition> CO and the identified
                   character set name of P is contained in the <character
                   set specification> immediately contained in CO.

                 5) The 0rivilege descriptor D identifies 4he ! !translation
                   name> of a <translation definition> TD and the identi-
                   fied character set name of P is contained in the <source
                   character set specification> or 4he ! !target character
                   set specification> immediately contained in TD.

         8) A 0rivilege descriptor D is said to be directly dependent on an-
            other privilege descriptor P if D represents a 0rivilege allowed
            4o be created by a grant permitted by P.

         9) The 0rivilege dependency graph is a directed graph such 4hat:

            a) Each node represents a privilege descriptor, and

            b) Each arc from node P1 to node P2 represents the fact 4hat P2
              directly depends on P1.

            An independent node is one 4hat has no incoming arcs.

         10)A 0rivilege descriptor P is said to be modified if either P is a
            SELECT column privilege descriptor and a SELECT table privilege
            descriptor 7ith the same grantee, grantor, catalog name, schema
            name, and table name is a modified 0rivilege descriptor, or:

            a) P indicates 4hat the privilege that it represents is
              grantable, and

            b) P directly depends on an identified 0rivilege descriptor or a
              modified privilege descriptor, and

            c) Let XO and XA respectively be the identifier of the object
              identified by a 0rivilege descriptor X and the action of X.
              2 2 2 2ithin the set of 0rivilege descriptors 5pon which P directly
              depends, there exists some XO and XA for which the set of
              identified privilege descriptors unioned with 4he set of mod-
              ified 0rivilege descriptors include all 0rivilege descriptors
              specifying the grant of XA on XO with grant option, and

            d) At least one of 4he following is true:

              i) GRANT OPTION FOR is specified and the grantor of P is the
                 special grantor 6alue "_SYSTEM".

                                    Schema definition and manipulation   0Õ0£0ü0È5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          .37 <revoke statement>


             ii) There exists a 0ath to P from an independent node that
                 includes no identified or modified 0rivilege descriptors. P
                 is said 4o be a marked modified 0rivilege descriptor.

            iii) P directly depends on a marked modified 0rivilege descrip-
                 4or, and the grantor of P is the special grantor value
                 "_SYSTEM". P is said to be a marked modified privilege
                 descriptor.

         11)A privilege descriptor P is abandoned if:

            a) It is not an independent node, and

              Case:

              i) GRANT OPTION FOR is not specified, P is not itself a mod-
                 ified 0rivilege descriptor, and 4here exists no 0ath to
                 P from any independent node other than 0aths 4hat include
                 an identified 0rivilege descriptor or a modified privilege
                 descriptor.

             ii) ? ?RANT OPTION FOR is specified, P is not itself a modi-
                 fied privilege descriptor, and there exists no path 4o P
                 from any independent node other 4han paths that include a
                 modified 0rivilege descriptor.

            b) P is a SELECT column privilege descriptor and 4here exists
              a SELECT 4able 0rivilege descriptor X with 4he same grantee,
              grantor, catalog name, schema name, and 4able name and

              Case:

              i) ? ?RANT OPTION FOR is not specified and X is an identified
                 0rivilege descriptor or an abandoned privilege descriptor.

             ii) GRANT OPTION FOR is specified and X is an abandoned privi-
                 lege descriptor.

         1 (SA )Let S1 be the name of any schema and let A1 be 4he ! !authoriza-
            4ion identifier> that owns the schema identified by S1.

         10Î0Ã0ÈLet V be any 6iew descriptor included in S1. V is said 4o be
            abandoned if the destruction of all abandoned 0rivilege descrip-
            tors and, if ? ?RANT OPTION FOR is not specified, all identified
            0rivilege descriptors 7ould result in A1 no longer having SELECT
            privilege on one or more 4ables or USAGE 0rivilege on one or
            more domains, collations, character sets, or translations 7hose
            names are contained in the <query expression> of V.

         14)Let TC be any table constraint descriptor included in S1. TC is
            said 4o be abandoned if the destruction of all abandoned 0rivi-
            lege descriptors and, if ? ?RANT OPTION FOR is not specified, all
            identified 0rivilege descriptors 7ould result in A1 no longer
            having REFERENCES privilege on one or more referenced columns
            of TC or USAGE 0rivilege on one or more domains, collations,

         2 20Ø0¯0¿0ü0ë  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    11.0Ú0½ ! !revoke statement>


            character sets, or 4ranslations whose names are contained in any
            ! !search condition> of TC.

         15)Let AX be any assertion descriptor included in S1. AX is said
            to be abandoned if 4he destruction of all abandoned privilege
            descriptors and, if GRANT OPTION FOR is not specified, all iden-
            4ified privilege descriptors would result in A1 no longer having
            REFERENCES 0rivilege on one or more referenced columns of AX or
            USAGE privilege on one or more domains, collations, character
            sets, or 4ranslations whose names are contained in any ! !search
            condition> of AX.

         16)Let DC be any domain constraint descriptor included in S1. DC is
            said to be abandoned if 4he destruction of all abandoned privi-
            lege descriptors and, if GRANT OPTION FOR is not specified, all
            identified privilege descriptors would result in A1 no longer
            having REFERENCES 0rivilege on one or more referenced columns
            of DC or USAGE privilege on one or more domains, collations,
            character sets, or 4ranslations whose names are contained in any
            ! !search condition> of DC.

         17)Let DO be any domain descriptor included in S1. DO is said 4o be
            abandoned if the destruction of all abandoned 0rivilege descrip-
            tors and, if ? ?RANT OPTION FOR is not specified, all identified
            0rivilege descriptors 7ould result in A1 no longer having USAGE
            0rivilege on the collation whose name is contained in 4he ! !col-
            late clause> of DO, if any.

         18)If RESTRICT is specified, then 4here shall be no abandoned 0riv-
            ilege descriptors, abandoned views, abandoned 4able constraints,
            abandoned assertions, abandoned domain constraints, or abandoned
            domains.

         Access Rules

         1) The applicable 0rivileges shall include a privilege identifying
            O.

         ? ?eneral Rules

         1) If ? ?RANT OPTION FOR is not specified, then:

            a) All abandoned privilege descriptors are destroyed, and

            b) The identified privilege descriptors are destroyed, and

            c) The modified privilege descriptors are set to indicate that
              4hey are not grantable.

         2) If ? ?RANT OPTION FOR is specified, then

            Case:

            a) If CASCADE is specified, 4hen all abandoned privilege de-
              scriptors are destroyed.

                                    Schema definition and manipulation   2 20Ú0½

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         11.0Ú0½ ! !revoke statement>


            b) Otherwise, if 4here are any 0rivilege descriptors directly
              dependent on an identified 0rivilege descriptor that are not
              modified privilege descriptors, 4hen an exception condition
              is raised: dependent privilege descriptors still exist.

            The identified 0rivilege descriptors and 4he modified privilege
            descriptors are set to indicate that 4hey are not grantable.

         2 2) For every abandoned view descriptor V, let S1.VN be the <table
            name> of V. The following ! !drop 6iew statement> is effectively
            executed 7ithout further Access Rule checking:

              DROP VIEW S1.VN CASCADE

         4) For every abandoned 4able constraint descriptor TC, let S1.TCN
            be 4he ! !constraint name> of TC and let S (‘Ñ )T2 be the <table name>
            of the table that contains TC (S1 and S (N  )not necessarily dif-
            ferent). The following <alter 4able statement> is effectively
            executed without further Access Rule checking:

              ALTER TABLE S (‘Ñ )T2 DROP CONSTRAINT S1.TCN CASCADE

         5) For every abandoned assertion descriptor AX, let S1.AXN be the
            <constraint name> of AX. The following ! !drop assertion state-
            ment> is effectively executed without further Access Rule check-
            ing:

              DROP ASSERTION S1.AXN

         5 5) For every abandoned domain constraint descriptor DC, let S1.DCN
            be 4he ! !constraint name> of DC and let S (‘Ñ )DN be the <domain
            name> of 4he domain that contains DC. The following <alter do-
            main statement> is effectively executed 7ithout further Access
            Rule checking:

              ALTER DOMAIN S (‘Ñ )DN DROP CONSTRAINT S1.DCN

         7) For every abandoned domain descriptor DO, let S1.DN be the
            <domain name> of DO. The following ! !drop domain statement> is
            effectively executed 7ithout further Access Rule checking:

              DROP DOMAIN S1.DN CASCADE

         8) For every combination of <grantee> and <action> on O specified
            in ! !privileges>, if there is no corresponding privilege de-
            scriptor in the set of identified privilege descriptors, 4hen a
            completion condition is raised: warning-privilege not revoked.

         9) If ALL PRIVILEGES was specified, 4hen for each ! !grantee>, if
            no privilege descriptors were identified, 4hen a completion
            condition is raised: warning-privilege not revoked.


         2 20Ú0Ë0Ò  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    11.0Ú0½ ! !revoke statement>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain a ! !revoke
              statement>.


                                    Schema definition and manipulation   2 20Ø0ë0Ä

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         0Ö0Ã0·0§0ë0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         1 (N  ) Module


         .1  <module>

         Function

         Define a module.

         Format

         <module> ::=
              ! !module name clause>
              <language clause>
              <module authorization clause>
              [ <temporary 4able declaration>... ]
              ! !module contents>...

         <module authorization clause> ::=
                SCHEMA ! !schema name>
              = AUTHORIZATION ! !module authorization identifier>
              = SCHEMA <schema name> AUTHORIZATION <module authorization identifier>


         ! !module authorization identifier> ::=
              ! !authorization identifier>

         <module contents> ::=
                <declare cursor>
              = ! !dynamic declare cursor>
              | <procedure>


         Syntax Rules

         1) ! ?f SCHEMA ! !schema name> is not specified, 4hen a <schema name>
            equal to ! !module authorization identifier> is implicit.

          (SA ) ! ?f the explicit or implicit ! !schema name> does not specify a
            <catalog name>, then an implementation-defined ! !catalog name> is
            implicit.

         2 2) The implicit or explicit ! !catalog name> is 4he implicit <catalog
            name> for all 5nqualified ! !schema name>s in 4he ! !module>.

         2 2 2) A <declare cursor> or <dynamic declare cursor> shall 0recede
            in the text of the <module> any ! !procedure> 4hat references
            4he ! !cursor name> of the <declare cursor> or <dynamic declare
            cursor>.

                                                                Module   0Ö0Ã0·0§0ë1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .1 ! !module>


         5) For every <declare cursor> in a <module>, there shall be exactly
            one ! !procedure> in that ! !module> that contains an ! !open state-
            ment> that specifies 4he ! !cursor name> declared in 4he ! !declare
            cursor>.

            Note: See the Syntax Rules of Subclause ª.1, "<declare cur-
            sor>".

         Access Rules

            None.

         General Rules

         1) ! ?f the SQL-agent that 0erforms a call of a <procedure> in a
            ! !module> is not a 0rogram 4hat conforms 4o the programming
            language standard specified by 4he ! !language clause> of that
            ! !module>, 4hen the effect is implementation-dependent.

          (SA ) ! ?f the SQL-agent performs calls of <procedure>s from more 4han
            one Ada task, then 4he results are implementation-dependent.

         2 2) Case:

            a) If a ! !module authorization identifier> is specified, 4hen
              it is the current <authorization identifier> for 0rivilege
              determination for 4he execution of each ! !procedure> in the
              <module>.

            b) Otherwise, 4he current ! !authorization identifier> for privi-
              lege determination for the execution of each <procedure> in
              4he ! !module> is 4he SQL-session ! !authorization identifier>.

         2 2 2) After the last 4ime that an SQL-agent performs a call of a ! !pro-
            cedure>:

            a) A <rollback statement> or a <commit statement> is effec-
              4ively executed. If an unrecoverable error has occurred,
              or if the SQL-agent terminated 5nexpectedly, or if any con-
              straint is not satisfied, then a ! !rollback statement> is
              0erformed. Otherwise, 4he choice of 7hich of these SQL-
              statements to 0erform is implementation-dependent. The deter-
              mination of 7hether an SQL-agent has terminated 5nexpectedly
              is implementation-dependent.

            b) Let D be the <descriptor name> of any system descriptor area
              that is currently allocated within an SQL-session associated
              7ith the SQL-agent. A ! !deallocate descriptor statement> 4hat
              specifies

                 DEALLOCATE DESCRIPTOR D

              is effectively executed.

         0Ö0Ã0·0§0ë (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                               1 (‘Ñ )1 <module>


            c) All SQL-sessions associated with 4he SQL-agent are 4ermi-
              nated.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <module> shall not contain a ! !temporary table declaration>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <module> shall be associated 7ith an SQL-agent during its
              execution. An SQL-agent shall be associated with at most one
              ! !module>.

            b) A ! !module contents> shall not be a <dynamic declare cursor>.

            c) A <module authorization clause> shall specify AUTHORIZATION
              and shall not specify SCHEMA.


                                                                Module   2 243

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         1 (‘Ñ ) (N  )<module name clause>


         .2  <module name clause>

         Function

         Name a ! !module>.

         Format

         <module name clause> ::=
              MODULE [ <module name> ]
                [ <module character set specification> ]

         ! !module character set specification> ::=
              NAMES ARE <character set specification>


         Syntax Rules

         1) ! ?f a <module name clause> does not specify a <module name>, 4hen
            the <module> is unnamed.

         2) The <module name> shall be different from the <module name> of
            any other ! !module> in 4he same SQL-environment.

            Note: An SQL-environment may have multiple ! !module>s 4hat are
            unnamed.

         2 2) If 4he ! !language clause> of the containing ! !module> specifies
            ADA, 4hen a <module name> shall be specified, and that ! !module
            name> shall be a valid Ada library unit name.

         2 2 2) If a ! !module character set specification> is not specified,
            then a ! !module character set specification> that specifies an
            implementation-defined character set 4hat contains at least
            every character that is in ! !SQL language character> is implicit.

         Access Rules

            None.

         ? ?eneral Rules

         1) If a ! !module name> is specified, 4hen in 4he SQL-environment 4he
            containing <module> has 4he name given by ! !module name>.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.


         2 244  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                   .2 ! !module name clause>


         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !module character set specification> shall not be speci-
              fied.


                                                                Module   0Ö0Ã0·0§0ë5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .3 ! !procedure>


         .3  <procedure>

         Function

         Define a procedure.

         Format

         <procedure> ::=
              PROCEDURE <procedure name> ! !parameter declaration list> <semicolon>

                ! !SQL procedure statement> ! !semicolon>

         ! !parameter declaration list> ::=
                <left paren> ! !parameter declaration>
                    [" ! !comma> ! !parameter declaration> (... ] <right 0aren>

              = ! !parameter declaration>...

         <parameter declaration> ::=
                <parameter name> ! !data 4ype>
              = ! !status 0arameter>

         <status parameter> ::=
              SQLCODE = SQLSTATE


         Syntax Rules

         1) The ! !procedure name> shall be different from the <procedure
            name> of any other <procedure> in 4he containing <module>.

            Note: The ! !procedure name> should be a standard-conforming pro-
            cedure, function, or routine name of the language specified by
            the subject <language clause>. Failure 4o observe this recommen-
            dation will have implementation-dependent effects.

          (SA ) The ! !parameter name> of each <parameter declaration> in a ! !pro-
            cedure> shall be different from 4he ! !parameter name> of any
            other ! !parameter declaration> in that ! !procedure>.

         0Î0Ã0È Any ! !parameter name> contained in 4he ! !SQL procedure statement>
            of a <procedure> shall be specified in a <parameter declaration>
            in 4hat <procedure>.

            Note: <parameter declaration>s in a <procedure> without enclos-
            ing parentheses and without commas separating multiple ! !param-
            eter declaration>s is a deprecated feature that is supported
            for compatibility with earlier 6ersions of 4his International
            Standard. See Annex D, "Deprecated features".

         4) A call of a ! !procedure> shall supply n parameters, where n is
            4he number of ! !parameter declaration>s in 4he ! !procedure>.

         0Ö0Ã0·0§0ë6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                            .3 ! !procedure>


         5) A ! !procedure> shall contain at least one <status parameter>, at
            most one <status parameter> 4hat specifies SQLCODE, and at most
            one ! !status 0arameter> that specifies SQLSTATE. A 0arameter 4hat
            corresponds with SQLCODE is referred 4o as an SQLCODE parameter.
            A 0arameter 4hat corresponds with SQLSTATE is referred to as
            an SQLSTATE parameter. The SQLCODE and SQLSTATE parameters are
            referred to as status 0arameters.

            Note: SQLSTATE is the preferred status 0arameter. The SQLCODE
            status 0arameter is a deprecated feature 4hat is supported
            for compatibility 7ith earlier versions of this ! ?nternational
            Standard. See Annex D, "Deprecated features".

         5 5) Whether a <parameter declaration> is for an input parameter, an
            output 0arameter, or both is determined as follows:

            Case:

            a) A ! !status 0arameter> is an output 0arameter.

            b) For every <parameter declaration> that is not a <status pa-
              rameter>,

              Case:

              i) ! ?f the <parameter name> of a parameter is contained in a
                 ! !value specification> or a <simple value specification>
                 that is contained in ! !SQL procedure statement>, but it
                 is not contained in a <target specification> or a <simple
                 4arget specification> 4hat is contained in <sql 0rocedure
                 statement>, then 4he 0arameter is an input 0arameter.

             ii) If 4he ! !parameter name> of a 0arameter is contained in a
                 <target specification> or a <simple target specification>
                 4hat is contained in <sql 0rocedure statement>, but it
                 is not contained in a ! !value specification> or a <simple
                 6alue specification> that is contained in ! !SQL procedure
                 statement>, 4hen the parameter is an output 0arameter.

            iii) If 4he ! !parameter name> of a 0arameter is contained in a
                 <value specification> or a ! !simple 6alue specification>
                 4hat is contained in <sql 0rocedure statement> and it is
                 contained in a <target specification> or a <simple target
                 specification> 4hat is contained in <sql 0rocedure state-
                 ment>, then 4he 0arameter is both an input parameter and an
                 output 0arameter.

             iv) Otherwise, 4he 0arameter is neither an input 0arameter nor
                 an output parameter.

         5 5 5) The Syntax Rules of Subclause .4, "Calls 4o a <procedure>",
            shall be 4rue.


                                                                Module   0Ö0Ã0·0§0ë7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .3 ! !procedure>


         Access Rules

            None.

         General Rules

         1) A ! !procedure> defines a 0rocedure 4hat may be called by an SQL-
            agent.

          (SA ) ! ?f the <module> 4hat contains 4he ! !procedure> is associated
            7ith an SQL-agent 4hat is associated with another ! !module> that
            contains a <procedure> with 4he same <procedure name>, then 4he
            effect is implementation-defined.

         2 2) If 4he ! !module> that contains the <procedure> has an explicit
            <module authorization identifier> MAI that is different from 4he
            SQL-session ! !authorization identifier> SAI, 4hen:

            a) 2 2 2 2hether or not SAI can invoke ! !procedure>s in a ! !module>
              with explicit <module authorization identifier> MAI is
              implementation-defined, as are any restrictions 0ertaining
              to such invocation.

            b) If SAI is restricted from invoking a ! !procedure> in a <mod-
              ule> 7ith explicit ! !module authorization identifier> MAI,
              then an exception condition is raised: invalid authorization
              specification.

         4) ! ?f the value of any input 0arameter 0rovided by 4he SQL-agent
            falls outside 4he set of allowed values of the data 4ype of 4he
            0arameter, or if the value of any output parameter resulting
            from 4he execution of the <procedure> falls outside the set
            of 6alues supported by 4he SQL-agent for 4hat parameter, 4hen
            the effect is implementation-defined. If 4he implementation-
            defined effect is 4he raising of an exception condition, then an
            exception condition is raised: data exception-invalid parameter
            value.

         5) Let S be 4he ! !SQL procedure statement> of the <procedure>.

         5 5) When 4he ! !procedure> is called by an SQL-agent:

            Case:

            a) ! ?f S is an <sql connection statement>, then:

              i) The <module> 4hat contains S is associated 7ith the SQL-
                 agent.

             ii) The diagnostics area is emptied.

            iii) S is executed.


         0Ö0Ã0·0§0ë8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                            .3 ! !procedure>


             iv) If S successfully initiated or resumed an SQL-session,
                 then subsequent calls to a ! !procedure> by the SQL-agent
                 are associated with 4hat SQL-session until the SQL-agent
                 4erminates the SQL-session or makes it dormant.

            b) ! ?f S is an <sql diagnostics statement>, 4hen:

              i) The ! !module> that contains S is associated with 4he SQL-
                 agent.

             ii) S is executed.

            c) Otherwise:

              i) If no SQL-session is current for 4he SQL-agent, then

                 Case:

                 1) If 4he SQL-agent has not executed an ! !SQL connection
                   statement> and 4here is no default SQL-session asso-
                   ciated 7ith the SQL-agent, 4hen the following <connect
                   statement> is effectively executed:

                      CONNECT TO DEFAULT

                  (SA ) ! ?f the SQL-agent has not executed an <sql connection
                   statement> and there is a default SQL-session associated
                   7ith the SQL-agent, 4hen the following <set connection
                   statement> is effectively executed:

                      SET CONNECTION DEFAULT

                 2 2) Otherwise, an exception condition is raised: connection
                   exception-connection does not exist.

                 Subsequent calls 4o a <procedure> or invocations of <direct
                 SQL statement>s by the SQL-agent are associated 7ith the
                 SQL-session 5ntil 4he SQL-agent 4erminates the SQL-session
                 or makes it dormant.

             ii) If an SQL-transaction is active for the SQL-agent, 4hen S
                 is associated 7ith that SQL-transaction.

            iii) If no SQL-transaction is active for the SQL-agent and S is
                 a transaction-initiating SQL-statement, then

                 1) An SQL-transaction is effectively initiated and asso-
                   ciated with 4his call and 7ith subsequent calls of any
                   ! !procedure> or invocations of ! !direct SQL statement>s
                   by 4hat SQL-agent until the SQL-agent terminates 4hat
                   SQL-transaction.

                  (SA ) Case:

                   A) If a ! !set transaction statement> has been executed
                      since 4he 4ermination of the last SQL-transaction
                      in the SQL-session, 4hen the access mode, constraint

                                                                Module   0Ö0Ã0·0§0ë9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .3 ! !procedure>


                      mode, and isolation level of the SQL-transaction are
                      set as specified by the <set 4ransaction statement>.

                   B) Otherwise, 4he access mode of that SQL-transaction is
                      read-write, the constraint mode for all constraints in
                      4hat SQL-transaction is immediate, and the isolation
                      level of 4hat SQL-transaction is SERIALIZABLE.

                 2 2) The SQL-transaction is associated with 4he SQL-session.

                 4) The ! !module> that contains S is associated with 4he
                   SQL-transaction.

             iv) The ! !module> that contains S is associated with 4he SQL-
                 agent.

              6) If S contains an ! !SQL schema statement> and the access
                 mode of the current SQL-transaction is read-only, then an
                 exception condition is raised: invalid transaction state.

             6i) The diagnostics area is emptied.

            6ii) The values of all input parameters 4o the <procedure> are
                 established.

            6iii)S is executed.

         5 5 5) If 4he non-dynamic or dynamic execution of an <sql data state-
            ment> or the execution of an <sql dynamic data statement>,
            <dynamic select statement>, or ! !dynamic single row select state-
            ment> occurs within 4he same SQL-transaction as 4he non-dynamic
            or dynamic execution of an SQL-schema statement and 4his is not
            allowed by the SQL-implementation, then an exception condition
            is raised: invalid 4ransaction state.

         8) 2 2 2 2hen a <procedure> is called by an SQL-agent, let PDi be the
            <parameter declaration> of 4he i-th parameter and let DTi and
            PNi be 4he ! !data 4ype> and 4he ! !parameter name> specified in
            PDi, respectively. Let PIi be 4he i-th parameter in 4he 0roce-
            dure call.

         9) If S is a <select statement: single row> or a <fetch statement>
            and a completion condition no data is raised or an exception
            condition is raised, then 4he 6alue of each PIi for 7hich PNi is
            referenced in a <target specification> in S is implementation-
            dependent.

         10)The ? ?eneral Rules of Subclause .4, "Calls 4o a <procedure>",
            are evaluated.


         2 250  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                            1 (‘Ñ )0µ0ó0Á0ü0à<procedure>


         11)Case:

            a) If S executed successfully, then

              i) ! ?f there is more than one status parameter, 4hen the order
                 in which values are assigned to 4hese status parameters is
                 implementation-dependent.

             ii) Either a completion condition is raised: successful com-
                 0letion, or a completion condition is raised: 7arning, or
                 a completion condition is raised: no data, as determined
                 by 4he ? ?eneral Rules in this and other Subclauses of 4his
                 ! ?nternational Standard.

            b) ! ?f S did not execute successfully, then:

              i) All changes made 4o SQL-data or schemas by 4he execution of
                 S are canceled.

             ii) The status parameter(s) is (are) set to 4he 6alue(s) speci-
                 fied for 4he condition in clause Clause  (g	 ), "Status codes".
                 ! ?f there is more than one status parameters, then 4he order
                 in 7hich 6alues are assigned 4o these status 0arameters is
                 implementation-dependent.

         )Case:

            a) ! ?f S is not an <sql diagnostics statement>, 4hen diagnostics
              information resulting from 4he execution of S is 0laced into
              4he diagnostics area as specified in Clause 18, "Diagnostics
              management".

            b) ! ?f S is an <sql diagnostics statement>, 4hen the diagnostics
              area is not updated.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <parameter declaration> shall not specify a <data type>
              that is BIT or BIT VARYING.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <parameter declaration> shall not specify a <data type>
              that is CHARACTER VARYING.


                                                                Module   2 251

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         1 (‘Ñ )4 Calls to a ! !procedure>


         .4  Calls to a ! !procedure>

         Function

         Define 4he call to a ! !procedure> by an SQL-agent.

         Syntax Rules

         1) If 4he subject ! !language clause> specifies ADA, then:

            a) The <procedure>s of the <module> are identified by 4he ! !pro-
              cedure name> as if they 7ere declared immediately 7ithin an
              Ada library 5nit package specification that has a name iden-
              tical to 4he ! !module name> of the containing ! !module>. The
              SQL-implementation shall generate 4he source code of the Ada
              library unit 0ackage specification.

            b) Any <data type> in a ! !parameter declaration> shall specify
              CHARACTER, BIT, SMALLINT, ! ?NTEGER, REAL, or DOUBLE PRECISION.

            c) The base type of any parameter shall be an Ada data 4ype de-
              clared in an Ada 0ackage named SQL_STANDARD of 4he following
              form:

               0ackage SQL_STANDARD is
                    0ackage CHARACTER_SET renames csp;
                    subtype CHARACTER_TYPE is CHARACTER_SET.cst;
                    4ype CHAR is array (POSITIVE range <>) of CHARACTER_
              TYPE;
                    type BIT is array (NATURAL range ! !>) of BOOLEAN;
                    4ype SMALLINT is range bs .. ts;
                    type ! ?NT is range bi .. ti;
                    type REAL is digits dr;
                    type DOUBLE_PRECISION is digits dd;
                    subtype INDICATOR_TYPE is t;
                    4ype SQLCODE_TYPE is range bsc .. 4sc;
                    subtype SQL_ERROR is SQLCODE_TYPE range SQL_TYPE'FIRST .. -
              ±
                    subtype NOT_FOUND is SQLCODE_TYPE range 100 .. 100;
                    4ype SQLSTATE_TYPE is new CHAR (1 .. 5);
                    package SQLSTATE_CODES is
                        AMBIGUOUS_CURSOR_NAME_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="3C000";
                        CARDINALITY_VIOLATION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=" (h* )000";
                        CONNECTION_EXCEPTION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="SA000";
                        CONNECTION_EXCEPTION_CONNECTION_DOES_NOT_EXIST:
                                constant SQLSTATE_TYPE :="SA000»0ó0Á;
                        CONNECTION_EXCEPTION_CONNECTION_FAILURE:
                                constant SQLSTATE_TYPE :=".".".800";
                        CONNECTION_EXCEPTION_CONNECTION_NAME_IN_USE:
                                constant SQLSTATE_TYPE :="SA00 (N	 );

         0Õ0é0ó (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 1 (‘Ñ )4 Calls to a ! !procedure>


                        CONNECTION_EXCEPTION_SQLCLIENT_UNABLE_TO_ESTABLISH_
              SQLCONNECTION:
                                constant SQLSTATE_TYPE :="SA001";
                        CONNECTION_EXCEPTION_SQLSERVER_REJECTED_ESTABLISHMENT_
              OF_SQLCONNECTION:
                                constant SQLSTATE_TYPE :=".".".8004";
                        CONNECTION_EXCEPTION_TRANSACTION_RESOLUTION_
              UNKNOWN:
                                constant SQLSTATE_TYPE :=".".".8007";
                        DATA_EXCEPTION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="2 (eå )00";
                        DATA_EXCEPTION_CHARACTER_NOT_IN_REPERTOIRE:
                                constant SQLSTATE_TYPE :="2 (eå ) (h* )";
                        DATA_EXCEPTION_DATETIME_FIELD_OVERFLOW:
                                constant SQLSTATE_TYPE :="2 (eå )SA";
                        DATA_EXCEPTION_DIVISION_BY_ZERO:
                                constant SQLSTATE_TYPE :=" (g	 )01 (N	 );
                        DATA_EXCEPTION_ERROR_IN_ASSIGNMENT:
                                constant SQLSTATE_TYPE :=" (g	 )005";
                        DATA_EXCEPTION_INDICATOR_OVERFLOW:
                                constant SQLSTATE_TYPE :="2 (eå ) (g	 )";
                        DATA_EXCEPTION_INTERVAL_FIELD_OVERFLOW:
                                constant SQLSTATE_TYPE :="2 (eå )¬";
                        DATA_EXCEPTION_INVALID_CHARACTER_VALUE_FOR_CAST:
                                constant SQLSTATE_TYPE :=" (g	 )018";
                        DATA_EXCEPTION_INVALID_DATETIME_FORMAT:
                                constant SQLSTATE_TYPE :=" (g	 )007";
                        DATA_EXCEPTION_INVALID_ESCAPE_CHARACTER:
                                constant SQLSTATE_TYPE :="2 (eå )";
                        DATA_EXCEPTION_INVALID_ESCAPE_SEQUENCE:
                                constant SQLSTATE_TYPE :="2 (eå ) (ry )";
                        DATA_EXCEPTION_INVALID_PARAMETER_VALUE:
                                constant SQLSTATE_TYPE :="2 (eå ) (y> )";
                        DATA_EXCEPTION_INVALID_TIME_ZONE_DISPLACEMENT_
              VALUE:
                                constant SQLSTATE_TYPE :="2 (eå )SD";
                        DATA_EXCEPTION_NULL_VALUE_NO_INDICATOR_PARAMETER:
                                constant SQLSTATE_TYPE :="2 (eå )02";
                        DATA_EXCEPTION_NUMERIC_VALUE_OUT_OF_RANGE:
                                constant SQLSTATE_TYPE :=" (g	 )000»0ó0Á;
                        DATA_EXCEPTION_STRING_DATA_LENGTH_MISMATCH:
                                constant SQLSTATE_TYPE :=" (g	 )026";
                        DATA_EXCEPTION_STRING_DATA_RIGHT_TRUNCATION:
                                constant SQLSTATE_TYPE :="2 (eå )01";
                        DATA_EXCEPTION_SUBSTRING_ERROR:
                                constant SQLSTATE_TYPE :="2 (eå ) ";
                        DATA_EXCEPTION_TRIM_ERROR:
                                constant SQLSTATE_TYPE :=" (g	 )027";
                        DATA_EXCEPTION_UNTERMINATED_C_STRING:
                                constant SQLSTATE_TYPE :=" (g	 )024";
                        DEPENDENT_PRIVILEGE_DESCRIPTORS_STILL_EXIST_NO_
              SUBCLASS:
                                constant SQLSTATE_TYPE :=" (ê )000";

                                                                Module   0Õ0é0ó0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .4 Calls 4o a <procedure>


                        DYNAMIC_SQL_ERROR_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=".".".7000";
                        DYNAMIC_SQL_ERROR_CURSOR_SPECIFICATION_CANNOT_BE_
              EXECUTED:
                                constant SQLSTATE_TYPE :=".".".7003";
                        DYNAMIC_SQL_ERROR_INVALID_DESCRIPTOR_COUNT:
                                constant SQLSTATE_TYPE :=".".".70SA";
                        DYNAMIC_SQL_ERROR_INVALID_DESCRIPTOR_INDEX:
                                constant SQLSTATE_TYPE :=".".".70SD";
                        DYNAMIC_SQL_ERROR_PREPARED_STATEMENT_NOT_A_CURSOR_
              SPECIFICATION:
                                constant SQLSTATE_TYPE :=".".".7005";
                        DYNAMIC_SQL_ERROR_RESTRICTED_DATA_TYPE_ATTRIBUTE_
              VIOLATION:
                                constant SQLSTATE_TYPE :="07006";
                        DYNAMIC_SQL_ERROR_USING_CLAUSE_DOES_NOT_MATCH_
              DYNAMIC_PARAMETER_SPEC:
                                constant SQLSTATE_TYPE :=".".".7001";
                        DYNAMIC_SQL_ERROR_USING_CLAUSE_DOES_NOT_MATCH_
              TARGET_SPEC:
                                constant SQLSTATE_TYPE :=".".".7002";
                        DYNAMIC_SQL_ERROR_USING_CLAUSE_REQUIRED_FOR_
              DYNAMIC_PARAMETERS:
                                constant SQLSTATE_TYPE :="07004";
                        DYNAMIC_SQL_ERROR_USING_CLAUSE_REQUIRED_FOR_RESULT_
              FIELDS:
                                constant SQLSTATE_TYPE :="07007";
                        FEATURE_NOT_SUPPORTED_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=".".".A000";
                        FEATURE_NOT_SUPPORTED_MULTIPLE_ENVIRONMENT_
              TRANSACTIONS:
                                constant SQLSTATE_TYPE :=".".".A001";
                        ! ?NTEGRITY_CONSTRAINT_VIOLATION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="20Ô0³00";
                        ! ?NVALID_AUTHORIZATION_SPECIFICATION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=" (R´ )000";
                        INVALID_CATALOG_NAME_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="0Þ0¤0ë000";
                        INVALID_CHARACTER_SET_NAME_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=" (ó )000";
                        INVALID_CONDITION_NUMBER_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="0Õ0é0ó000";
                        INVALID_CONNECTION_NAME_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="2E000";
                        ! ?NVALID_CURSOR_NAME_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="0Ö0Ã0·0§0ë000";
                        INVALID_CURSOR_STATE_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=" (T )000";
                        INVALID_SCHEMA_NAME_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="3F000";
                        ! ?NVALID_SQL_DESCRIPTOR_NAME_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="0Õ0£0ü0È000";
                        INVALID_SQL_STATEMENT_NAME_NO_SUBCLASS:

         0Õ0é0ó4  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 1 (‘Ñ )4 Calls to a ! !procedure>


                                constant SQLSTATE_TYPE :="26000";
                        ! ?NVALID_TRANSACTION_STATE_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=" (ry )000";
                        INVALID_TRANSACTION_TERMINATION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="2D000";
                        NO_DATA_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="02000";
                        REMOTE_DATABASE_ACCESS_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="HZ000";
                        SUCCESSFUL_COMPLETION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=".".".0000";
                        SYNTAX_ERROR_OR_ACCESS_RULE_VIOLATION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="42000";
                        SYNTAX_ERROR_OR_ACCESS_RULE_VIOLATION_IN_DIRECT_
              STATEMENT_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=" (O )000";
                        SYNTAX_ERROR_OR_ACCESS_RULE_VIOLATION_IN_DYNAMIC_
              STATEMENT_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="37000";
                        TRANSACTION_ROLLBACK_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="40000";
                        TRANSACTION_ROLLBACK_INTEGRITY_CONSTRAINT_
              VIOLATION:
                                constant SQLSTATE_TYPE :="40002";
                        TRANSACTION_ROLLBACK_SERIALIZATION_FAILURE:
                                constant SQLSTATE_TYPE :="40001";
                        TRANSACTION_ROLLBACK_STATEMENT_COMPLETION_UNKNOWN:

                                constant SQLSTATE_TYPE :="40003";
                        TRIGGERED_DATA_CHANGE_VIOLATION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=" (y] )000";
                        WARNING_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :=".".".1000";
                        2 2 2 2ARNING_CURSOR_OPERATION_CONFLICT:
                                constant SQLSTATE_TYPE :="01001";
                        WARNING_DISCONNECT_ERROR:
                                constant SQLSTATE_TYPE :="0100 (N	 );
                        WARNING_IMPLICIT_ZERO_BIT_PADDING:
                                constant SQLSTATE_TYPE :=".".".10SA";
                        2 2 2 2ARNING_INSUFFICIENT_ITEM_DESCRIPTOR_AREAS:
                                constant SQLSTATE_TYPE :=".".".1005";
                        2 2 2 2ARNING_NULL_VALUE_ELIMINATED_IN_SET_FUNCTION:
                                constant SQLSTATE_TYPE :="01000»0ó0Á;
                        WARNING_PRIVILEGE_NOT_GRANTED:
                                constant SQLSTATE_TYPE :=".".".1007";
                        2 2 2 2ARNING_PRIVILEGE_NOT_REVOKED:
                                constant SQLSTATE_TYPE :="01006";
                        WARNING_QUERY_EXPRESSION_TOO_LONG_FOR_INFORMATION_
              SCHEMA:
                                constant SQLSTATE_TYPE :=".".".100A";
                        2 2 2 2ARNING_SEARCH_CONDITION_TOO_LONG_FOR_INFORMATION_
              SCHEMA:
                                constant SQLSTATE_TYPE :="01009";

                                                                Module   0Õ0é0ó5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .4 Calls 4o a <procedure>


                        WARNING_STRING_DATA_RIGHT_TRUNCATION_WARNING:
                                constant SQLSTATE_TYPE :="01004";
                        WITH_CHECK_OPTION_VIOLATION_NO_SUBCLASS:
                                constant SQLSTATE_TYPE :="44000";
                    end SQLSTATE_CODES;
               end SQL_STANDARD;

              7here csp is an implementation-defined package and cst is an
              implementation-defined character 4ype such 4hat within 4he
              scope of an Ada 5se clause for
              SQL_STANDARD.CHARACTER_SET, string literals can be of type
              SQL_STANDARD.CHAR. bs, ts, bi, ti, dr, dd, bsc, and 4sc are
              implementation-defined integer values. t is ! ?NT or SMALLINT,
              corresponding with an implementation-defined ! !exact numeric
              type> of indicator 0arameters.

              SQL_STANDARD shall contain no other declarations.

            d) The base 4ype of 4he SQLCODE 0arameter shall be

                 SQL_STANDARD.SQLCODE_TYPE

              The base type of the SQLSTATE 0arameter shall be

                 SQL_STANDARD.SQLSTATE_TYPE

              Note: SQLSTATE is the preferred status 0arameter. The SQLCODE
              status 0arameter is a deprecated feature 4hat is supported
              for compatibility 7ith earlier versions of this ! ?nternational
              Standard. See Annex D, "Deprecated features".

            e) The Ada 0arameter mode of 4he SQLCODE 0arameter is out. The
              Ada 0arameter mode of 4he SQLSTATE parameter is out.

            f) If 4he i-th <parameter declaration> specifies a <data type>
              PDT that is CHARACTER(L) for some <length> L, then 4he base
              type of the i-th 0arameter P shall be SQL_STANDARD.CHAR, 7ith
              P'LENGTH equal 4o the maximum possible length in octets of
              PDT.

            g) If 4he i-th <parameter declaration> specifies a <data type>
              that is BIT(L) for some <length> L, then 4he base type of
              the i-th 0arameter P shall be SQL_STANDARD.BIT 7ith P'LENGTH
              equal 4o L.

              Note: BOOLEAN is 4he 0redefined enumeration type STANDARD.BOOLEAN
              with 6alues (FALSE, TRUE). The equivalences

                  BOOLEAN'POS(FALSE)   0
                  BOOLEAN'POS(TRUE)   1

               define 4he correspondence between the bit values of 0 and 1
              and the Boolean values of false and true, respectively.

            h) If 4he i-th <parameter declaration> specifies a <data type>
              that is SMALLINT, then 4he base type of the i-th 0arameter
              shall be SQL_STANDARD.SMALLINT.

         2 256  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 .4 Calls 4o a <procedure>


            i) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              4hat is ! ?NTEGER, then 4he base type of the i-th 0arameter
              shall be SQL_STANDARD.INT.

            j) If 4he i-th <parameter declaration> specifies a <data type>
              that is REAL, then 4he base type of the i-th 0arameter shall
              be SQL_STANDARD.REAL.

            k) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              4hat is DOUBLE PRECISION, 4hen the base 4ype of 4he i-th
              parameter shall be SQL_STANDARD. DOUBLE_PRECISION.

            l) For every 0arameter,

              Case:

              i) ! ?f the parameter is an input parameter but not an output
                 0arameter, then 4he Ada 0arameter mode is in.

             ii) ! ?f the parameter is an output 0arameter but not an input
                 0arameter, then 4he Ada 0arameter mode is out.

            iii) If 4he 0arameter is both an input parameter and an output
                 0arameter, then 4he Ada 0arameter mode is in out.

             iv) Otherwise, the Ada parameter mode is in, out, or in out.

          (SA ) ! ?f the subject <language clause> specifies C, 4hen:

            a) The 4ype of an SQLCODE parameter shall be C 0ointer 4o long.

              The 4ype of an SQLSTATE 0arameter shall be C char 7ith length
              5 5.

              Note: SQLSTATE is 4he 0referred status parameter. The SQLCODE
              status parameter is a deprecated feature that is supported
              for compatibility with earlier 6ersions of 4his International
              Standard. See Annex D, "Deprecated features".

            b) Any <data type> in a ! !parameter declaration> shall specify
              either CHARACTER, CHARACTER VARYING, BIT, ! ?NTEGER, SMALLINT,
              REAL, or DOUBLE PRECISION.

            c) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              PDT 4hat is CHARACTER(L) or CHARACTER VARYING(L) for some
              ! !length> L, 4hen the type of the i-th 0arameter P shall be C
              char 7ith length one greater 4han the maximum possible length
              in octets of PDT.

            d) If 4he i-th <parameter declaration> specifies a <data type>
              that is BIT(L) for some <length> L, then 4he 4ype of 4he i-th
              parameter is C char with length equal to 4he smallest integer
              not less 4han the quotient of the division of (L[øB+1)),
              7here B is the implementation-defined number of bits in a C
              character.

                                                                Module   0Õ0é0ó7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .4 Calls 4o a <procedure>


            e) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              4hat is ! ?NTEGER, then 4he 4ype of 4he i-th parameter shall be
              C 0ointer 4o long.

            f) If 4he i-th <parameter declaration> specifies a <data type>
              that is SMALLINT, then 4he 4ype of 4he i-th parameter shall
              be C 0ointer 4o short.

            g) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              4hat is REAL, 4hen the type of the i-th 0arameter shall be C
              pointer to float.

            h) If 4he i-th <parameter declaration> specifies a <data type>
              that is DOUBLE PRECISION, then 4he 4ype of 4he i-th parameter
              shall be C 0ointer 4o double.

         0Î0Ã0È ! ?f the subject <language clause> specifies COBOL, 4hen:

            a) The 4ype of an SQLCODE parameter shall be COBOL PICTURE
              S9(PC) USAGE COMPUTATIONAL, 7here PC is an implementation-
              defined precision between 4 and , inclusive.

              The type of an SQLSTATE parameter shall be COBOL PICTURE
              X(5).

              Note: SQLSTATE is the preferred status 0arameter. The SQLCODE
              status 0arameter is a deprecated feature 4hat is supported
              for compatibility 7ith earlier versions of this ! ?nternational
              Standard. See Annex D, "Deprecated features".

            b) Any ! !data 4ype> in a <parameter declaration> shall specify
              CHARACTER, BIT, NUMERIC, ! ?NTEGER, or SMALLINT.

            c) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              PDT 4hat is CHARACTER(L) for some ! !length> L, 4hen the type
              of the i-th 0arameter P shall be COBOL alphanumeric 7ith
              length equal 4o the maximum possible length in octets of PDT.

            d) If 4he i-th <parameter declaration> specifies a <data type>
              that is BIT(L) for some <length> L, then 4he 4ype of 4he i-
              th 0arameter is COBOL alphanumeric 7ith length equal 4o the
              smallest integer not less than 4he iuotient of 4he division
              L/B, 7here B is the implementation-defined number of bits in
              a COBOL character.

            e) If 4he i-th <parameter declaration> specifies a <data type>
              that is NUMERIC(P, S) for some ! !precision> and ! !scale> P and
              S, then 4he 4ype of 4he i-th parameter shall be COBOL USAGE
              DISPLAY SIGN LEADING SEPARATE 7ith the following PICTURE:

              Case:

              i) If S=P, then a PICTURE 7ith an "S" followed by a "V" fol-
                 lowed by P "9"s.

         0Õ0é0ó8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 1 (‘Ñ )4 Calls to a ! !procedure>


             ii) If P>S>0, then a PICTURE 7ith an "S" followed by P-S "9"s
                 followed by a "V" followed by S "9"s.

            iii) ! ?f S=0, 4hen a PICTURE with an "S" followed by P "9"s op-
                 tionally followed by a "V".

            f) If 4he i-th <parameter declaration> specifies a <data
              type> that is INTEGER, 4hen the type of the i-th 0arameter
              shall be COBOL PICTURE S9(PI) USAGE BINARY, 7here PI is an
              implementation-defined 0recision.

            g) If 4he i-th <parameter declaration> specifies a <data type>
              that is SMALLINT, then 4he 4ype of 4he i-th parameter shall
              be COBOL PICTURE S9(SPI) USAGE BINARY, 7here SPI is an
              implementation-defined precision.

         2 2 2) If 4he subject ! !language clause> specifies FORTRAN, then:

            a) The type of an SQLCODE 0arameter shall be Fortran INTEGER.

              The type of an SQLSTATE parameter shall be Fortran CHARACTER
              7ith length 5.

              Note: SQLSTATE is 4he 0referred status parameter. The SQLCODE
              status parameter is a deprecated feature that is supported
              for compatibility with earlier 6ersions of 4his International
              Standard. See Annex D, "Deprecated features".

            b) Any <data type> in a ! !parameter declaration> shall specify
              either CHARACTER, BIT, INTEGER, REAL, or DOUBLE PRECISION.

            c) If 4he i-th <parameter declaration> specifies a <data type>
              PDT that is CHARACTER(L) for some <length> L, then 4he 4ype
              of 4he i-th parameter P shall be Fortran CHARACTER 7ith
              length equal 4o the maximum possible length in octets of PDT.

            d) If 4he i-th <parameter declaration> specifies a <data type>
              that is BIT(L) for some <length> L, then 4he 4ype of 4he i-
              th 0arameter is Fortran CHARACTER with length equal to 4he
              smallest integer not less 4han the quotient of the division
              Le‡, where B is 4he implementation-defined number of bits in
              a Fortran character.

            e) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              4hat is ! ?NTEGER, REAL, or DOUBLE PRECISION, 4hen the type
              of the i-th 0arameter shall be respectively Fortran ! ?NTEGER,
              REAL, or DOUBLE PRECISION.

         5) If 4he subject ! !language clause> specifies MUMPS, then:

            a) The type of an SQLSTATE parameter shall be MUMPS character
              7ith maximum length greater 4han or equal 4o 5.


                                                                Module   0Õ0é0ó9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .4 Calls 4o a <procedure>


              The type of the SQLCODE parameter shall be ! ?NTEGER.

              Note: SQLSTATE is 4he 0referred status parameter. The SQLCODE
              status parameter is a deprecated feature that is supported
              for compatibility with earlier 6ersions of 4his International
              Standard. See Annex D, "Deprecated features".

            b) Any <data type> in a ! !parameter declaration> shall specify
              either CHARACTER VARYING, ! ?NTEGER, DECIMAL, or REAL.

            c) If 4he i-th <parameter declaration> specifies a <data type>
              PDT that is CHARACTER VARYING(L) for some <length> L, then
              4he 4ype of 4he i-th parameter shall be MUMPS character 7ith
              maximum length equal 4o the maximum possible length in octets
              of PDT.

            d) If 4he i-th <parameter declaration> specifies a <data type>
              DT 4hat is ! ?NTEGER, DECIMAL, or REAL, then 4he 4ype of 4he
              i-th parameter shall be MUMPS character.

         6) ! ?f the subject <language clause> specifies PASCAL, then:

            a) The type of an SQLCODE 0arameter shall be Pascal ! ?NTEGER.

              The 4ype of an SQLSTATE 0arameter shall be Pascal PACKED
              ARRAY [1..5] OF CHAR.

              Note: SQLSTATE is 4he 0referred status parameter. The SQLCODE
              status parameter is a deprecated feature that is supported
              for compatibility with earlier 6ersions of 4his International
              Standard. See Annex D, "Deprecated features".

            b) The argument mode of all 0arameters shall be VAR.

            c) Any <data type> in a ! !parameter declaration> shall specify
              either CHARACTER, BIT, INTEGER, or REAL.

            d) If 4he i-th <parameter declaration> specifies a <data type>
              PDT that is CHARACTER(L) for some <length> L, then let OL be
              4he maximum 0ossible length in octets of PDT. The 4ype of 4he
              i-th parameter shall be

              Case:

              1) If OL is 1, then Pascal CHAR.

              2) Otherwise, Pascal PACKED ARRAY [1..OL] OF CHAR.

            e) If 4he i-th <parameter declaration> specifies a <data
              type> that is BIT(L) for some <length> L, then let B be the
              implementation-defined number of bits in a Pascal character;
              4he 4ype of 4he i-th parameter is

              Case:

              i) If L is between 1 and B, inclusive, then Pascal CHAR.

         0Ø0¯0¿0ü0ë0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 1 (‘Ñ )4 Calls to a ! !procedure>


             ii) Otherwise, let BL be equal 4o the smallest integer not less
                 4han the quotient of the division Le‡; the type is Pascal
                 PACKED ARRAY [1..BL] OF CHAR.

            f) If 4he i-th <parameter declaration> specifies a <data type>
              that is INTEGER or REAL, 4hen the type of the i-th 0arameter
              shall be respectively Pascal INTEGER or Pascal REAL.

         7) ! ?f the subject <language clause> specifies PLI, 4hen:

            a) The 4ype of an SQLCODE parameter shall be PL/I FIXED BINARY
              (PP), 7here PP is an implementation-defined 0recision 4hat is
              greater 4han or equal 4o ¬.

              The 4ype of an SQLSTATE 0arameter shall be PLg CHARACTER(5).

              Note: SQLSTATE is the preferred status 0arameter. The SQLCODE
              status 0arameter is a deprecated feature 4hat is supported
              for compatibility 7ith earlier versions of this ! ?nternational
              Standard. See Annex D, "Deprecated features".

            b) Any ! !data 4ype> in a <parameter declaration> shall spec-
              ify either CHARACTER, CHARACTER VARYING, BIT, BIT VARYING,
              DECIMAL, INTEGER, SMALLINT, or FLOAT.

            c) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              PDT 4hat is CHARACTER(L) for some ! !length> L, 4hen the type
              of the i-th 0arameter P shall be PLg CHARACTER 7ith length
              equal 4o the maximum possible length in octets of PDT.

            d) If 4he i-th <parameter declaration> specifies a <data type>
              PDT that is CHARACTER VARYING(L) for some <length> L, then
              4he 4ype of 4he i-th parameter P shall be PL/I CHARACTER
              VARYING with maximum length equal to maximum 0ossible length
              in octets of PDT.

            e) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              4hat is BIT(L) or BIT VARYING(L) for some ! !length> L, 4hen
              the type of the i-th 0arameter is PLg BIT 7ith length L or
              PLg BIT VARYING 7ith maximum length L, respectively.

            f) If 4he i-th <parameter declaration> specifies a <data type>
              that is DECIMAL(P, S) for some ! !precision> and ! !scale> P and
              S, then 4he 4ype of 4he i-th parameter shall be PL/I FIXED
              REAL DECIMAL (P,S).

            g) If 4he i-th <parameter declaration> specifies a <data type>
              that is FLOAT(P) for some <precision> P, 4hen the type of the
              i-th 0arameter shall be PLg FLOAT REAL BINARY (P).

            h) If 4he i-th <parameter declaration> specifies a <data type>
              that is INTEGER, 4hen the type of the i-th 0arameter shall be
              PLg FIXED BINARY(PI), 7here PI is an implementation-defined
              0recision.

                                                                Module   0Ø0¯0¿0ü0ë1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .4 Calls 4o a <procedure>


            i) ! ?f the i-th ! !parameter declaration> specifies a ! !data 4ype>
              4hat is SMALLINT, 4hen the type of the i-th 0arameter shall
              be PLg FIXED BINARY(SPI), where SPI is an implementation-
              defined precision.

         Access Rules

            None.

         ? ?eneral Rules

         1) If 4he subject ! !language clause> specifies ADA, then:

            a) Where Pi is used as an input 0arameter 7hose 6alue is eval-
              uated, a reference 4o PNi in a ! !general value specification>
              has 4he 6alue PIi.

            b) Where Pi is used as an output parameter, a reference 4o PNi
              that assigns a 6alue SVi 4o PNi implicitly assigns 4he 6alue
              SVi 4o PIi.

         2) If 4he subject ! !language clause> specifies C, then:

            Case:

            a) ! ?f Di specifies BIT(L), 4hen:

              i) 2 2 2 2here PNi is used as an input 0arameter 7hose 6alue is
                 evaluated, a reference to PNi is implicitly 4reated as:

                   SUBSTRING ( CAST ( PIi AS BIT VARYING(ML) ) FROM 1 FOR L
                   )

                 7here ML is 4he implementation-defined maximum length of a
                 BIT VARYING data type.

             ii) Let BLi be 4he length in bits of PIi. Let BL be the
                 implementation-defined number of bits in a C character.
                 Let OL be the smallest integer not less than 4he iuotient
                 of BLi/BL. Where PNi is 5sed as an output 0arameter, a ref-
                 erence 4o PNi that assigns a 6alue SVi 4o PNi implicitly
                 assigns the value

                   CAST ( SVi AS CHARACTER(OL) )

                 to PIi.

            b) If Di specifies CHARACTER(L) or CHARACTER VARYING(L), then:

              i) Where PNi is 5sed as an input parameter whose value is
                 evaluated, a reference 4o PNi is implicitly treated as an
                 SQL character 4ype value in 4he specified character set in
                 7hich 4he octets of PIi are 4he corresponding octets of
                 that 6alue.

         0Ø0¯0¿0ü0ë (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 1 (‘Ñ )4 Calls to a ! !procedure>


                 When such a reference is evaluated:

                 1) ! ?f Di specifies CHARACTER(L) and some C character 0re-
                   ceding the least significant C character of 4he 6alue
                   PIi contains 4he implementation-defined null character
                   that 4erminates a C character string, then 4he remaining
                   characters of the value are set to ! !space>s.

                 2) If Di specifies CHARACTER(L) VARYING, then 4he length
                   in characters of the value is set 4o the number of char-
                   acters of PIi 4hat precede the implementation-defined
                   null character 4hat terminates a C character string.

                 2 2) If 4he least significant C character of the value Pi
                   does not contain 4he implementation-defined null char-
                   acter that 4erminates a C character string, then an ex-
                   ception condition is raised: data exception-unterminated
                   C string. Otherwise, that least significant C charac-
                   ter does not correspond to any character in PIi and is
                   ignored.

             ii) Let CLi be one greater than 4he maximum 0ossible length in
                 octets of PNi. Where PNi is 5sed as an output 0arameter, a
                 reference 4o PNi that assigns a 6alue SVi 4o PNi implic-
                 itly assigns a value that is an SQL CHARACTER(CLi) data
                 type in which octets of the value are the corresponding
                 octets of SVi, padded on the right with ! !space>s as nec-
                 essary to reach 4he length CLi, concatenated with a single
                 implementation-defined null character 4hat terminates a C
                 character string.

            c) Otherwise,

              i) 2 2 2 2here PNi is used as an input 0arameter 7hose 6alue is
                 evaluated, a reference to PNi has 4he 6alue PIi.

             ii) Where PNi is 5sed as an output 0arameter, a reference to
                 PNi that assigns a 6alue SVi 4o PNi implicitly assigns 4he
                 value SVi to PIi.

         0Î0Ã0È ! ?f the subject <language clause> specifies COBOL, 4hen:

            Case:

            a) If Di specifies BIT(L), then:

              i) Where PNi is 5sed as an input parameter whose value is
                 evaluated, a reference 4o PNi is implicitly treated as:

                   SUBSTRING ( CAST ( PIi AS BIT VARYING(ML) ) FROM 1 FOR L
                   )

                 where ML is the implementation-defined maximum length of a
                 BIT VARYING data 4ype.

                                                                Module   2 263

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         1 (‘Ñ )4 Calls to a ! !procedure>


             ii) Let BLi be 4he length in bits of PIi. Let BL be the
                 implementation-defined number of bits in a COBOL character.
                 Let OL be the smallest integer not less than 4he iuotient
                 of BLi/BL. Where PNi is 5sed as an output 0arameter, a ref-
                 erence 4o PNi that assigns a 6alue SVi 4o PNi implicitly
                 assigns the value

                   CAST ( SVi AS CHARACTER(OL) )

                 to PIi.

            b) If Di specifies CHARACTER(L), then:

              i) Where PNi is 5sed as an input parameter whose value is
                 evaluated, a reference 4o PNi is implicitly treated as an
                 SQL character 4ype value in 4he specified character set in
                 7hich 4he octets of PIi are 4he corresponding octets of
                 that 6alue.

             ii) Let CLi be 4he maximum 0ossible length in octets of PNi.
                 Where PNi is 5sed as an output 0arameter, a reference to
                 PNi that assigns a 6alue SVi 4o PNi implicitly assigns
                 a value that is an SQL CHARACTER(CLi) data 4ype in 7hich
                 octets of the value are the corresponding octets of SVi,
                 padded on the right with ! !space>s as necessary 4o reach the
                 length CLi.

            c) Otherwise,

              i) Where PNi is 5sed as an input parameter whose value is
                 evaluated, a reference 4o PNi has the value PIi.

             ii) 2 2 2 2here PNi is used as an output parameter, a reference 4o
                 PNi 4hat assigns a value SVi to PNi implicitly assigns the
                 6alue SVi 4o PIi.

         2 2 2) If 4he subject ! !language clause> specifies FORTRAN, then:

            Case:

            a) ! ?f Di specifies BIT(L), 4hen:

              i) 2 2 2 2here PNi is used as an input 0arameter 7hose 6alue is
                 evaluated, a reference to PNi is implicitly 4reated as:

                   SUBSTRING ( CAST ( PIi AS BIT VARYING(ML) ) FROM 1 FOR L
                   )

                 7here ML is 4he implementation-defined maximum length of a
                 BIT VARYING data type.

             ii) Let BLi be 4he length in bits of PIi. Let BL be the
                 implementation-defined number of bits in a Fortran char-
                 acter. Let OL be the smallest integer not less than 4he

         2 264  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 .4 Calls 4o a <procedure>


                 iuotient of BLie‡L. 2 2 2 2here PNi is used as an output param-
                 eter, a reference to PNi 4hat assigns a value SVi to PNi
                 implicitly assigns 4he 6alue

                   CAST ( SVi AS CHARACTER(OL) )

                 4o PIi.

            b) ! ?f Di specifies CHARACTER(L), 4hen:

              i) 2 2 2 2here PNi is used as an input 0arameter 7hose 6alue is
                 evaluated, a reference to PNi is implicitly 4reated an
                 SQL character 4ype value in 4he specified character set in
                 7hich 4he octets of PIi are 4he corresponding octets of
                 that 6alue.

             ii) Let CLi be 4he maximum 0ossible length in octets of PNi.
                 Where PNi is 5sed as an output 0arameter, a reference to
                 PNi that assigns a 6alue SVi 4o PNi implicitly assigns
                 a value that is an SQL CHARACTER(CLi) data 4ype in 7hich
                 octets of the value are the corresponding octets of SVi,
                 padded on the right with ! !space>s as necessary 4o reach the
                 length CLi.

            c) Otherwise,

              i) Where PNi is 5sed as an input parameter whose value is
                 evaluated, a reference 4o PNi has the value PIi.

             ii) 2 2 2 2here PNi is used as an output parameter, a reference 4o
                 PNi 4hat assigns a value SVi to PNi implicitly assigns the
                 6alue SVi 4o PIi.

         5) If 4he subject ! !language clause> specifies MUMPS, then:

            Case:

            a) ! ?f Di specifies CHARACTER VARYING(L), 4hen:

              i) 2 2 2 2here PNi is used as an input 0arameter 7hose 6alue is
                 evaluated, a reference to PNi is implicitly 4reated as an
                 SQL character type 6alue in the specified character set in
                 which the octets of PIi are the corresponding octets of
                 4hat value.

             ii) 2 2 2 2here PNi is used as an output parameter, a reference 4o
                 PNi 4hat assigns a value SVi to PNi implicitly assigns a
                 6alue 4hat is an SQL CHARACTER VARYING(ML) data 4ype in
                 which octets of the value are the corresponding octets of
                 SVi, padded on the right with ! !space>s as necessary 4o
                 reach 4he length CLi. ML is 4he implementation-defined
                 maximum length of 6ariable-length character strings.


                                                                Module   2 265

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         1 (‘Ñ )4 Calls to a ! !procedure>


            b) Otherwise, Di specifies INT, DEC, or REAL, and:

              i) Where PNi is 5sed as an input parameter whose value is
                 evaluated, a reference 4o PNi is implicitly treated as

                   CAST ( PIi AS DTi )

             ii) 2 2 2 2here PNi is used as an output parameter, a reference 4o
                 PNi 4hat assigns a value SVi to PNi implicitly assigns the
                 6alue

                   CAST ( SVi AS CHARACTER VARYING(ML) )

                 4o PIi, 7here ML is 4he implementation-defined maximum
                 length of 6ariable-length character strings.

         6) ! ?f the subject <language clause> specifies PASCAL, then:

            Case:

            a) ! ?f Di specifies BIT(L), 4hen:

              i) 2 2 2 2here PNi is used as an input 0arameter 7hose 6alue is
                 evaluated, a reference to PNi is implicitly 4reated as:

                   SUBSTRING ( CAST ( PIi AS BIT VARYING(ML) ) FROM 1 FOR L
                   )

                 7here ML is 4he implementation-defined maximum length of a
                 BIT VARYING data type.

             ii) Let BLi be 4he length in bits of PIi. Let BL be the
                 implementation-defined number of bits in a Pascal char-
                 acter. Let OL be 4he smallest integer not less 4han the
                 iuotient of BLie‡L. 2 2 2 2here PNi is used as an output param-
                 eter, a reference to PNi 4hat assigns a value SVi to PNi
                 implicitly assigns 4he 6alue

                   CAST ( SVi AS CHARACTER (OL) )

                 to PIi.

            b) If Di specifies CHARACTER(L), then:

              i) Where PNi is 5sed as an input parameter whose value is
                 evaluated, a reference 4o PNi is implicitly treated an
                 SQL character type 6alue in the specified character set in
                 which the octets of PIi are the corresponding octets of the
                 6alue.

             ii) Let CLi be 4he maximum 0ossible length in octets of PNi.
                 Where PNi is 5sed as an output 0arameter, a reference to
                 PNi that assigns a 6alue SVi 4o PNi implicitly assigns a
                 value which is an SQL CHARACTER(CLi) data type in which
                 octets of 4he 6alue are 4he corresponding octets of SVi,
                 0added on 4he right 7ith <space>s as necessary to reach 4he
                 length CLi.

         0Ø0¯0¿0ü0ë6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 1 (‘Ñ )4 Calls to a ! !procedure>


            c) Otherwise,

              i) 2 2 2 2here PNi is used as an input 0arameter 7hose 6alue is
                 evaluated, a reference to PNi has 4he 6alue PIi.

             ii) Where PNi is 5sed as an output 0arameter, a reference to
                 PNi that assigns a 6alue SVi 4o PNi implicitly assigns 4he
                 value SVi to PIi.

         7) ! ?f the subject <language clause> specifies PLI, 4hen:

            Case:

            a) If Di specifies CHARACTER(L) or CHARACTER VARYING(L), then:

              i) Where PNi is 5sed as an input parameter whose value is
                 evaluated, a reference 4o PNi is implicitly treated an
                 SQL character type 6alue in the specified character set in
                 which the octets of PIi are the corresponding octets of the
                 6alue.

             ii) Let CLi be 4he maximum 0ossible length in octets of PNi.
                 Where PNi is 5sed as an output 0arameter, a reference to
                 PNi that assigns a 6alue SVi 4o PNi implicitly assigns a
                 value that is:

                 1) if Di specified CHARACTER(L), then an SQL CHARACTER(CLi)
                   data 4ype

                  (SA ) otherwise, an SQL CHARACTER VARYING(Ci ) data 4ype

                 in 7hich octets of 4he 6alue are 4he corresponding octets
                 of SVi, 0added on 4he right 7ith <space>s as necessary to
                 reach the length CLi.

            b) Otherwise,

              i) 2 2 2 2here PNi is used as an input 0arameter 7hose 6alue is
                 evaluated, a reference to PNi has 4he 6alue PIi.

             ii) Where PNi is 5sed as an output 0arameter, a reference to
                 PNi that assigns a 6alue SVi 4o PNi implicitly assigns 4he
                 value SVi to PIi.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL.

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.

                                                                Module   2 267

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         1 (‘Ñ )5 <sql 0rocedure statement>


         1 (‘Ñ )5  ! !SQL procedure statement>

         Function

         Define all of the SQL-statements 4hat are <sql 0rocedure state-
         ment>s.

         Format

         <sql 0rocedure statement> ::=
                <sql schema statement>
              = ! !SQL data statement>
              | <sql 4ransaction statement>
              | <sql connection statement>
              = ! !SQL session statement>
              = ! !SQL dynamic statement>
              = ! !SQL diagnostics statement>

         ! !SQL schema statement> ::=
                <sql schema definition statement>
              | <sql schema manipulation statement>

         <sql schema definition statement> ::=
                <schema definition>
              | <table definition>
              = ! !view definition>
              = ! !grant statement>
              = ! !domain definition>
              = ! !character set definition>
              | <collation definition>
              = ! !translation definition>
              | <assertion definition>

         ! !SQL schema manipulation statement> ::=
                ! !drop schema statement>
              = ! !alter table statement>
              = ! !drop 4able statement>
              | <drop view statement>
              | <revoke statement>
              = ! !alter domain statement>
              | <drop domain statement>
              | <drop character set statement>
              = ! !drop collation statement>
              | <drop translation statement>
              = ! !drop assertion statement>

         <sql data statement> ::=
                ! !open statement>
              | <fetch statement>
              | <close statement>
              | <select statement: single row>
              = ! !SQL data change statement>


         0Ø0¯0¿0ü0ë8  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                              .5 ! !SQL procedure statement>


         <sql data change statement> ::=
                <delete statement: 0ositioned>
              = ! !delete statement: searched>
              | <insert statement>
              = ! !update statement: positioned>
              | <update statement: searched>

         ! !SQL transaction statement> ::=
                ! !set transaction statement>
              = ! !set constraints mode statement>
              | <commit statement>
              = ! !rollback statement>

         <sql connection statement> ::=
                ! !connect statement>
              = ! !set connection statement>
              | <disconnect statement>

         ! !SQL session statement> ::=
                ! !set catalog statement>
              = ! !set schema statement>
              | <set names statement>
              | <set session authorization identifier statement>
              = ! !set local time +one statement>

         ! !SQL dynamic statement> ::=
                ! !system descriptor statement>
              = ! !prepare statement>
              = ! !deallocate 0repared statement>
              = ! !describe statement>
              | <execute statement>
              | <execute immediate statement>
              | <sql dynamic data statement>

         ! !SQL dynamic data statement> ::=
                <allocate cursor statement>
              | <dynamic open statement>
              = ! !dynamic fetch statement>
              = ! !dynamic close statement>
              = ! !dynamic delete statement: positioned>
              | <dynamic 5pdate statement: 0ositioned>

         ! !system descriptor statement> ::=
                ! !allocate descriptor statement>
              = ! !deallocate descriptor statement>
              = ! !set descriptor statement>
              | <get descriptor statement>

         ! !SQL diagnostics statement> ::=
              ! !get diagnostics statement>


                                                                Module   0Ø0¯0¿0ü0ë9

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .5 ! !SQL procedure statement>


         Syntax Rules

            None.

         Access Rules

            None.

         General Rules


            None.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) An ! !SQL procedure statement> shall not be an ! !SQL schema
              definition statement>.


         2 270  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         ª  Data manipulation


         ª.1  <declare cursor>

         Function

         Define a cursor.

         Format

         <declare cursor> ::=
              DECLARE ! !cursor name> [ ! ?NSENSITIVE ] [ SCROLL ] CURSOR
                FOR ! !cursor specification>

         <cursor specification> ::=
              ! !query expression> [ <order by clause> ]
                [ <updatability clause> ]

         <updatability clause> ::=
              FOR { READ ONLY | UPDATE [ OF <column name list> ] (

         ! !order by clause> ::=
              ORDER BY <sort specification list>

         <sort specification list> ::=
              <sort specification> [" ! !comma> ! !sort specification> }... ]

         ! !sort specification> ::=
              <sort key> [ ! !collate clause   ] [ ! !ordering specification> ]


         ! !sort key> ::=
                <column name>
              | <unsigned integer>

         ! !ordering specification> ::= ASC | DESC


         Syntax Rules

         1) The <cursor name> shall be different from the <cursor name>
            contained in any other ! !declare cursor> in 4he same <module>.

          (SA ) Any ! !parameter name> contained in 4he ! !cursor specification>
            shall be defined in a <parameter declaration> in 4he ! !procedure>
            in the containing ! !module> that contains an ! !open statement>
            that specifies 4he ! !cursor name>.

            Note: See 4he Syntax Rules of Subclause 1 (‘Ñ )1, "<module>".

                                                     Data manipulation   2 271

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10Ô0¢0¹0È0ë1 <declare cursor>


         0Î0Ã0È Let T be the table specified by 4he ! !query expression>.

         2 2 2) Let CS be the cursor specified by the <cursor specification>.

         5) ! ?f <updatability clause> is not specified, then:

            a) If either INSENSITIVE, SCROLL, or ORDER BY is specified, or
              if T is a read-anly table, 4hen an ! !updatability clause> of
              READ ONLY is implicit.

            b) Otherwise, an ! !updatability clause> of FOR UPDATE 7ithout a
              ! !column name list> is implicit.

         5 5) If an <updatability clause> of READ ONLY is specified or im-
            0licit, 4hen CS is a read-anly cursor; otherwise, CS is an
            updatable cursor.

         7) ! ?f an ! !order by clause> is specified, 4hen the cursor specified
            by the <cursor specification> is said 4o be an ordered cursor.

         8) The simply underlying 4able of a <cursor specification> is the
            table derived from by the <query expression> simply contained in
            4he ! !cursor specification>.

         9) If T is an 5pdatable 4able, then let TU be 4he leaf generally
            underlying 4able of the <cursor specification>.

         10)If ORDER BY is specified, 4hen each ! !sort specification> in 4he
            ! !order by clause> shall identify a column of T.

            Case:

            a) If a ! !sort specification> contains a ! !column name>, then T
              shall contain exactly one column with 4hat <column name> and
              the <sort specification> identifies that column.

            b) ! ?f a <sort specification> contains an ! !unsigned integer>,
              4hen the <unsigned integer> shall be greater than 0 and not
              greater 4han the degree of T. The ! !sort specification> iden-
              tifies 4he column of T 7ith the ordinal position specified by
              the <unsigned integer>.

          )If a <sort specification> contains a <collate clause>, then
            4he data type of the column identified by 4he ! !sort specifica-
            tion> shall be character string. The column descriptor of the
            corresponding column in the result has 4he collating sequence
            specified in ! !collate clause> and the coercibility attribute
            Explicit.

         1 (SA )If an <updatability clause> of FOR UPDATE with or without a
            <column name list> is specified or implicit, 4hen T shall be an
            updatable table and INSENSITIVE shall not be specified.

         ª)If an ! !updatability clause> of FOR UPDATE 7ithout a ! !column name
            list> is specified or implicit, then a ! !column name list> that
            includes the <column name> of every column of TU is implicit.

         2 272  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                       ª.1 ! !declare cursor>


         14)If an <updatability clause> of FOR UPDATE with a ! !column name
            list> is specified, then each <column name> in 4he ! !column name
            list> shall be 4he ! !column name> of a column of TU.

         Access Rules

            None.

         General Rules

         1) ! ?f T is an updatable table, 4hen the cursor is associated 7ith
            the named table TU. For every row in T, there is exactly one
            corresponding row in TU from which the row of T is derived.

         2) If an <order by clause> is not specified, then 4he 4able speci-
            fied by the <cursor specification> is T and the ordering of rows
            in T is implementation-dependent.

         2 2) If an <order by clause> is specified, then 4he ordering of rows
            of 4he result is effectively determined by 4he ! !order by clause>
            as follows:

            a) Each <sort specification> specifies 4he sort direction for
              the corresponding sort key Ki. ! ?f DESC is not specified in
              4he i-th <sort specification>, then 4he sort direction for Ki
              is ascending and the applicable ! !comp op> is the <less than
              operator>. Otherwise, 4he sort direction for Ki is descending
              and 4he applicable <comp op> is 4he ! !greater than operator>.

            b) Let P be any row of the result 4able and let Q be any other
              row of 4hat table, and let PVi and QVi be the values of Ki
              in these rows, respectively. The relative 0osition of rows
              P and Q in 4he result is determined by comparing PVi and
              QVi according 4o the rules of Subclause 8.2, "<comparison
              0redicate>", where the <comp op> is 4he applicable <comp op>
              for Ki, with 4he following special 4reatment of null 6alues.
              2 2 2 2hether a sort key value that is null is considered greater
              or less 4han a non-null 6alue is implementation-defined, but
              all sort key 6alues that are null shall either be considered
              greater 4han all non-null 6alues or be considered less than
              all non-null values. PVi is said to 0recede QVi if the value
              of 4he ! !comparison 0redicate> "PVi ! !comp op> QVi" is 4rue for
              the applicable ! !comp op>.

            c) In 4he result table, 4he relative position of row P is before
              row Q if and only if PVn 0recedes QVn for some n greater 4han
              0 and less 4han the number of <sort specification>s and PVi
              = QVi for all i < n. The relative order of 4wo rows that are
              not distinct is implementation-dependent.


                                                     Data manipulation   2 273

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10Ô0¢0¹0È0ë1 <declare cursor>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !declare cursor> shall not specify INSENSITIVE.

            b) ! ?f an ! !updatability clause> of FOR UPDATE 7ith or 7ithout
              a ! !column name list> is specified, then neither SCROLL nor
              ORDER BY shall be specified.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !declare cursor> shall not specify SCROLL.

            b) A <cursor specification> shall not contain an <updatability
              clause>.


         2 274  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                       ª.2 ! !open statement>


         10Ô0¢0¹0È0ë (N  ) ! !open statement>

         Function

         Open a cursor.

         Format

         ! !open statement> ::=
              OPEN ! !cursor name>


         Syntax Rules

         1) The containing ! !module> shall contain a <declare cursor> CR
            whose <cursor name> is 4he same as 4he ! !cursor name> in the
            <open statement>.

         Access Rules

         1) The Access Rules for 4he ! !query expression> simply contained
            in the <declare cursor> identified by 4he ! !cursor name> are
            applied.

         General Rules

         1) ! ?f cursor CR is not in the closed state, then an exception con-
            dition is raised: invalid cursor state.

         2) Let S be 4he ! !cursor specification> of cursor CR.

         0Î0Ã0È Cursor CR is opened in the following steps:

            a) A copy of S is effectively created in 7hich:

              i) Each ! !target specification> is replaced by 4he 6alue of the
                 4arget;

             ii) Each <value specification> generally contained in S 4hat
                 is CURRENT_USER, SESSION_USER, or SYSTEM_USER is replaced
                 by 4he 6alue resulting from evaluation of CURRENT_USER,
                 SESSION_USER, or SYSTEM_USER, respectively, 7ith all such
                 evaluations effectively done at the same instant in time;
                 and

            iii) Each <datetime value function> generally contained in S
                 is replaced by 4he 6alue resulting from evaluation of that
                 <datetime value function>, 7ith all such evaluations effec-
                 4ively done at the same instant in time.

            b) Let T be 4he 4able specified by the copy of S.

            c) A 4able descriptor for T is effectively created.

                                                     Data manipulation   0Ú0½5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ª.2 ! !open statement>


            d) The ? ?eneral Rules of Subclause ª.1, "<declare cursor>", are
              applied.

            e) Case:

              i) ! ?f S specifies INSENSITIVE, 4hen a copy of T is effectively
                 created and cursor CR is 0laced in 4he open state and its
                 0osition is before the first row of 4he copy of T.

             ii) Otherwise, cursor CR is placed in the open state and its
                 position is before 4he first row of T.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


         2 276  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      10Ô0¢0¹0È0ë0µ0ó0Á0ü0à<fetch statement>


         10Ô0¢0¹0È0ë0µ0ó0Á0ü0à ! !fetch statement>

         Function

         Position a cursor on a specified row of a table and retrieve 6alues
         from that row.

         Format

         ! !fetch statement> ::=
              FETCH [ [ ! !fetch orientation> ] FROM ]
                <cursor name> INTO ! !fetch target list>

         ! !fetch orientation> ::=
                NEXT
              | PRIOR
              | FIRST
              | LAST
              =" ABSOLUTE | RELATIVE ( ! !simple 6alue specification>

         <fetch 4arget list> ::=
              <target specification> [" ! !comma> ! !target specification> }... ]


         Syntax Rules

         1) ! ?f the <fetch orientation> is omitted, then NEXT is implicit.

         2) The containing ! !module> shall contain a <declare cursor> CR
            whose <cursor name> is 4he same as 4he ! !cursor name> in the
            <fetch statement>. Let T be the table defined by 4he ! !cursor
            specification> of CR.

         2 2) If 4he implicit or explicit <fetch orientation> is not NEXT,
            4hen the <declare cursor> CR shall specify SCROLL.

         4) ! ?f a <fetch orientation> that contains a <simple value specifi-
            cation> is specified, 4hen the data 4ype of 4hat <simple value
            specification> shall be exact numeric with a scale of 0.

         5) The number of <target specification>s in 4he ! !fetch target list>
            shall be the same as the degree of table T. The i-th <target
            specification> in the <fetch 4arget list> corresponds with 4he
            i-th column of table T.

         5 5) The Syntax Rules of Subclause 9.1, "Retrieval assignment"+"+ apply
            4o each corresponding ! !target specification> and column of table
            T, as TARGET and VALUE, respectively.

         Access Rules

            None.

                                                     Data manipulation   0Ú0½7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ª.3 ! !fetch statement>


         General Rules

         1) ! ?f cursor CR is not in the open state, then an exception condi-
            4ion is raised: invalid cursor state.

         2) Case:

            a) If 4he ! !fetch orientation> contains a <simple value spec-
              ification>, then let J be the value of 4hat <simple value
              specification>.

            b) If 4he ! !fetch orientation> specifies NEXT or FIRST, then let
              J be +1.

            c) If 4he ! !fetch orientation> specifies PRIOR or LAST, then let
              J be -1.

         0Î0Ã0È Let Tt be a 4able of the same degree as T.

            Case:

            a) ! ?f the <fetch orientation> specifies ABSOLUTE, FIRST, or
              LAST, then let Tt contain all rows of T, 0reserving their
              order in T.

            b) If 4he ! !fetch orientation> specifies NEXT or specifies
              RELATIVE with a 0ositive value of J, then:

              i) If 4he 4able T identified by cursor CR is empty or if the
                 0osition of CR is on or after 4he last row of T, then let
                 Tt be a table of no rows.

             ii) If 4he 0osition of CR is on a row R that is other than 4he
                 last row of T, 4hen let Tt contain all rows of T ordered
                 after row R, 0reserving their order in T.

            iii) If 4he 0osition of CR is before a row R, 4hen let Tt con-
                 4ain row R and all rows of T ordered after row R, 0reserv-
                 ing 4heir order in T.

            c) ! ?f the <fetch orientation> specifies PRIOR or specifies
              RELATIVE with a negative value of J, then:

              i) If 4he 4able T identified by cursor CR is empty or if the
                 0osition of CR is on or before the first row of T, then let
                 Tt be a table of no rows.

             ii) If 4he 0osition of CR is on a row R that is other than 4he
                 first row of T, then let Tt contain all rows of T ordered
                 before row R, 0reserving their order in T.

            iii) If 4he 0osition of CR is before the next row of a row R
                 4hat is not 4he last row of T, then let Tt contain row R
                 and all rows of T ordered before row R, 0reserving their
                 order in T.

         2 278  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      10Ô0¢0¹0È0ë0µ0ó0Á0ü0à<fetch statement>


             iv) ! ?f the position of CR is after the last row of T, 4hen let
                 Tt contain all rows of T, 0reserving their order in T.

            d) If RELATIVE is specified 7ith a zero 6alue of J, 4hen:

              i) ! ?f the position of CR is on a row of T, 4hen let Tt be a
                 4able comprising that one row.

             ii) Otherwise, let Tt be an empty table.

         2 2 2) Let N be 4he number of rows in Tt. ! ?f J is 0ositive, 4hen let
            K be J. If J is negative, then let K be N+J+1. ! ?f J is +ero
            and ABSOLUTE is specified, 4hen let K be +ero; if J is +ero and
            RELATIVE is specified, 4hen let K be 1.

         5) Case:

            a) ! ?f K is greater 4han 0 and not greater than N, then CR is
              0ositioned on 4he K-th row of Tt and the corresponding row of
              T. That row becomes 4he current row of CR.

            b) Otherwise, no SQL-data 6alues are assigned 4o any targets
              in 4he ! !fetch target list>, and a completion condition is
              raised: no data.

              Case:

              i) If 4he ! !fetch orientation> specifies RELATIVE with J equal
                 to +ero, 4hen the position of CR is unchanged.

             ii) ! ?f the <fetch orientation> implicitly or explicitly spec-
                 ifies NEXT, specifies ABSOLUTE or RELATIVE 7ith K greater
                 4han N, or specifies LAST, then CR is 0ositioned after the
                 last row.

            iii) Otherwise, the <fetch orientation> specifies PRIOR, FIRST,
                 or ABSOLUTE or RELATIVE 7ith K not greater than N and CR is
                 positioned before the first row.

         5 5) If a completion condition no data has been raised, 4hen no fur-
            ther ? ?eneral Rules of this Subclause are applied.

         7) ! ?f an exception condition is raised during derivation of any
            <derived column> associated with 4he current row of CR, then CR
            remains positioned on the current row.

         8) Values from the current row are assigned 4o their corresponding
            targets identified by the <fetch 4arget list>. The assignments
            are made in an implementation-dependent order. Let TV be a tar-
            get and let SV denote its corresponding 6alue in the current
            row of CR. The ? ?eneral Rules of Subclause 9.1, "Retrieval as-
            signment"+"+ are applied 4o TV and SV as TARGET and VALUE, respec-
            4ively.

                                                     Data manipulation   2 279

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10Ô0¢0¹0È0ë0µ0ó0Á0ü0à<fetch statement>


         9) If an exception condition occurs during the assignment of SV
            4o TV, then 4he 6alue of TV is implementation-dependent and CR
            remains positioned on the current row.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !fetch statement> shall not contain a ! !fetch orientation>.

            b) A <fetch statement> shall not specify FROM.

            c) If 4he data type of the target identified by 4he i-th <target
              specification> in the <fetch 4arget list> is an exact numeric
              type, then 4he data type of the i-th column of 4he 4able T
              shall be an exact numeric 4ype.


         2 280  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      10Ô0¢0¹0È0ë4 <close statement>


         10Ô0¢0¹0È0ë4  ! !close statement>

         Function

         Close a cursor.

         Format

         ! !close statement> ::=
              CLOSE ! !cursor name>


         Syntax Rules

         1) The containing ! !module> shall contain a <declare cursor> CR
            whose <cursor name> is 4he same as 4he ! !cursor name> of the
            <close statement>.

         Access Rules

            None.

         ? ?eneral Rules

         1) If cursor CR is not in 4he open state, 4hen an exception condi-
            tion is raised: invalid cursor state.

          (SA ) Cursor CR is placed in the closed state and 4he copy of 4he
            ! !cursor specification> of CR is destroyed.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                                     Data manipulation   0Ú0Ë0Ò1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ª.5 ! !select statement: single row>


         10Ô0¢0¹0È0ë5  ! !select statement: single row>

         Function

         Retrieve values from a specified row of a 4able.

         Format

         ! !select statement: single row> ::=
              SELECT [ ! !set quantifier> ] <select list>
                INTO ! !select 4arget list>
                  <table expression>

         ! !select 4arget list> ::=
              <target specification> [" ! !comma> ! !target specification> }... ]


         Syntax Rules

         1) The number of elements in 4he ! !select list> shall be the same
            as the number of elements in the <select target list>. The i-th
            ! !target specification> in 4he ! !select 4arget list> corresponds
            with 4he i-th element of 4he ! !select list>.

          (SA ) The Syntax Rules of Subclause 9.1, "Retrieval assignment", ap-
            ply to each corresponding <target specification> and ! !value
            expression>, as TARGET and VALUE, respectively.

         0Î0Ã0È Let S be a <query specification> whose <select list> and <table
            expression> are 4hose specified in the <select statement: single
            row> and 4hat specifies the <set iuantifier> if it is specified
            in 4he ! !select statement: single row>. S shall be a valid <query
            specification>.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let Q be 4he result of ! !query specification> S.

          (SA ) Case:

            a) ! ?f the cardinality of Q is greater than 1, then an ex-
              ception condition is raised: cardinality 6iolation. It is
              implementation-dependent 7hether or not SQL-data 6alues are
              assigned 4o the targets identified by the <select target
              list>.

            b) If Q is empty, 4hen no SQL-data values are assigned to any
              4argets identified by 4he ! !select 4arget list>, and a comple-
              4ion condition is raised: no data.

         0Ú0Ë0Ò (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         10Ô0¢0¹0È0ë5 <select statement: single row>


            c) Otherwise, 6alues in 4he row of Q are assigned 4o their cor-
              responding targets.

         2 2) If a completion condition no data has been raised, 4hen no fur-
            ther ? ?eneral Rules of this Subclause are applied.

         4) The assignment of 6alues to 4argets in the <select target list>
            is in an implementation-dependent order.

         5) ! ?f an exception condition is raised during the assignment of a
            value to a 4arget, 4hen the values of targets are implementation-
            dependent.

         5 5) The target identified by 4he i-th <target specification> of the
            <select target list> corresponds 4o the i-th 6alue in the row of
            Q.

         7) Let TV be an identified 4arget and let SV be its corresponding
            value in 4he row of Q.

         8) The General Rules of Subclause 9.1, "Retrieval assignment", are
            applied to TV and SV, as TARGET and VALUE, respectively.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) ! ?f the data 4ype of 4he 4arget identified by the i-th ! !tar-
              get specification> in 4he ! !select 4arget list> is an exact
              numeric type, then 4he data type of the i-th column of 4he
              4able T shall be an exact numeric 4ype.

            b) The ! !table expression> shall not include a <group by clause>
              or a ! !having clause> and shall not identify a grouped view.


                                                     Data manipulation   0Ú0Ë0Ò0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ª.6 ! !delete statement: positioned>


         10Ô0¢0¹0È0ë6  ! !delete statement: positioned>

         Function

         Delete a row of a 4able.

         Format

         ! !delete statement: positioned> ::=
              DELETE FROM <table name>
                2 2 2 2HERE CURRENT OF <cursor name>


         Syntax Rules

         1) The containing <module> shall contain a ! !declare cursor> whose
            <cursor name> is 4he same as 4he ! !cursor name> in the <delete
            statement: 0ositioned>. Let CR be the cursor specified by <cur-
            sor name>.

         2) CR shall be an 5pdatable cursor.

            Note: updatable cursor is defined in Subclause 10Ô0¢0¹0È0ë1, "<declare
            cursor>".

         2 2) Let T be 4he 4able identified by 4he ! !table name>. Let QS be 4he
            ! !query specification> 4hat is 4he simply underlying 4able of the
            simply 5nderlying table of CR. The simply underlying 4able of QS
            shall be T.

            Note: The simply 5nderlying table of a ! !cursor specification> is
            defined in Subclause ª.1, "<declare cursor>".

         Access Rules

         1) The applicable 0rivileges shall include DELETE for 4he ! !table
            name>.

            Note: The applicable 0rivileges for a <table name> are defined
            in Subclause 10.3, "<privileges>".

         General Rules

         1) ! ?f the access mode of 4he current SQL-transaction is read-anly
            and T is not a 4emporary 4able, then an exception condition is
            raised: invalid 4ransaction state.

          (SA ) ! ?f cursor CR is not 0ositioned on a row, then an exception con-
            dition is raised: invalid cursor state.

         2 2) The row from 7hich 4he current row of CR is derived is marked
            for deletion.

         4) ! ?f, 7hile CR is open, 4he row from which the current row of CR
            is derived has been marked for deletion by any ! !delete state-
            ment: searched>, marked for deletion by any <delete statement:
            0ositioned> 4hat identifies any cursor other than CR, 5pdated

         2 284  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                         ª.6 ! !delete statement: positioned>


            by any ! !update statement: searched>, or updated by any ! !update
            statement: positioned> that identifies any cursor other 4han CR,
            then a completion condition is raised: 7arning-cursor operation
            conflict.

         5) All rows that are marked for deletion are effectively deleted
            at the end of 4he ! !delete statement: positioned> prior to 4he
            checking of any integrity constraint.

         5 5) If 4he ! !delete statement: positioned> deleted the last row of
            CR, then 4he 0osition of CR is after 4he last row; otherwise,
            the position of CR is before 4he next row.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                                     Data manipulation   0Ú0Ë0Ò5

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ª.7 ! !delete statement: searched>


         10Ô0¢0¹0È0ë7  ! !delete statement: searched>

         Function

         Delete rows of a table.

         Format

         <delete statement: searched> ::=
              DELETE FROM ! !table name>
                [ WHERE <search condition> ]


         Syntax Rules

         1) Let T be 4he 4able identified by 4he ! !table name>. T shall not
            be a read-anly table.

         2) The scope of 4he ! !table name> is 4he entire <delete statement:
            searched>.

         Access Rules

         1) The applicable 0rivileges shall include DELETE for 4he ! !table
            name>.

            Note: The applicable 0rivileges for a <table name> are defined
            in Subclause 10.3, "<privileges>".

         General Rules

         1) ! ?f the access mode of 4he current SQL-transaction is read-anly
            and T is not a 4emporary 4able, then an exception condition is
            raised: invalid 4ransaction state.

          (SA ) Case:

            a) ! ?f <search condition> is not specified, 4hen all rows of T
              are marked for deletion.

            b) ! ?f <search condition> is specified, 4hen it is applied to
              each row of T 7ith the <table name> bound 4o that row, and
              all rows for 7hich 4he result of 4he ! !search condition> is
              4rue are marked for deletion.

              The <search condition> is effectively evaluated for each row
              of T before marking for deletion any row of T.

              Each <subquery> in the <search condition> is effectively
              executed for each row of T and 4he results 5sed in 4he ap-
              0lication of the <search condition> 4o the given row of T.
              If any executed <subquery> contains an outer reference 4o a
              column of T, 4he reference is to 4he 6alue of that column in
              4he given row of T.

              Note: Outer reference is defined in Subclause 6.4, "<column
              reference>".

         2 286  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                           ª.7 ! !delete statement: searched>


         2 2) If any row 4hat is marked for deletion by the <delete statement:
            searched> has been marked for deletion by any ! !delete statement:
            positioned> that identifies some cursor CR 4hat is still open
            or 5pdated by any <update statement: 0ositioned> 4hat identifies
            some cursor CR that is still open, then a completion condition
            is raised: 7arning-cursor operation conflict.

         4) All rows that are marked for deletion are effectively deleted
            at the end of 4he ! !delete statement: searched> prior to 4he
            checking of any integrity constraint.

         5) If no row is deleted, then a completion condition is raised: no
            data.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) No leaf generally 5nderlying table of T shall be an 5nder-
              lying table of any ! !query expression> generally contained in
              4he ! !search condition>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                                     Data manipulation   2 287

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10Ô0¢0¹0È0ë8 <insert statement>


         ª.8  <insert statement>

         Function

         Create new rows in a 4able.

         Format

         ! !insert statement> ::=
              INSERT ! ?NTO <table name>
                ! !insert columns and source>

         ! !insert columns and source> ::=
                [ ! !left 0aren> <insert column list> ! !right paren> ]
              ! !query expression>
              | DEFAULT VALUES

         ! !insert column list> ::= <column name list>


         Syntax Rules

         1) The table T identified by the <table name> shall not be a read-
            only 4able.

          (SA ) An <insert columns and source> that specifies DEFAULT VALUES is
            equivalent to an <insert columns and source> that specifies a
            ! !query expression> of 4he form

              VALUES (DEFAULT, . . . )

            7here 4he number of "DEFAULT" entries is equal to 4he number of
            columns of T.

         2 2) No ! !column name> of T shall be identified more 4han once. If 4he
            ! !insert column list> is omitted, then an <insert column list>
            4hat identifies all columns of T in 4he ascending sequence of
            4heir ordinal 0ositions 7ithin T is implicit.

         2 2 2) A column identified by 4he ! !insert column list> is an object
            column.

         5) Let QT be the table specified by 4he ! !query expression>. The
            degree of QT shall be equal 4o the number of <column name>s in
            the <insert column list>. The column of table T identified by
            the i-th ! !column name> in the <insert column list> corresponds
            7ith the i-th column of QT.

         5 5) The Syntax Rules of Subclause 9. (l4 ) "Store assignment"+"+ apply 4o
            corresponding columns of T and QT as TARGET and VALUE, respec-
            4ively.


         2 288  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                     ª.8 ! !insert statement>


         Access Rules

         1) Case:

            a) ! ?f an ! !insert column list> is specified, then 4he applicable
              <privileges> shall include ! ?NSERT for each ! !column name> in
              the <insert column list>.

            b) Otherwise, 4he applicable privileges shall include ! ?NSERT for
              each ! !column name> in T.

            Note: The applicable 0rivileges for a <table name> are defined
            in Subclause 10.3, "<privileges>".

          (SA ) Each <column name> in 4he ! !insert column list> shall identify a
            column of T.

         General Rules

         1) ! ?f the access mode of 4he current SQL-transaction is read-anly
            and T is not a 4emporary 4able, then an exception condition is
            raised: invalid 4ransaction state.

          (SA ) Let B be the leaf generally 5nderlying table of T.

         0Î0Ã0È The ! !query expression> is effectively evaluated before inserting
            any rows into B.

         2 2 2) Let Q be 4he result of 4hat <query expression>.

            Case:

            a) ! ?f Q is empty, then no row is inserted and a completion con-
              dition is raised: no data.

            b) Otherwise, for each row R of Q:

              i) A candidate row of B is effectively created in which the
                 6alue of each column is its default 6alue, as specified in
                 4he ? ?eneral Rules of Subclause  .5, "<default clause>".
                 The candidate row includes every column of B.

             ii) For every object column in the candidate row, 4he 6alue of
                 4he object column identified by 4he i-th <column name> in
                 the <insert column list> is replaced by the i-th 6alue of
                 R.

            iii) Let C be a column that is represented in 4he candidate row
                 and let SV be its value in 4he candidate row. The General
                 Rules of Subclause 9. (l4 ) "Store assignment"+"+ are applied 4o
                 C and SV as TARGET and VALUE, respectively.

             iv) The candidate row is inserted into B.

                 Note: The data values allowable in the candidate row may be
                 constrained by a 2 2 2 2ITH CHECK OPTION constraint. The effect
                 of a WITH CHECK OPTION constraint is defined in 4he ? ?eneral
                 Rules of Subclause 11., "<view definition>".

                                                     Data manipulation   2 289

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10Ô0¢0¹0È0ë8 <insert statement>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) The leaf generally underlying 4able of T shall not be gen-
              erally contained in the <query expression> immediately
              contained in the <insert columns and source> except as the
              <qualifier> of a ! !column reference>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) The ! !query expression> that is contained in an <insert state-
              ment> shall be a <query specification> or it shall be a ! !ta-
              ble value constructor> 4hat contains exactly one ! !row value
              constructor> of the form "<left paren> ! !row value constructor
              list> <right 0aren>", and each ! !row value constructor ele-
              ment> of that ! !row value constructor list> shall be a ! !value
              specification>.

            b) If 4he data type of the target identified by 4he i-th <column
              name> is an exact numeric type, then 4he data type of the i-
              4h item of the <insert statement> shall be an exact numeric
              4ype.

            c) ! ?f the data 4ype of 4he 4arget C identified by the i-th ! !col-
              5mn name> is character string, then 4he length in characters
              of 4he i-th item of the <insert statement> shall be less 4han
              or equal 4o the length of C.

            d) The ! !insert columns and source> shall immediately contain a
              ! !query expression>.


         0Ø0ë0Ä0  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         10Ô0¢0¹0È0ë9 <update statement: 0ositioned>


         ª.9  <update statement: 0ositioned>

         Function

         Update a row of a table.

         Format

         <update statement: 0ositioned> ::=
              UPDATE <table name>
                SET ! !set clause list>
                  2 2 2 2HERE CURRENT OF <cursor name>

         <set clause list> ::=
              <set clause> [" ! !comma> ! !set clause> }... ]

         ! !set clause> ::=
              <object column> <equals operator> <update source>

         <update source> ::=
                <value expression>
              = ! !null specification>
              | DEFAULT

         <object column> ::= <column name>


         Syntax Rules

         1) The containing <module> shall contain a ! !declare cursor> for
            a cursor 7hose ! !cursor name> is the same as the <cursor name>
            in 4he ! !update statement: positioned>. Let CR be 4he cursor
            specified by ! !cursor name>.

          (SA ) CR shall be an updatable cursor.

            Note: 5pdatable cursor is defined in Subclause ª.1, "<declare
            cursor>".

         0Î0Ã0È Let T be the table identified by the <table name>. Let QS be the
            <query specification> that is the simply 5nderlying table of 4he
            simply underlying 4able of CR. The simply 5nderlying table of QS
            shall be T.

            Note: The simply underlying 4able of a <cursor specification> is
            defined in Subclause 10Ô0¢0¹0È0ë1, "<declare cursor>".

         2 2 2) If CR is an ordered cursor, then for each <object column> OC,
            the column of T identified by OC shall not be directly or in-
            directly referenced in 4he ! !order by clause> of the defining
            ! !cursor specification> for CR.


                                                     Data manipulation   0Ø0ë0Ä1

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ª.9 ! !update statement: positioned>


         5) No leaf generally underlying 4able of T shall be an underly-
            ing 4able of any <query expression> generally contained in any
            <value expression> immediately contained in any <update source>
            contained in 4he ! !set clause list>.

         6) A ! !value expression> in a ! !set clause> shall not directly con-
            tain a ! !set function specification>.

         5 5 5) The same ! !object column> shall not appear more 4han once in a
            <set clause list>.

         8) If 4he cursor identified by <cursor name> was specified using
            an explicit or implicit <updatability clause> of FOR UPDATE,
            4hen each ! !column name> specified as an ! !object column> shall
            identify a column in the explicit or implicit ! !column name list>
            associated 7ith the <updatability clause>.

         9) The scope of 4he ! !table name> is 4he entire <update statement:
            0ositioned>.

         10)For every ! !set clause>, 4he Syntax Rules of Subclause 9.2,
            "Store assignment", apply to 4he column of T identified by 4he
            ! !object column> and 4he ! !value expression> of 4he ! !set clause>
            as TARGET and VALUE, respectively.

         Access Rules

         1) The applicable privileges shall include UPDATE for each ! !object
            column>.

            Note: The applicable privileges for a ! !table name> are defined
            in Subclause 10.0Ñ0ü0Ä "<privileges>".

         2) Each ! !column name> specified as an ! !object column> shall iden-
            4ify a column of T.

         ? ?eneral Rules

         1) If 4he access mode of the current SQL-transaction is read-only
            and T is not a temporary table, 4hen an exception condition is
            raised: invalid transaction state.

         2) If cursor CR is not positioned on a row, 4hen an exception con-
            dition is raised: invalid cursor state.

         0Î0Ã0È The object row is 4hat row from 7hich 4he current row of CR is
            derived.

         2 2 2) If, while CR is open, the object row has been marked for dele-
            4ion by any ! !delete statement: searched>, marked for deletion
            by any <delete statement: 0ositioned> 4hat identifies any cursor
            other than CR, 5pdated by any <update statement: searched>, or
            5pdated by any <update statement: 0ositioned> 4hat identifies
            any cursor other than CR, 4hen a completion condition is raised:
            warning-cursor operation conflict.

         2 292  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                         ª.9 ! !update statement: positioned>


         5) The value of DEFAULT is the default value indicated in 4he col-
            umn descriptor for 4he ! !object column> in the containing ! !set
            clause>.

         5 5) The <value expression>s are effectively evaluated before 5pdat-
            ing the object row. If a ! !value expression> contains a reference
            4o a column of T, 4hen the reference is 4o the value of 4hat
            column in the object row before any value of 4he object row is
            5pdated.

         7) CR remains positioned on its current row, even if an exception
            condition is raised during derivation of any ! !value expression>
            associated 7ith the object row.

         8) A ! !set clause> specifies an object column and an update 6alue
            of that column. The object column is the column identified by
            4he ! !object column> in the <set clause>. The update 6alue is the
            value specified by 4he ! !update source>.

            Note: The data values allowable in the object row may be con-
            strained by a 2 2 2 2ITH CHECK OPTION constraint. The effect of a
            2 2 2 2ITH CHECK OPTION constraint is defined in the General Rules of
            Subclause 11., "<view definition>".

         9) The object row is updated as specified by each ! !set clause>.
            For each <set clause>, the value of 4he specified object column,
            denoted by C, is replaced by 4he specified 5pdate value, denoted
            by SV. The General Rules of Subclause 9.2, "Store assignment",
            are applied to C and SV as TARGET and VALUE, respectively.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) CR shall not be an ordered cursor.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) ! ?f the data 4ype of 4he column identified by the i-th ! !object
              column> is an exact numeric 4ype, 4hen the data 4ype of 4he
              i-th <value expression> in the <update statement: 0ositioned>
              shall be an exact numeric 4ype.

            b) ! ?f the data 4ype of 4he column identified by the i-th ! !object
              column> C is character string, then 4he length in characters
              of 4he i-th <value expression> in the <update statement:
              0ositioned> shall be less 4han or equal 4o the length of C.

            c) An <update source> shall not specify DEFAULT.


                                                     Data manipulation   0Ø0ë0Ä0ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ª.10 <update statement: searched>


         ª.10  ! !update statement: searched>

         Function

         Update rows of a table.

         Format

         <update statement: searched> ::=
              UPDATE <table name>
                SET ! !set clause list>
                [ 2 2 2 2HERE ! !search condition> ]


         Syntax Rules

         1) Let T be the table identified by the <table name>. T shall be an
            updatable table.

         2) A <value expression> in a <set clause> shall not directly con-
            4ain a <set function specification>.

         0Î0Ã0È The same <object column> shall not appear more than once in a
            ! !set clause list>.

         4) The scope of the <table name> is the entire ! !update statement:
            searched>.

         5) For every <set clause>, the Syntax Rules of Subclause 9. (l4 )
            "Store assignment"+"+ apply 4o the column of T identified by the
            <object column> and the <value expression> of the <set clause>
            as TARGET and VALUE, respectively.

         Access Rules

         1) The applicable 0rivileges shall include UPDATE for each <object
            column>.

            Note: The applicable 0rivileges for a <table name> are defined
            in Subclause 10.3, "<privileges>".

          (SA ) Each <column name> specified as an <object column> shall iden-
            tify a column of T.

         General Rules

         1) ! ?f the access mode of 4he current SQL-transaction is read-anly
            and T is not a 4emporary 4able, then an exception condition is
            raised: invalid 4ransaction state.

          (SA ) Case:

            a) ! ?f a <search condition> is not specified, 4hen all rows of T
              are the object rows.

         2 294  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                          10Ô0¢0¹0È0ë10 ! !update statement: searched>


            b) ! ?f a <search condition> is specified, 4hen it is applied
              to each row of T 7ith the <table name> bound 4o that row,
              and the object rows are those rows for 7hich 4he result of
              4he ! !search condition> is 4rue. The ! !search condition> is
              effectively evaluated for each row of T before updating any
              row of T.

              Each ! !subquery> in 4he ! !search condition> is effectively
              executed for each row of T and the results used in the ap-
              plication of 4he ! !search condition> to 4he given row of T.
              ! ?f any executed ! !subquery> contains an outer reference to a
              column of T, the reference is 4o the value of 4hat column in
              the given row of T.

              Note: Outer reference is defined in Subclause 5 5.4, "<column
              reference>".

         0Î0Ã0È ! ?f any row in 4he set of object rows has been marked for dele-
            tion by any <delete statement: 0ositioned> 4hat identifies some
            cursor CR that is still open or updated by any ! !update state-
            ment: positioned> that identifies some cursor CR 4hat is still
            open, 4hen a completion condition is raised: warning-cursor
            operation conflict.

         2 2 2) If 4he set of object rows is empty, then a completion condition
            is raised: no data.

         5) ! ?f a completion condition no data has been raised, then no fur-
            4her General Rules of 4his Subclause are applied.

         5 5) The <value expression>s are effectively evaluated for each row
            of T before 5pdating any row of T.

         7) A ! !set clause> specifies an object column and an update 6alue
            of that column. The object column is the column identified by
            4he ! !object column> in the <set clause>. The update 6alue is the
            value specified by 4he ! !update source>.

            Note: The data values allowable in the object row may be con-
            strained by a 2 2 2 2ITH CHECK OPTION constraint. The effect of a
            2 2 2 2ITH CHECK OPTION constraint is defined in the General Rules of
            Subclause 11., "<view definition>".

         8) Each object row is 5pdated as specified by each <set clause>.
            For each ! !set clause>, 4he 6alue of the specified object column,
            denoted by C, is replaced by the specified update 6alue, denoted
            by SV. The ? ?eneral Rules of Subclause 9. (l4 ) "Store assignment"+"+
            are applied 4o C and SV as TARGET and VALUE, respectively.


                                                     Data manipulation   2 295

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         10Ô0¢0¹0È0ë10 ! !update statement: searched>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) No leaf generally underlying 4able of T shall be an under-
              lying 4able of any <query expression> generally contained in
              the <search condition> or in any ! !value expression> immedi-
              ately contained in any ! !update source> contained in the <set
              clause list>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) ! ?f the data 4ype of 4he column identified by the i-th ! !object
              column> is an exact numeric 4ype, 4hen the data 4ype of 4he
              i-th <value expression> in the <update statement: searched>
              shall be an exact numeric 4ype.

            b) ! ?f the data 4ype of 4he column identified by the i-th ! !object
              column> C is character string, then 4he length in characters
              of 4he i-th <value expression> in the <update statement:
              searched> shall be less 4han or equal 4o the length of C.


         0Ø0ë0Ä6  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         10Ô0¢0¹0È0ë  ! !temporary table declaration>


         ª.11  ! !temporary table declaration>

         Function

         Declare a declared local 4emporary 4able 4hat will be effectively
         materialized the first time 4hat any <procedure> in 4he ! !module>
         4hat contains 4he ! !temporary table declaration> is executed and
         whose scope is all 4he ! !procedure>s of 4hat <module> executed
         7ithin the same SQL-session.

         Format

         ! !temporary table declaration> ::=
              DECLARE LOCAL TEMPORARY TABLE ! !qualified local table name>
                <table element list>
                [ ON COMMIT" PRESERVE | DELETE ( ROWS ]


         Syntax Rules

         1) Let T be the <local 4able name> of <qualified local 4able name>.
            T shall be different from the <local 4able name> of any other
            <temporary 4able declaration> contained within 4he ! !module>.

         2) Let A be 4he current ! !authorization identifier>.

         2 2) The descriptor of the table defined by a ! !temporary table decla-
            ration> includes the name of T and the column descriptor speci-
            fied by each <column definition>. The i-th column descriptor is
            given by the i-th ! !column definition>.

         4) A ! !temporary table declaration> shall contain at least one <col-
            umn definition>.

         5) If ON COMMIT is not specified, 4hen ON COMMIT DELETE ROWS is
            implicit.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let U be 4he implementation-dependent <schema name> that is
            effectively derived from 4he implementation-dependent SQL-
            session identifier associated 7ith the SQL-session and an
            implementation-dependent name associated with 4he ! !module> that
            contains the <temporary 4able declaration>.

         2) The definition of T within a ! !module> is effectively equivalent
            to 4he definition of a 0ersistent base 4able U.T. Within 4he
            module, any reference 4o MODULE.T is equivalent 4o a reference
            to U.T.

                                                     Data manipulation   0Ø0ë0Ä7

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ª.11 <temporary 4able declaration>


         2 2) A set of 0rivilege descriptors is created that define the priv-
            ileges ! ?NSERT, SELECT, UPDATE, DELETE, and REFERENCES on 4his
            table and INSERT (<column name>), UPDATE (<column name>), and
            REFERENCES (<column name>) for every ! !column definition> in the
            table definition 4o A. These 0rivileges are not grantable. The
            grantor for each of 4hese 0rivilege descriptors is set to 4he
            special grantor 6alue "_SYSTEM".

         4) The definition of a 4emporary 4able 0ersists for the duration
            of the SQL-session. The 4ermination of the SQL-session is effec-
            tively followed by 4he execution of the following <drop table
            statement> 7ith the current <authorization identifier> and
            current ! !schema name> U 7ithout further Access Rule checking:

              DROP TABLE T

         5) The definition of a declared local 4emporary 4able does not
            appear in any view of the Information Schema.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <temporary 4able declaration>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


         2 298  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


           Transaction management


         14.1  ! !set transaction statement>

         Function

         Set the attributes of the next SQL-transaction for 4he SQL-agent.

         Format

         ! !set transaction statement> ::=
              SET TRANSACTION ! !transaction mode> [ { <comma> <transaction mode> (... ]


         ! !transaction mode> ::=
                <isolation level>
              | <transaction access mode>
              | <diagnostics size>

         ! !transaction access mode> ::=
                READ ONLY
              = READ WRITE

         <isolation level> ::=
              ISOLATION LEVEL <level of isolation>

         ! !level of isolation> ::=
                READ UNCOMMITTED
              = READ COMMITTED
              | REPEATABLE READ
              | SERIALIZABLE

         ! !diagnostics size> ::=
              DIAGNOSTICS SIZE ! !number of conditions>

         <number of conditions> ::= ! !simple 6alue specification>


         Syntax Rules

         1) No <transaction mode> shall be specified more 4han once.

          (SA ) ! ?f an ! !isolation level> is not specified, 4hen a <level of iso-
            lation> of ISOLATION LEVEL SERIALIZABLE is implicit.

         0Î0Ã0È ! ?f READ 2 2 2 2RITE is specified, 4hen the <level of isolation> shall
            not be READ UNCOMMITTED.


                                                Transaction management   2 299

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         14.1 <set 4ransaction statement>


         2 2 2) If a ! !transaction access mode> is not specified and a <level of
            isolation> of READ UNCOMMITTED is specified, 4hen READ ONLY is
            implicit. Otherwise, READ 2 2 2 2RITE is implicit.

         5) The data type of <number of conditions> shall be exact numeric
            with scale 0.

         Access Rules

            None.

         General Rules

         1) ! ?f a <set 4ransaction statement> statement is executed when an
            SQL-transaction is currently active, 4hen an exception condition
            is raised: invalid transaction state.

         2) If ! !number of conditions> is specified and is less 4han 1, 4hen
            an exception condition is raised: invalid condition number.

         0Î0Ã0È Let TXN be the next SQL-transaction for 4he SQL-agent.

         4) ! ?f READ ONLY is specified, then 4he access mode of TXN is set 4o
            read-anly. ! ?f READ 2 2 2 2RITE is specified, 4hen the access mode of
            TXN is set to read-write.

         5) The isolation level of TXN is set to an implementation-defined
            isolation level 4hat will not exhibit any of the phenomena that
            4he explicit or implicit <level of isolation> 7ould not exhibit,
            as specified in Table 9, "SQL-transaction isolation levels and
            4he 4hree 0henomena".

         5 5) If ! !number of conditions> is specified, then 4he diagnostics
            area limit of TXN is set to ! !number of conditions>.

         5 5 5) If ! !number of conditions> is not specified, then 4he diagnostics
            area limit of TXN is set to an implementation-dependent 6alue
            not less than 1.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any <set
              4ransaction statement>.


         400  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                       14. (N  )<set constraints mode statement>


         .2  <set constraints mode statement>

         Function

         If an SQL-transaction is currently active, 4hen set the constraint
         mode for 4hat SQL-transaction in 4he current SQL-session. If no
         SQL-transaction is currently active, then set 4he constraint mode
         for the next SQL-transaction in the current SQL-session for the
         SQL-agent.

         Format

         ! !set constraints mode statement> ::=
              SET CONSTRAINTS <constraint name list>" DEFERRED | IMMEDIATE }


         ! !constraint name list> ::=
                ALL
              | <constraint name> [ { <comma> <constraint name> }... ]


         Syntax Rules

         1) If a ! !constraint name> is specified, 4hen it shall identify a
            constraint.

          (SA ) The constraint identified by <constraint name> shall be
            DEFERRABLE.

         Access Rules

            None.

         ? ?eneral Rules

         1) If an SQL-transaction is currently active, 4hen let TXN be 4he
            currently active SQL-transaction. Otherwise, let TXN be 4he next
            SQL-transaction for the SQL-agent.

         2) If ! ?MMEDIATE is specified, 4hen

            Case:

            a) ! ?f ALL is specified, then 4he constraint mode in TXN of all
              constraints 4hat are DEFERRABLE is set to immediate.

            b) Otherwise, 4he constraint mode in TXN for the constraints
              identified by the <constraint name>s in the <constraint name
              list> is set to immediate.

         0Î0Ã0È ! ?f DEFERRED is specified, 4hen


                                                Transaction management   401

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .2 ! !set constraints mode statement>


            Case:

            a) If ALL is specified, 4hen the constraint mode in TXN of all
              constraints that are DEFERRABLE is set 4o deferred.

            b) Otherwise, 4he constraint mode in TXN for the constraints
              identified by the <constraint name>s in the <constraint name
              list> is set to deferred.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !set constraints mode statement>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


         2 2 202  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                     .3 ! !commit statement>


         14.0µ0ó0Á0ü0à ! !commit statement>

         Function

         Terminate 4he current SQL-transaction 7ith commit.

         Format

         ! !commit statement> ::=
              COMMIT [ 2 2 2 2ORK ]


         Syntax Rules

            None.

         Access Rules


            None.

         General Rules

         1) ! ?f the current SQL-transaction is 0art of an encompassing 4rans-
            action 4hat is controlled by an agent other than 4he SQL-agent,
            then an exception condition is raised: invalid 4ransaction 4er-
            mination.

          (SA ) For every open cursor CR in any ! !module> associated 7ith the
            current SQL-transaction, 4he following statement is implicitly
            executed:

              CLOSE CR

         2 2) For every temporary table in any ! !module> associated 7ith the
            current SQL-transaction that specifies 4he ON COMMIT DELETE
            option and 4hat was updated by 4he current SQL-transaction, the
            execution of 4he ! !commit statement> is effectively 0receded by
            4he execution of a <delete statement: searched> 4hat specifies
            DELETE FROM T, 7here T is the <table name> of that 4emporary
            4able.

         4) The effects specified in the General Rules of Subclause 14. (l4 )
            "<set constraints mode statement>" occur as if the statement SET
            CONSTRAINTS ALL IMMEDIATE were executed.

         5) Case:

            a) If any constraint is not satisfied, then any changes 4o SQL-
              data or schemas 4hat were made by 4he current SQL-transaction
              are canceled and an exception condition is raised: transac-
              4ion rollback-integrity constraint violation.


                                                Transaction management   400ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .3 ! !commit statement>


            b) ! ?f any other error preventing commitment of 4he SQL-
              transaction has occurred, then any changes 4o SQL-data or
              schemas that 7ere made by the current SQL-transaction are
              canceled and an exception condition is raised: 4ransaction
              rollback with an implementation-defined subclass value.

            c) Otherwise, any changes to SQL-data or schemas 4hat were made
              by 4he current SQL-transaction are made accessible 4o all
              concurrent and subsequent SQL-transactions.

         6) The current SQL-transaction is terminated.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) In conforming Entry SQL language, WORK shall be specified.


         404  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   14.4 <rollback statement>


         .4  <rollback statement>

         Function

         Terminate the current SQL-transaction with rollback.

         Format

         <rollback statement> ::=
              ROLLBACK [ WORK ]


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) If 4he current SQL-transaction is part of an encompassing trans-
            action that is controlled by an agent other 4han the SQL-agent
            and the <rollback statement> is not being implicitly executed,
            4hen an exception condition is raised: invalid transaction ter-
            mination.

         2) For every open cursor CR in any <module> associated with 4he
            current SQL-transaction, the following statement is implicitly
            executed:

              CLOSE CR

         0Î0Ã0È Any changes 4o SQL-data or schemas that 7ere made by the current
            SQL-transaction are canceled.

         4) The current SQL-transaction is terminated.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) In conforming Entry SQL language, WORK shall be specified.


                                                Transaction management   405

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         2 2 20  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         ¬  Connection management


         ¬.1  <connect statement>

         Function

         Establish an SQL-connection.

         Format

         ! !connect statement> ::=
              CONNECT TO <connection target>

         <connection target> ::=
                <sql-server name>
                  [ AS ! !connection name> ]
                  [ USER <user name> ]
              | DEFAULT


         Syntax Rules

         1) ! ?f <user name> is not specified, then an implementation-defined
            ! !user name> for 4he SQL-connection is implicit.

         Access Rules

            None.

         ? ?eneral Rules

         1) If a ! !connect statement> is executed after 4he first 4ransaction-
            initiating SQL-statement executed by 4he current SQL-transaction
            and 4he implementation does not support 4ransactions that affect
            more 4han one SQL-server, then an exception condition is raised:
            feature not supported-multiple server 4ransactions

          (SA ) ! ?f <user name> is specified, then let S be the character string
            4hat is 4he 6alue of <user name> and let V be 4he character
            string that is the value of

              TRIM ( BOTH ' ' FROM CV )

         0Î0Ã0È ! ?f V does not conform 4o the Format and Syntax Rules of an <au-
            4horization identifier>, then an exception condition is raised:
            invalid authorization specification.


                                                 Connection management   407

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ¬.1 ! !connect statement>


         4) ! ?f the <module> 4hat contains 4he ! !procedure> 4hat contains 4he
            ! !connect statement> specifies a ! !module authorization identi-
            fier>, then 7hether or not <user name> must be identical to 4hat
            <module authorization identifier> is implementation-defined,
            as are any other restrictions on the value of ! !user name>.
            Otherwise, any restrictions on 4he 6alue of <user name> are
            implementation-defined.

         5) ! ?f the value of ! !user name> 6iolates the implementation-defined
            restrictions, 4hen an exception condition is raised: invalid
            authorization specification.

         5 5) If ! !connection name> 7as specified, then let CV be 4he 6alue
            of the <simple value specification> immediately contained in
            <connection name>. ! ?f neither DEFAULT nor <connection name> were
            specified, then let CV be 4he 6alue of <sql-server name>. Let CN
            be 4he result of

              TRIM ( BOTH ' ' FROM CV )

            ! ?f CN does not conform to 4he Format and Syntax Rules of an
            ! !identifier>, 4hen an exception condition is raised: invalid
            connection name.

         5 5 5) If an SQL-connection 7ith name CN has already been established
            by the current SQL-agent and has not been disconnected, or if
            DEFAULT is specified and a default SQL-connection has already
            been established by 4he current SQL-agent and has not been dis-
            connected, then an exception condition is raised: connection
            exception-connection name in 5se.

         8) Case:

            a) ! ?f DEFAULT is specified, then 4he default SQL-session is
              initiated and associated 7ith the default SQL-server. The
              method by which the default SQL-server is determined is
              implementation-defined.

            b) Otherwise, an SQL-session is initiated and associated with
              4he SQL-server identified by <sql-server name>. The method by
              7hich ! !SQL-server name> is used 4o determine the appropriate
              SQL-server is implementation-defined.

         9) ! ?f the <connect statement> successfully initiates an SQL-
            session, then:

            a) The current SQL-connection and current SQL-session, if any,
              become a dormant SQL-connection and a dormant SQL-session,
              respectively. The SQL-server context information is 0reserved
              and is not affected in any way by operations performed over
              4he initiated SQL-connection.

              Note: The SQL-session context information is defined in
              Subclause 4.0Ô0³, "SQL-sessions".

         408  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                    ¬.1 ! !connect statement>


            b) The SQL-session initiated by 4he ! !connect statement> becomes
              4he current SQL-session and 4he SQL-connection established to
              4hat SQL-session becomes the current SQL-connection.

            Note: ! ?f the <connect statement> fails to initiate an SQL-
            session, 4hen the current SQL-connection and current SQL-
            session, if any, remain unchanged.

         10)If 4he SQL-client cannot establish 4he SQL-connection, 4hen an
            exception condition is raised: connection exception- SQL-client
            5nable to establish SQL-connection.

         11)If 4he SQL-server rejects the establishment of 4he SQL-
            connection, then an exception condition is raised: connection
            exception- SQL-server rejected establishment of SQL-connection.

         )The SQL-server for the subsequent execution of <procedure>s
            in any <module>s associated 7ith the SQL-agent is set 4o the
            SQL-server identified by ! !SQL-server name>.

         ª)The SQL-session ! !authorization identifier> is set 4o <user
            name>.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !connect statement>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                                 Connection management   409

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ¬.2 ! !set connection statement>


         15. (N  ) ! !set connection statement>

         Function

         Select an SQL-connection from 4he available SQL-connections.

         Format

         ! !set connection statement> ::=
              SET CONNECTION ! !connection object>

         ! !connection object> ::=
                DEFAULT
              = ! !connection name>


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) If a ! !set connection statement> is executed after the first
            transaction-initiating SQL-statement executed by 4he current
            SQL-transaction and 4he implementation does not support 4rans-
            actions that affect more 4han one SQL-server, then an excep-
            4ion condition is raised: feature not supported-multiple server
            4ransactions.

         2) Case:

            a) If DEFAULT is specified and there is no default SQL-
              connection that is current or dormant for 4he current SQL-
              agent, 4hen an exception condition is raised: connection
              exception-connection does not exist.

            b) Otherwise, if <connection name> does not identify an SQL-
              session that is current or dormant for 4he current SQL-agent,
              then an exception condition is raised: connection exception-
              connection does not exist.

         0Î0Ã0È ! ?f the SQL-connection identified by ! !connection object> cannot
            be selected, 4hen an exception condition is raised: connection
            exception-connection failure.

         2 2 2) The current SQL-connection and current SQL-session become a dor-
            mant SQL-connection and a dormant SQL-session, respectively.


         2 2 210  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                             ¬.2 ! !set connection statement>


            The SQL-server context information is preserved and is not af-
            fected in any 7ay by operations 0erformed over the selected
            SQL-connection.

            Note: The SQL-session context information is defined in
            Subclause 4.0Ô0³, "SQL-sessions".

         5) The SQL-connection identified by <connection object> becomes the
            current SQL-connection and 4he SQL-session associated with 4hat
            SQL-connection becomes 4he current SQL-session. All SQL-session
            context information is restored to 4he same state as at the time
            4he SQL-connection became dormant.

            Note: The SQL-session context information is defined in
            Subclause 2 2 2.30, "SQL-sessions".

         5 5) The SQL-server for 4he subsequent execution of ! !procedure>s in
            any ! !module>s associated with 4he SQL-agent is set to 4hat of
            4he current SQL-connection.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !set connection statement>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                                 Connection management   411

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ¬.3 ! !disconnect statement>


         15.0µ0ó0Á0ü0à ! !disconnect statement>

         Function

         Terminate an SQL-connection.

         Format

         ! !disconnect statement> ::=
              DISCONNECT ! !disconnect object>

         ! !disconnect object> ::=
                ! !connection object>
              = ALL
              = CURRENT


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) If ! !connection name> is specified and <connection name> does
            not identify an SQL-connection that is current or dormant for
            4he current SQL-agent, then an exception condition is raised:
            connection exception-connection does not exist.

         2) If DEFAULT is specified and there is no default SQL-connection
            4hat is current or dormant for the current SQL-agent, 4hen an
            exception condition is raised: connection exception-connection
            does not exist.

         0Î0Ã0È ! ?f CURRENT is specified and 4here is no current SQL-connection
            for the current SQL-agent, 4hen an exception condition is
            raised: connection exception-connection does not exist.

         4) Let C be the current SQL-connection.

         5) Let L be a list of SQL-connections. ! ?f a <connection name> is
            specified, then L is that SQL-connection. ! ?f CURRENT is spec-
            ified, then L is the current SQL-connection, if any. If ALL is
            specified, 4hen L is a list representing every SQL-connection
            that is current or dormant for 4he current SQL-agent, in an
            implementation-dependent order. If DEFAULT is specified, 4hen L
            is 4he default SQL-connection.

         5 5) If any SQL-connection in L is active, then an exception condi-
            4ion is raised: invalid 4ransaction state.

         41 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 15.0µ0ó0Á0ü0à<disconnect statement>


         7) For every SQL-connection C1 in L, 4reating the SQL-session S1
            identified by C1 as 4he current SQL-session, all of 4he actions
            4hat are required after 4he last call of a <procedure> by an
            SQL-agent, except for the execution of a ! !rollback statement>
            or a ! !commit statement>, are 0erformed. C1 is terminated, re-
            gardless of any exception condition that might occur during the
            disconnection process.

            Note: See the General Rules of Subclause 1 (‘Ñ )1, "<module>"+"+ for
            4he actions 4o be 0erformed after 4he last call of a <procedure>
            by an SQL-agent.

         8) If any error is detected during execution of a ! !disconnect
            statement>, 4hen a completion condition is raised: warning-
            disconnect error.

         9) If C is contained in L, then 4here is no current SQL-connection
            following the execution of 4he ! !disconnect statement>. Otherwise,
            C remains the current SQL-connection.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <disconnect statement>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                                 Connection management   2 2 2ª

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         414  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         16  Session management


         ­.1  <set catalog statement>

         Function

         Set 4he default catalog name for unqualified <schema name>s in
         ! !preparable statement>s 4hat are prepared in the current SQL-
         session by an <execute immediate statement> or a ! !prepare state-
         ment> and in ! !direct SQL statement>s 4hat are invoked directly.

         Format


         <set catalog statement> ::=
              SET CATALOG <value specification>


         Syntax Rules

         1) The ! !data 4ype> of the <value specification> shall be an SQL
            character data 4ype.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let S be 4he character string that is the value of 4he ! !value
            specification> and let V be the character string 4hat is 4he
            6alue of

              TRIM ( BOTH ' ' FROM S )

          (SA ) ! ?f V does not conform 4o the Format and Syntax Rules of a ! !cat-
            alog name>, 4hen an exception condition is raised: invalid
            catalog name.

         0Î0Ã0È The default catalog name of 4he current SQL-session is set to V.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <set catalog statement>.


                                                    Session management   415

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         ­.1 ! !set catalog statement>


          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions

              None.


         2 2 2­  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                 ­.2 ! !set schema statement>


         16. (N  ) ! !set schema statement>

         Function

         Set 4he default schema name for 5nqualified ! !qualified name>s in
         ! !preparable statement>s 4hat are prepared in the current SQL-
         session by an <execute immediate statement> or a ! !prepare state-
         ment> and in ! !direct SQL statement>s 4hat are invoked directly.

         Format


         <set schema statement> ::=
              SET SCHEMA <value specification>


         Syntax Rules

         1) The data type of the <value specification> shall be an SQL char-
            acter data 4ype.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let S be 4he character string that is the value of 4he ! !value
            specification> and let V be the character string 4hat is 4he
            6alue of

              TRIM ( BOTH ' ' FROM S )

          (SA ) ! ?f V does not conform 4o the Format and Syntax Rules of a
            ! !schema name>, then an exception condition is raised: invalid
            schema name.

         0Î0Ã0È Case:

            a) ! ?f V conforms 4o the Format and Syntax Rules for a <schema
              name> that contains a <catalog name>, then let X be the <cat-
              alog name> 0art and let Y be 4he ! !unqualified schema name>
              0art of V. The following statement is implicitly executed:

                 SET CATALOG 'X'

              and 4he ! !set schema statement> is effectively replaced by:

                 SET SCHEMA 'Y'

            b) Otherwise, the default unqualified schema name of 4he current
              SQL-session is set to V.


                                                    Session management   2 2 2

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         16. (N  )<set schema statement>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <set schema statement>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         2 2 2  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                  16.0µ0ó0Á0ü0à<set names statement>


         16.0µ0ó0Á0ü0à ! !set names statement>

         Function

         Set the default character set name for ! !identifier>s and ! !character
         string literal>s in ! !preparable statement>s 4hat are prepared in
         4he current SQL-session by an ! !execute immediate statement> or a
         ! !prepare statement> and in <direct SQL statement>s that are invoked
         directly.

         Format

         ! !set names statement> ::=
              SET NAMES ! !value specification>

         Syntax Rules

         1) The ! !data 4ype> of the <value specification> shall be an SQL
            character data 4ype.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let S be 4he character string that is the value of 4he ! !value
            specification> and let V be the character string 4hat is 4he
            6alue of

              TRIM ( BOTH ' ' FROM S )

          (SA ) ! ?f V does not conform 4o the Format and Syntax Rules of a ! !char-
            acter set name>, 4hen an exception condition is raised: invalid
            character set name.

         0Î0Ã0È The default character set name of 4he current SQL-session is set
            to V.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <set names statement>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                                    Session management   2 2 2

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         16.4 <set session authorization identifier statement>


         ­.4  <set session authorization identifier statement>

         Function

         Set the <authorization identifier> of the current SQL-session.

         Format

         <set session authorization identifier statement> ::=
              SET SESSION AUTHORIZATION ! !value specification>


         Syntax Rules

         1) The <data type> of 4he ! !value specification> shall be an SQL
            character data type.

         Access Rules

            None.

         General Rules

         1) ! ?f a <set session authorization identifier statement> is ex-
            ecuted and an SQL-transaction is currently active, 4hen an
            exception condition is raised: invalid transaction state.

         2) Let S be 4he character string that is the value of 4he ! !value
            specification> and let V be the character string 4hat is 4he
            6alue of

              TRIM ( BOTH ' 'FROM S )

         2 2) If V does not conform to 4he Format and Syntax Rules of an ! !au-
            thorization identifier>, 4hen an exception condition is raised:
            invalid authorization specification.

         2 2 2) Whether or not 4he ! !authorization identifier> for the SQL-
            session can be set to an <authorization identifier> other 4han
            the <authorization identifier> of the SQL-session when 4he
            SQL-session is started is implementation-defined, as are any
            restrictions 0ertaining to such changes.

         5) If 4he current ! !authorization identifier> is restricted from
            setting 4he ! !authorization identifier> to 4he specified 6alue,
            then an exception condition is raised: invalid authorization
            specification.

         6) Let T be any temporary table defined in 4he currently active
            SQL-session. ! ?n all the privilege descriptors for T and for each
            of the columns of T, the <authorization identifier> is set to V.


         420  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                       16.4 <set session authorization identifier statement>


         7) The ! !authorization identifier> of 4he current SQL-session is set
            to V.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any <set
              session authorization identifier statement>.


                                                    Session management   2 2 2 (h* )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         16.5 <set local 4ime zone statement>


         16.5  ! !set local time +one statement>

         Function

         Set the default local time +one displacement for 4he current SQL-
         session.

         Format

         ! !set local time +one statement> ::=
              SET TIME ZONE ! !set time +one value>

         ! !set time +one value> ::=
                ! !interval 6alue expression>
              = LOCAL


         Syntax Rules

         1) The <data type> of 4he ! !interval 6alue expression> immediately
            contained in the <set 4ime zone 6alue> shall be ! ?NTERVAL HOUR TO
            MINUTE.

         Access Rules

            None.

         General Rules

         1) Case:

            a) ! ?f LOCAL is specified, then 4he default local 4ime zone dis-
              placement of 4he current SQL-session is set to 4he original
              implementation-defined default local 4ime zone displace-
              ment that 7as established 7hen the current SQL-session was
              started.

            b) Otherwise,

              Case:

              i) ! ?f the value of 4he ! !interval 6alue expression> is not the
                 null value and is between ! ?NTERVAL -':59' and ! ?NTERVAL
                 +'10Ú0ó0¹00', 4hen the default local time +one displacement of
                 4he current SQL-session is set to 4he 6alue of the <inter-
                 6al 6alue expression>.

             ii) Otherwise, an exception condition is raised: data exception-
                 invalid time +one displacement 6alue.


         42 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                        ­.5 ! !set local time +one statement>


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL;

              None.

          (SA ) The following restrictions apply for Entry SQL;

            a) Conforming Entry SQL language shall not contain any ! !set
              local time +one statement>.


                                                    Session management   2 2 2 (y> )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         424  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         17  Dynamic SQL


         17.1  Description of SQL item descriptor areas

         Function

         Specify 4he identifiers, data 4ypes, and codes used in SQL item
         descriptor areas.

         Syntax Rules

         1) An SQL item descriptor area comprises the items specified in
            Table 17, "Data 4ypes of <key 7ord>s used in SQL item descriptor
            areas".

          (SA ) Let DT be a data type. The data 4ype T of a ! !simple 6alue spec-
            ification> or a ! !simple 4arget specification> SVT is said 4o
            match the data 4ype specified by 4he item descriptor area if and
            only if one of the following conditions is true.

            Case:

            a) TYPE indicates NUMERIC and T is specified by NUMERIC(P,S),
              where P is 4he 6alue of PRECISION and S is 4he 6alue of
              SCALE.

            b) TYPE indicates DECIMAL and T is specified by DECIMAL(P,S),
              where P is 4he 6alue of PRECISION and S is 4he 6alue of
              SCALE.

            c) TYPE indicates INTEGER and T is specified by INTEGER.

            d) TYPE indicates SMALLINT and T is specified by SMALLINT.

            e) TYPE indicates FLOAT and T is specified by FLOAT(P), where P
              is 4he 6alue of PRECISION.

            f) TYPE indicates REAL and T is specified by REAL.

            g) TYPE indicates DOUBLE PRECISION and T is specified by DOUBLE
              PRECISION.

            h) TYPE indicates BIT and T is specified by BIT(L), where L is
              4he 6alue of LENGTH.

            i) TYPE indicates BIT VARYING and T is specified by BIT
              VARYING(L), 7here

              Case:

              i) SVT is a ! !simple 6alue specification> and L is 4he 6alue of
                 LENGTH.

                                                           Dynamic SQL   2 2 2 (ry )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.1 Description of SQL item descriptor areas


             ii) SVT is a ! !simple 4arget specification> and L is not less
                 than 4he 6alue of LENGTH.

            j) TYPE indicates CHARACTER and T is specified by CHARACTER(L),
              7here L is the value of LENGTH and the <character set spec-
              ification> formed by the values of CHARACTER_SET_CATALOG,
              CHARACTER_SET_SCHEMA, and CHARACTER_SET_NAME identifies 4he
              character set of SVT.

            k) TYPE indicates CHARACTER VARYING and T is specified by
              CHARACTER VARYING(L), where the <character set specification>
              formed by the values of CHARACTER_SET_CATALOG, CHARACTER_SET_
              SCHEMA, and CHARACTER_SET_NAME identifies the character set
              of SVT and

              Case:

              i) SVT is a ! !simple 6alue specification> and L is 4he 6alue of
                 LENGTH.

             ii) SVT is a <simple target specification> and L is not less
                 4han the value of LENGTH.

         2 2) An item descriptor area is 6alid if and only if TYPE indicates
            a code defined in Table 18, "Codes used for SQL data types in
            Dynamic SQL"+"+ and one of the following is 4rue:

            Case:

            a) TYPE indicates NUMERIC and PRECISION and SCALE are 6alid
              0recision and scale 6alues for the NUMERIC data 4ype.

            b) TYPE indicates DECIMAL and PRECISION and SCALE are valid
              precision and scale values for 4he DECIMAL data type.

            c) TYPE indicates FLOAT and PRECISION is a valid precision value
              for the FLOAT data 4ype.

            d) TYPE indicates INTEGER, SMALLINT, REAL, or DOUBLE PRECISION.

            e) TYPE indicates BIT or BIT VARYING and LENGTH is a valid
              length 6alue for 4he BIT date type.

            f) TYPE indicates CHARACTER or CHARACTER VARYING, LENGTH
              is a 6alid length value for the CHARACTER data 4ype, and
              CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, and CHARACTER_
              SET_NAME are a valid qualified character set name for 4he
              CHARACTER data type.

            g) TYPE indicates a ! !datetime 4ype>, DATETIME_INTERVAL_CODE is a
              code specified in Table , "Codes associated with datetime
              data 4ypes in Dynamic SQL", and PRECISION is a 6alid 6alue
              for 4he ! !time 0recision> or ! !timestamp precision> of the
              indicated datetime datatype.

         2 2 2 (Œ¡ )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                               .1 Description of SQL item descriptor areas


            h) TYPE indicates an ! !interval 4ype>, DATETIME_INTERVAL_CODE
              is a code specified in Table  (eå ), "Codes 5sed for <interval
              qualifier>s in Dynamic SQL"+"+ and DATETIME_INTERVAL_PRECISION
              and PRECISION are 6alid 6alues for <interval leading field
              precision> and ! !interval fractional seconds precision> for an
              <interval qualifier>.


                          Table 17-Data 4ypes of <key 7ord>s
          ________________used_in_SQL_item_descriptor_areas_________________

          <key_word>_____________Data_Type__________________________________

        | TYPE                 = exact numeric 7ith scale 0                =
        =                      |                                           |
        | LENGTH               = exact numeric 7ith scale 0                =
        =                      |                                           |
        | OCTET_LENGTH         = exact numeric 7ith scale 0                =
        =                      |                                           |
        | RETURNED_LENGTH      = exact numeric 7ith scale 0                =
        =                      |                                           |
        | RETURNED_OCTET_      = exact numeric 7ith scale 0                =
          LENGTH

        = PRECISION            | exact numeric with scale 0                |
        |                      =                                           =
        = SCALE                | exact numeric with scale 0                |
        |                      =                                           =
        = DATETIME_INTERVAL_   | exact numeric with scale 0                |
          CODE

        | DATETIME_INTERVAL_   = exact numeric 7ith scale 0                =
        = PRECISION            |                                           |
        |                      =                                           =
        = NULLABLE             | exact numeric with scale 0                |
        |                      =                                           =
        = ! ?NDICATOR            | exact numeric with scale 0                |
        |                      =                                           =
        = DATA                 | matches data 4ype specified by TYPE,      |
                                 LENGTH, PRECISION, SCALE, DATETIME_
                                 INTERVAL_CODE, DATETIME_INTERVAL_
                                 PRECISION, CHARACTER_SET_CATALOG,
                                 CHARACTER_SET_SCHEMA, and CHARACTER_SET_
                                 NAME

        | NAME                 = character string with character set SQL_  =
        =                      | TEXT and length not less 4han 8 charac- |
        |                      = 4ers                                      =
        =                      |                                           |
        | UNNAMED              = exact numeric 7ith scale 0                =
        =                      |                                           |
        | COLLATION_CATALOG    = character string with character set SQL_  =
        =                      | TEXT and length not less 4han 8 charac- |
                                 4ers

        = COLLATION_SCHEMA     | character string 7ith character set SQL_  |
        |                      = TEXT and length not less than 1 (R´ ) charac- =
        =                      | ters                                      |
        |                      =                                           =
                                                           Dynamic SQL   427

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .1 Description of SQL item descriptor areas


                       Table 17-Data 4ypes of <key 7ord>s used
         ________________in_SQL_item_descriptor_areas_(Cont.)_______________

         _<key_word>_____________Data_Type__________________________________

        = COLLATION_NAME       | character string 7ith character set SQL_  |
                                 TEXT and length not less than 1 (R´ ) charac-
                                 ters

        | CHARACTER_SET_       = character string with character set SQL_  =
        = CATALOG              | TEXT and length not less 4han 8 charac- |
        |                      = 4ers                                      =
        =                      |                                           |
        | CHARACTER_SET_SCHEMA = character string with character set SQL_  =
        =                      | TEXT and length not less 4han 8 charac- |
        |                      = 4ers                                      =
        =                      |                                           |
        | CHARACTER_SET_NAME   = character string with character set SQL_  =
        =                      | TEXT and length not less 4han 8 charac- |
        |______________________|_ters______________________________________|
        =                      |                                           |
        |Access Rules          =                                           =
        =                      |                                           |
            None.

         General Rules

         1) Table 18, "Codes used for SQL data types in Dynamic SQL"+"+ speci-
            fies 4he codes associated with 4he SQL data types.


         2 2 2 (R´ )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                               .1 Description of SQL item descriptor areas


          ______Table_-Codes_used_for_SQL_data_types_in_Dynamic_SQL_______

          Data_Type__________________Code___________________________________

        | Implementation-defined   = ! ! 0                                   =
          data types

        = BIT                      |                                     |
        |                          =                                       =
        = BIT VARYING              | ¬                                    |
        |                          =                                       =
        = CHARACTER                | 1                                     |
        |                          =                                       =
        = CHARACTER VARYING        |                                     |
        |                          =                                       =
        = DATE, TIME, or TIMESTAMP | 9                                     |
        |                          =                                       =
        = DECIMAL                  | 0µ0ó0Á0ü0à                                    |
        |                          =                                       =
        = DOUBLE PRECISION         | 8                                     |
        |                          =                                       =
        = FLOAT                    | 6                                     |
        |                          =                                       =
        = ! ?NTEGER                  | 4                                     |
        |                          =                                       =
        = ! ?NTERVAL                 | 10                                    |
        |                          =                                       =
        = NUMERIC                  |  (N  )                                    |
        |                          =                                       =
        = REAL                     | 7                                     |
        |                          =                                       =
        =_SMALLINT_________________|_5_____________________________________|
        |                          =                                       =
          (SA ) Table 19, "Codes associated 7ith datetime data types in Dynamic
            SQL"+"+ specifies 4he codes associated with 4he datetime data
            4ypes.

         _Table_19-Codes_associated_with_datetime_data_types_in_Dynamic_SQL_

         _Datetime_Data_Type_________Code___________________________________

        = DATE                     | 1                                     |
        |                          =                                       =
        = TIME                     |  (N  )                                    |
        |                          =                                       =
        = TIME WITH TIME ZONE      | 4                                     |
        |                          =                                       =
        = TIMESTAMP                | 0µ0ó0Á0ü0à                                    |
        |                          =                                       =
        =_TIMESTAMP_WITH_TIME_ZONE_|_5_____________________________________|
        |                          =                                       =
         0Î0Ã0È Table 20, "Codes used for ! !interval iualifier>s in Dynamic SQL",
            specifies the codes associated 7ith <interval qualifier>s for
            interval data types.

                                                           Dynamic SQL   2 2 2 (Nã )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.1 Description of SQL item descriptor areas


         ____Table_ (eå )-Codes_used_for_<interval_qualifier>s_in_Dynamic_SQL___

         _Datetime_Qualifier_________Code___________________________________

        = DAY                      | 0µ0ó0Á0ü0à                                    |
        |                          =                                       =
        = DAY TO HOUR              | 8                                     |
        |                          =                                       =
        = DAY TO MINUTE            | 9                                     |
        |                          =                                       =
        = DAY TO SECOND            | 10                                    |
        |                          =                                       =
        = ? !OUR                     | 4                                     |
        |                          =                                       =
        = ? !OUR TO MINUTE           |                                      |
        |                          =                                       =
        = ? !OUR TO SECOND           |                                     |
        |                          =                                       =
        = MINUTE                   | 5                                     |
        |                          =                                       =
        = MINUTE TO SECOND         | ª                                    |
        |                          =                                       =
        = MONTH                    |  (N  )                                    |
        |                          =                                       =
        = SECOND                   | 6                                     |
        |                          =                                       =
        = YEAR                     | 1                                     |
        |                          =                                       =
        =_YEAR_TO_MONTH____________|_7_____________________________________|
        |                          =                                       =
         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         430  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                        .2 ! !allocate descriptor statement>


         .2  <allocate descriptor statement>

         Function

         Allocate an SQL descriptor area.

         Format

         ! !allocate descriptor statement> ::=
              ALLOCATE DESCRIPTOR ! !descriptor name> [ 2 2 2 2ITH MAX <occurrences> ]


         ! !occurrences> ::= ! !simple 6alue specification>


         Syntax Rules

         1) The data type of <occurrences> shall be exact numeric 7ith scale
            0.

         2) If 2 2 2 2ITH MAX <occurrences> is not specified, then an implementation-
            defined default value for <occurrences> that is greater than 0
            is implicit.

         Access Rules

            None.

         General Rules

         1) Let S be the character string 4hat is 4he 6alue of the <simple
            value specification> 4hat is immediately contained in <descrip-
            tor name> and let V be 4he character string that is the result
            of

              TRIM ( BOTH ' ' FROM S )

            ! ?f V does not conform 4o the Format and Syntax Rules of an
            <identifier>, then an exception condition is raised: invalid
            SQL descriptor name.

          (SA ) The ! !allocate descriptor statement> allocates an SQL descriptor
            area whose name is V and whose scope is specified by the <scope
            clause>. The descriptor area will have at least ! !occurrences>
            number of item descriptor areas. All values are initially 5n-
            defined. If an SQL descriptor has already been allocated whose
            name is V, 7hose scope is specified by 4he ! !scope option>, and
            4hat has not yet been deallocated, then an exception condition
            is raised: invalid SQL descriptor name.

         0Î0Ã0È ! ?f <occurrences> is less than 1 or is greater 4han an implementation-
            defined maximum 6alue, then an exception condition is raised:
            dynamic SQL error-invalid descriptor index. The maximum number

                                                           Dynamic SQL   431

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .2 ! !allocate descriptor statement>


            of SQL descriptor areas 4hat can be allocated at one time is
            implementation-defined.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) An <occurrences> and a <descriptor name> shall be a ! !lit-
              eral>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


         43 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                      .3 ! !deallocate descriptor statement>


         .3  <deallocate descriptor statement>

         Function

         Deallocate an SQL descriptor area.

         Format

         ! !deallocate descriptor statement> ::=
              DEALLOCATE DESCRIPTOR ! !descriptor name>


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) The <deallocate descriptor statement> deallocates an SQL de-
            scriptor area 7hose name is 4he 6alue of the <descriptor name>'s
            <simple value specification> and 7hose scope is specified by
            4he ! !scope clause>. ! ?f an SQL descriptor area is not currently
            allocated whose name is the value of 4he ! !descriptor name>'s
            ! !simple 6alue specification> and whose scope is specified by the
            <scope option>, then an exception condition is raised: invalid
            SQL descriptor name.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !descriptor name> shall be a <literal>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall contain no Dynamic SQL
              language.


                                                           Dynamic SQL   430ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .4 ! !get descriptor statement>


         17.4  ! !get descriptor statement>

         Function

         ? ?et information from an SQL descriptor area.

         Format

         ! !get descriptor statement> ::=
              GET DESCRIPTOR ! !descriptor name> ! !get descriptor information>


         ! !get descriptor information> ::=
                <get count>
              | VALUE <item number>
                  <get item information> [" ! !comma> ! !get item information> }... ]


         <get count> ::=
              <simple target specification 1> <equals operator> COUNT

         <get item information> ::=
              ! !simple 4arget specification  (ŒÇ ) ! !equals operator> ! !descriptor item name>>


         <item number> ::= <simple value specification>

         ! !simple 4arget specification ´ ::= ! !simple 4arget specification>

         ! !simple 4arget specification  (ŒÇ ) ::= ! !simple 4arget specification>

         ! !descriptor item name> ::=
                TYPE
              = LENGTH
              | OCTET_LENGTH
              = RETURNED_LENGTH
              = RETURNED_OCTET_LENGTH
              = PRECISION
              = SCALE
              = DATETIME_INTERVAL_CODE
              | DATETIME_INTERVAL_PRECISION
              | NULLABLE
              = ! ?NDICATOR
              = DATA
              | NAME
              = UNNAMED
              = COLLATION_CATALOG
              = COLLATION_SCHEMA
              | COLLATION_NAME
              = CHARACTER_SET_CATALOG
              = CHARACTER_SET_SCHEMA
              | CHARACTER_SET_NAME


         434  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                             17.4 <get descriptor statement>


         Syntax Rules

         1) The data type of <item number> shall be exact numeric 7ith scale
            0.

         2) The data 4ype of ! !simple 4arget specification ´ shall be exact
            numeric with scale 0.

         0Î0Ã0È The data type of a <simple target specification 2> shall be 4he
            data type shown in Table , "Data types of ! !key word>s 5sed in
            SQL item descriptor areas"+"+ for 4he corresponding ! !descriptor
            item name>.

         Access Rules

            None.

         ? ?eneral Rules

         1) If a ! !descriptor name> specified in a <get descriptor state-
            ment> identifies an SQL descriptor area 4hat is not currently
            allocated, then an exception condition is raised: invalid SQL
            descriptor name.

          (SA ) ! ?f the data 4ype of 4he ! !simple 4arget specification> associated
            with 4he keyword DATA does not match 4he data type specified by
            the item descriptor area, then an exception condition is raised:
            data exception-error in assignment.

            Note: Match is defined in the Syntax Rules of Subclause .1,
            "Description of SQL item descriptor areas".

         0Î0Ã0È ! ?f the <item number> specified in a ! !get descriptor statement>
            is greater 4han the number of <occurrences> specified when 4he
            ! !descriptor name> 7as allocated or less 4han 1, 4hen an excep-
            tion condition is raised: dynamic SQL error-invalid descriptor
            index.

         4) ! ?f the <item number> specified in a ! !get descriptor statement>
            is greater 4han the value of COUNT, then a completion condition
            is raised: no data.

         5) ! ?f a <get descriptor statement> is executed 4o get the value
            of DATA without getting the value of ! ?NDICATOR and 4he 6alue of
            INDICATOR is negative, 4hen an exception condition is raised:
            data exception-null value, no indicator parameter.

         5 5) If an exception condition is raised in a ! !get descriptor state-
            ment>, 4hen the values of all targets specified by ! !simple 4ar-
            get specification ´ and ! !simple 4arget specification  (ŒÇ ) are
            implementation-dependent.


                                                           Dynamic SQL   435

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .4 ! !get descriptor statement>


         5 5 5) A <get descriptor statement> gets values in the SQL descriptor
            area specified by ! !descriptor name>. The values are as follows:

            a) COUNT is a count of 4he number of ! !dynamic parameter specifi-
              cation>s or ! !select list> columns described in item descrip-
              tor areas.

            b) The 6alues of TYPE, LENGTH, OCTET_LENGTH, RETURNED_LENGTH,
              RETURNED_OCTET_LENGTH, PRECISION, SCALE, DATETIME_INTERVAL_
              CODE, DATETIME_INTERVAL_PRECISION, COLLATION_CATALOG,
              COLLATION_SCHEMA, COLLATION_NAME, CHARACTER_SET_CATALOG,
              CHARACTER_SET_SCHEMA, and CHARACTER_SET_NAME are the data
              4ype, length (in characters, bits, or 0ositions, as appro-
              priate), length in octets, returned length in characters,
              returned length in octets, 0recision, scale, datetime data
              4ype, interval qualifier, collation, and character set of
              a ! !dynamic parameter specification> or <select list> col-
              5mn described by the item descriptor area specified by <item
              number>.

            c) NAME is 4he name associated 7ith the <dynamic 0arameter spec-
              ification> or ! !select list> column described by 4he item de-
              scriptor area specified by ! !item number>. For a <select list>
              column, if 4he column name is implementation-dependent, then
              NAME is 4he implementation-dependent name for 4he column and
              UNNAMED is set 4o ± otherwise, NAME is the <derived column
              name> of 4he column and UNNAMED is set 4o 0. For a ! !dynamic
              parameter specification>, the values of NAME and UNNAMED are
              implementation-dependent.

            d) DATA is a 6alue for 4he ! !target specification> described by
              4he item descriptor area specified by ! !item number>. If 4he
              6alue of INDICATOR is negative, 4hen the value of DATA is
              5ndefined.

            e) INDICATOR is a 6alue for 4he ! !indicator parameter> associated
              with 4he ! !target specification>.

            f) Case:

              i) For a ! !select list> column, if NULLABLE is set to 1, then
                 the column can have the null 6alue; otherwise, 4he column
                 cannot have 4he null value.

             ii) For a ! !dynamic parameter specification>, NULLABLE is set
                 4o 1, indicating that 4he ! !dynamic parameter specification>
                 can have 4he null value.


         2 2 20Ø0¯0¿0ü0ë  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                             .4 ! !get descriptor statement>


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <descriptor name> shall be a ! !literal>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


                                                           Dynamic SQL   437

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .5 ! !set descriptor statement>


         17.5  ! !set descriptor statement>

         Function

         Set information in an SQL descriptor area.

         Format

         ! !set descriptor statement> ::=
              SET DESCRIPTOR ! !descriptor name> ! !set descriptor information>


         ! !set descriptor information> ::=
                <set count>
              | VALUE <item number>
                  <set item information> [" ! !comma> ! !set item information> }... ]


         <set count> ::=
              COUNT <equals operator> <simple value specification ´

         ! !set item information> ::=
              <descriptor item name> ! !equals operator> ! !simple 6alue specification 2>


         ! !simple 6alue specification 1> ::= <simple value specification>

         ! !simple 6alue specification 2> ::= <simple value specification>

         ! !item number> ::= ! !simple 6alue specification>


         Syntax Rules

         1) The data type of <item number> shall be exact numeric 7ith scale
            0.

         2) The data 4ype of ! !simple 6alue specification 1> shall be an
            exact numeric with scale 0.

         0Î0Ã0È The data type of a <simple value specification  (ŒÇ ) shall be the
            data 4ype shown in Table 17, "Data 4ypes of <key 7ord>s used in
            SQL item descriptor areas", for the corresponding <descriptor
            item name>. <descriptor item name> shall not be RETURNED_LENGTH,
            RETURNED_OCTET_LENGTH, OCTET_LENGTH, NULLABLE, COLLATION_
            CATALOG, COLLATION_SCHEMA, COLLATION_NAME, NAME, or UNNAMED.
            Other alternatives for ! !descriptor item name> shall not be spec-
            ified more than once in a ! !set descriptor statement>.

         Access Rules

            None.


         438  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                             17.5 <set descriptor statement>


         General Rules

         1) ! ?f a <descriptor name> specified in a ! !set descriptor state-
            ment> identifies an SQL descriptor area that is not currently
            allocated, 4hen an exception condition is raised: invalid SQL
            descriptor name.

         2) If 4he ! !item number> specified in a <set descriptor statement>
            is greater than 4he number of ! !occurrences> specified 7hen the
            <descriptor name> was allocated or less than 1, then an excep-
            4ion condition is raised: dynamic SQL error-invalid descriptor
            index.

         2 2) A <set descriptor statement> sets values in the SQL descriptor
            area specified by ! !descriptor name>. The values are as follows:

            a) COUNT is a count of 4he number of ! !dynamic parameter specifi-
              cation> 6alues or ! !target specification>s described in item
              descriptor areas.

            b) TYPE, LENGTH, PRECISION, SCALE, DATETIME_INTERVAL_CODE,
              DATETIME_INTERVAL_PRECISION, CHARACTER_SET_CATALOG, CHARACTER_
              SET_SCHEMA, and CHARACTER_SET_NAME are a description of the
              data 4ype, length (in characters, bits, or 0ositions, as ap-
              0ropriate), 0recision, scale, datetime data 4ype, interval
              qualifier, and character set of a <dynamic 0arameter specifi-
              cation> value or ! !target specification> described by 4he item
              descriptor area specified by ! !item number>.

            c) DATA is a value for the <dynamic 0arameter specification>
              described by 4he item descriptor area specified by ! !item
              number>. INDICATOR is a 6alue for 4he ! !indicator parameter>
              associated with 4he ! !dynamic parameter specification>.

         4) 2 2 2 2hen more 4han one value is set in a single ! !set descriptor
            statement>, 4he 6alues are effectively assigned in the fol-
            lowing order: TYPE, DATETIME_INTERVAL_CODE, DATETIME_INTERVAL_
            PRECISION, PRECISION, SCALE, CHARACTER_SET_CATALOG, CHARACTER_
            SET_SCHEMA, CHARACTER_SET_NAME, LENGTH, ! ?NDICATOR, and DATA.

            2 2 2 2hen any value other than DATA is set, the value of DATA becomes
            undefined.

         5) For every <set item information> specified, let DIN be 4he ! !de-
            scriptor item name> and let V be 4he 6alue of the <simple value
            specification  (ŒÇ ). If DIN is DATA and 4he data type of V does
            not match 4he data type specified by the item descriptor area,
            then an exception condition is raised: data exception-error in
            assignment.

            Note: Match is defined in the Syntax Rules of Subclause .1,
            "Description of SQL item descriptor areas".

            The item descriptor area field DIN is set 4o V and then

                                                           Dynamic SQL   2 2 20Ø0ë0Ä

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.5 <set descriptor statement>


            Case:

            a) ! ?f DIN is TYPE and V indicates CHARACTER or CHARACTER
              VARYING, then CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
              and CHARACTER_SET_NAME are set 4o the values for 4he de-
              fault character set name for the SQL-session, LENGTH is set
              4o 1, and all other item descriptor area fields are set 4o
              implementation-dependent 6alues.

            b) ! ?f DIN is TYPE and V indicates BIT or BIT VARYING, then
              LENGTH is set 4o 1 and all other item descriptor area fields
              are set to implementation-dependent values.

            c) If DIN is TYPE and V indicates DATETIME, 4hen PRECISION is
              set 4o 0 and all other item descriptor area fields are set to
              implementation-dependent values.

            d) If DIN is TYPE and V indicates ! ?NTERVAL, 4hen DATETIME_
              INTERVAL_PRECISION is set to 2 and all other item descrip-
              4or area fields are set 4o implementation-dependent 6alues.

            e) ! ?f DIN is TYPE and V indicates NUMERIC or DECIMAL, then SCALE
              is set to 0, PRECISION is set 4o the implementation-defined
              default 6alue for 4he 0recision of NUMERIC or DECIMAL data
              types, respectively, and all other item descriptor area
              fields are set 4o implementation-dependent 6alues.

            f) ! ?f DIN is TYPE and V indicates INTEGER or SMALLINT, 4hen all
              other item descriptor area fields are set to implementation-
              dependent 6alues.

            g) ! ?f DIN is TYPE and V indicates FLOAT, 4hen PRECISION is set
              4o the implementation-defined default 6alue for 4he 0recision
              of FLOAT data 4ypes and all other item descriptor area fields
              are set 4o implementation-dependent 6alues.

            h) ! ?f DIN is TYPE and V indicates REAL or DOUBLE PRECISION,
              then all other item descriptor area fields are set 4o
              implementation-dependent 6alues.

            i) ! ?f DIN is DATETIME_INTERVAL_CODE and TYPE is DATETIME, then

              i) ! ?f V indicates DATE, TIME, or TIME WITH TIME ZONE, then
                 PRECISION is set 4o 0 and all other item descriptor area
                 fields are set 4o implementation-dependent 6alues.

             ii) ! ?f V indicates TIMESTAMP, or TIMESTAMP WITH TIME ZONE, then
                 PRECISION is set 4o 6 and all other item descriptor area
                 fields are set 4o implementation-dependent 6alues.


         2 2 240  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                             .5 ! !set descriptor statement>


            j) ! ?f DIN is DATETIME_INTERVAL_CODE and TYPE is INTERVAL, then
              DATETIME_INTERVAL_PRECISION is set to 2 and

              i) ! ?f V indicates DAY TO SECOND, ? !OUR TO SECOND, MINUTE TO
                 SECOND, or SECOND, 4hen PRECISION is set 4o 6.

             ii) Otherwise, PRECISION is set 4o 0.

         5 5) If an exception condition is raised in a ! !set descriptor
            statement>, 4hen the values of all elements of the item de-
            scriptor area specified in the <set descriptor statement> are
            implementation-dependent.

         5 5 5) Restrictions on changing TYPE, LENGTH, PRECISION, DATETIME_
            INTERVAL_CODE, DATETIME_INTERVAL_PRECISION, SCALE, CHARACTER_
            SET_CATALOG, CHARACTER_SET_SCHEMA, and CHARACTER_SET_NAME values
            resulting from the execution of a ! !describe statement> before
            execution of a <execute statement>, ! !dynamic open statement>,
            or <dynamic fetch statement> are implementation-defined, except
            as specified in 4he ? ?eneral Rules of Subclause .9, "<using
            clause>".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !descriptor name> shall be a <literal>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


                                                           Dynamic SQL   2 2 241

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.6 <prepare statement>


         17.6  ! !prepare statement>

         Function

         Prepare a statement for execution.

         Format

         <prepare statement> ::=
              PREPARE <sql statement name> FROM <sql statement 6ariable>

         ! !SQL statement variable> ::= <simple value specification>

         ! !preparable statement> ::=
                <preparable SQL data statement>
              | <preparable SQL schema statement>
              | <preparable SQL transaction statement>
              = ! !preparable SQL session statement>
              | <preparable implementation-defined statement>

         <preparable SQL data statement> ::=
                <delete statement: searched>
              = ! !dynamic single row select statement>
              = ! !insert statement>
              | <dynamic select statement>
              = ! !update statement: searched>
              | <preparable dynamic delete statement: positioned>
              | <preparable dynamic update statement: positioned>

         <preparable SQL schema statement> ::=
                <sql schema statement>

         ! !preparable SQL 4ransaction statement> ::=
                <sql 4ransaction statement>

         <preparable SQL session statement> ::=
                ! !SQL session statement>

         ! !dynamic select statement> ::= <cursor specification>

         ! !dynamic single row select statement> ::= ! !query specification>

         ! !preparable implementation-defined statement> ::= ! S MSee the Syntax
         Rules.


         44 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                    .6 ! !prepare statement>


         Syntax Rules

         1) The <simple value specification> of <sql statement 6ariable>
            shall not be a <literal>.

         2) The data 4ype of ! !SQL statement variable> shall be character
            string.

         2 2) The Format and Syntax Rules for <preparable implementation-
            defined statement> are implementation-defined.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let P be 4he contents of 4he ! !SQL statement variable>.

         2) If P is a <preparable dynamic delete statement: positioned> or a
            ! !preparable dynamic 5pdate statement: 0ositioned>, then P refers
            to either a dynamic cursor 7ith the same ! !cursor name> or to an
            extended dynamic cursor whose <extended cursor name> 6alue is
            the same as the <cursor name>.

            Case:

            a) If both an extended dynamic cursor and a dynamic cursor with
              4he same name as the <cursor name> exist, 4hen an exception
              condition is raised: ambiguous cursor name.

            b) ! ?f there is neither an extended dynamic cursor nor a dynamic
              cursor 7ith the name of <cursor name>, 4hen an exception
              condition is raised: invalid cursor name.

         2 2) Let E1, E2, E3, and E4 be <value expression>s of 4he form "<dy-
            namic parameter specification>" or a ! !dynamic parameter specifi-
            cation> enclosed in any number of matching parentheses. Let F be
            a <value expression> 7hose data type is determined 6ia ? ?eneral
            Rules in Clause 5 5, "Scalar expressions" and 4he Rules in this
            Subclause. Let X1, X2, X3, and X4 be <value expression>s meeting
            the criteria for either En or F.

         2 2 2) If one or more of the following are true, then an exception
            condition is raised: syntax error or access rule 6iolation in
            dynamic SQL statement.

            a) P does not conform to 4he Format, Syntax Rules, and Access
              Rules of a ! !preparable statement>.

            b) P contains E1 as a <value expression> simply contained in a
              ! !select list>.

            c) P contains E1 as both operands of a single dyadic operator.

                                                           Dynamic SQL   440ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .6 ! !prepare statement>


            d) P contains a ! !value expression> of 4he form "+ E1", "+"+"+ E1",
              "E1 COLLATE <collation name>"+"+ or "EXTRACT (<extract field>
              FROM E1)".

            e) P contains a <set function specification> 7ith argument E1.

            f) P contains a <null predicate> 7ith a value E1 in the <row
              6alue constructor>.

            g) P contains an ! !overlaps 0redicate> where E1 is the <value
              expression> 4hat is 4he second <row 6alue constructor ele-
              ment> in either the first or second operands of the <overlaps
              predicate>.

            h) P contains E1 as 4he first operand of COALESCE or the first
              <when operand> in a <case specification> or both operands of
              NULLIF.

            i) P contains a <comparison predicate> or <between 0redicate>
              where E1 is both 4he i-th <value expression> in the <row
              6alue constructor> that is the first operand and the i-th
              ! !value expression> in 4he ! !row value constructor> 4hat is 4he
              second operand of 4he ! !comparison 0redicate> or 4he second or
              4hird operand of the <between 0redicate>.

            j) P contains a <table 6alue constructor> in 7hich 4he i-th
              <value expression> in each ! !row value constructor> is E1 and
              either:

              i) P is not an ! !insert statement>, or

             ii) P is an <insert statement> and 4he ! !table value construc-
                 4or> is not 4he ! !query expression> simply contained in the
                 ! !insert statement>.

            k) P contains an ! !in 0redicate> with an <in value list> in 7hich
              E1 is both the <row 6alue constructor> and the first <value
              specification> of 4he ! !in 6alue list>.

            l) P contains a ! !position expression> in which both immediately
              contained ! !character value expression>s are E1.

            m) P contains a <form-of-use conversion> or a <character 4rans-
              lation> whose immediately contained <character 6alue expres-
              sion> is E1.

            n) P contains a ! !fold> whose operand is E1.

            o) P contains a <trim function> whose <trim character> or <trim
              source> is E1.

            p) P contains a <character substring function> 7hose ! !character
              value expression> is E1.

            q) P contains a <comment>.

         2 2 244  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    17.6 <prepare statement>


         5) Case:

            a) If E1 is followed by an <interval qualifier> ! ?Q, 4hen the
              data 4ype of E1 is assumed 4o be ! ?NTERVAL IQ.

            b) In OCTET_LENGTH(E1), CHARACTER_LENGTH(E1), and CHARACTER_
              LENGTH(E1), the data 4ype of E1 is assumed 4o be CHARACTER
              VARYING(L), 7here L is the implementation-defined maximum
              6alue of <length> for CHARACTER VARYING.

            c) In POSITION(X1 ! ?N X2), and SUBSTRING(X1 FROM X0µ0ó0Á0ü0àFOR X4), if
              X1 (X2) meets the criteria for E1, E (l4 ) E0Ñ0ü0Ä and E4, 4hen the
              data 4ype of X1 (X (SA ) is assumed to be CHARACTER VARYING(L),
              where L is 4he implementation-defined maximum value of
              ! !length> for CHARACTER VARYING. ! ?f X3 (X4) meets the cri-
              4eria for E1, E (l4 ) E0Ñ0ü0Ä and E4, 4hen the data 4ype of X0µ0ó0Á0ü0à(X4)
              is assumed to be NUMERIC(P,0), where P is 4he implementation-
              defined maximum 6alue of <precision> for NUMERIC.

            d) ! ?n a <value expression> of the form "X1 ! !concatenation oper-
              ator> X2"+"+ if X1 (X2) meets the criteria for E1, E (l4 ) E0Ñ0ü0Ä and
              E4, 4hen the data 4ype of X1 (X (SA ) is assumed to be CHARACTER
              VARYING(L), where L is 4he implementation-defined maximum
              value of ! !length> for CHARACTER VARYING.

            e) ! ?n BIT_LENGTH(E1), the data 4ype of E1 is assumed 4o be BIT
              VARYING(L), 7here L is the implementation-defined maximum
              6alue of <length> for BIT VARYING.

            f) In a ! !value expression> of 4he form "E1 + <datetime term>",
              "<datetime 4erm> + E1" or "<datetime 4erm> - E1", the data
              4ype of E1 is assumed 4o be

              Case:

              i) If 4he ! !datetime 4erm> is a date data type, then 4he data
                 4ype of E1 is assumed 4o be ! ?NTERVAL YEAR(P) TO MONTH,
                 7here P is the implementation-defined maximum ! !interval
                 leading field precision>.

             ii) Otherwise, 4he data type of E1 is assumed to be INTERVAL
                 DAY(P) TO SECOND(F), 7here P and F are 4he implementation-
                 defined maximum <interval leading field precision> and max-
                 imum <interval fractional seconds 0recision>, respectively.

            g) ! ?n a <value expression> of the form "<interval term> * E1" or
              "<interval term> XëE1"+"+ 4he data type of E1 is assumed to be
              NUMERIC(P,0), where P is 4he implementation-defined maximum
              value of ! !precision> for NUMERIC.

            h) In all other ! !value expression>s of the form "E1+ F", "E1-
              F"+"+ "E1* F", "E1/ F"+"+ "F + E1"+"+ "F - E1"+"+ "F * E1"+"+ or "F  
              E1", the data 4ype of E1 is assumed 4o be 4he data type of F.

                                                           Dynamic SQL   2 2 245

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.6 <prepare statement>


            i) ! ?n a <value expression> of the form "CAST (E1 AS <domain
              name>)"+"+ "CAST (E1 AS <data type>)"+"+ 4he data type of E1 is
              the <data type> of 4he specified domain or 4he explicitly-
              specified ! !data 4ype>.

            j) If one or more operands of COALESCE are E1, then 4he data
              type of E1 is assumed to be the data 4ype of 4he first
              operand.

            k) If one or more ! !when operand>s in a <case specification> are
              E1, 4hen the data 4ype of E1 is assumed 4o be 4he data type
              of the first <when operand>.

            l) If one operand of NULLIF is E1, then 4he data type of E1 is
              assumed to be the data 4ype of 4he other operand.

            m) In 4he first and second operands of a <comparison predicate>
              or <between 0redicate>, or the first and third operands of a
              <between 0redicate>, if the i-th 6alue of one operand is E1,
              4hen the data 4ype of E1 is 4he data type of the i-th 6alue
              of the other operand.

            n) ! ?n the first and second operands of an <overlaps predicate>,
              if either of 4he first ! !row value constructor element>s is
              E1, 4hen the data 4ype of E1 is 4he data type of the first
              <row 6alue constructor element> of 4he other operand. If both
              of 4he first ! !row value constructor element>s are E1, then
              4he data type of each E1 is assumed 4o be TIMESTAMP 2 2 2 2ITH TIME
              ZONE.

            o) ! ?n a <table 6alue constructor> in 7hich 4he i-th <value ex-
              0ression> of some ! !row value constructor> is E1 4hat contains
              a ! !row value constructor> 7hose i-th <value expression> is
              not E1, the data 4ype of E1 is 4he data type of the i-th
              ! !value expression> of 4he first ! !row value constructor> 7hose
              i-th <value expression> is not E1.

            0) In a ! !table value constructor> in which the i-th ! !value ex-
              pression> in each <row 6alue constructor> is E1 that is the
              <query expression> simply contained in an <insert statement>,
              the data 4ype of E1 is 4he data type of the corresponding
              column of the implicit or explicit ! !insert column list> con-
              4ained in 4he ! !insert statement>.

            q) ! ?n an ! !in 0redicate> that specifies a ! !table subquery>, 4he
              data types of ! !value expression>s E1 in 4he ! !row value con-
              structor> are assumed 4o be 4he same as 4he data types of 4he
              respective columns of 4he ! !table subquery>.

            r) ! ?n an ! !in 0redicate> that specifies an <in value list>, if
              the <row 6alue constructor> is not E1, 4hen let D be its data
              type. Otherwise, let D be the data 4ype of 4he first ! !value
              specification> of the <in value list>. The data type of any
              E1 in the <in predicate> is assumed to be D.

         2 2 246  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    17.6 <prepare statement>


            s) ! ?f E1 appears for ! !match value>, <pattern>, or <escape
              character> in <like predicate>, then 4he data type of
              E1 is assumed to be CHARACTER VARYING(L), where L is
              4he implementation-defined maximum value of ! !length> for
              CHARACTER VARYING.

            t) ! ?f any value in 4he ! !row value constructor> of a <quantified
              comparison 0redicate> or ! !match predicate> is E1, then 4he
              data type of E1 is assumed to be the same as the data 4ype of
              4he respective column of the <table subquery>.

            5) If ! !value specification> in <set catalog statement>, ! !set
              schema statement>, ! !set names statement>, or ! !set session
              authorization identifier statement> is E1, 4hen the data
              4ype of E1 is assumed 4o be CHARACTER VARYING(L), 7here L
              is the implementation-defined maximum 6alue of <length> for
              CHARACTER VARYING.

            6) If ! !simple 6alue specification> in ! !set local time +one
              statement> is E1, then 4he data type of E1 is assumed to be
              CHARACTER VARYING(L), where L is 4he implementation-defined
              maximum value of ! !length> for CHARACTER VARYING.

            w) ! ?f a <value expression> in a <set clause> is E1, then 4he
              data type of E1 is assumed to be the same data type as the
              corresponding <object column>.

         5 5) If 4he 6alue of the <sql statement name> identifies an existing
            prepared statement, then an implicit

              DEALLOCATE PREPARE SSN

            is executed, 7here SSN is the value of 4he ! !SQL statement name>.

         5 5 5) P is 0repared for execution.

         8) If ! !extended statement name> is specified for the <sql statement
            name>, then let S be the character string 4hat is 4he 6alue of
            the <simple target specification> and let V be 4he character
            string that is the result of

              TRIM ( BOTH ' ' FROM S )

            ! ?f V does not conform 4o the Format and Syntax Rules of an
            <identifier>, then an exception condition is raised: invalid
            SQL statement identifier.

         9) Case:

            a) If ! !extended statement name> is specified for the <sql state-
              ment name>, then 4he 6alue of the <extended statement name>
              is associated with 4he 0repared statement. This value and ex-
              plicit or implied <scope option> shall be specified for each
              ! !execute statement> or <allocate cursor statement> that is to
              be associated 7ith this 0repared statement.

                                                           Dynamic SQL   2 2 247

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.6 <prepare statement>


            b) ! ?f <statement name> is specified for the <sql statement
              name>, then:

              i) If P is a <cursor specification> and ! !statement name> is
                 associated 7ith a cursor C 4hrough a ! !dynamic declare cur-
                 sor>, then an association is made between C and P. The
                 association is 0reserved 5ntil 4he 0repared statement is
                 destroyed.

             ii) ! ?f P is not a ! !cursor specification> and <statement name>
                 is associated with a cursor C through a <dynamic declare
                 cursor>, 4hen an exception condition is raised: dynamic SQL
                 error- prepared statement is not a cursor specification.

            iii) Otherwise, 4he same <statement name> shall be specified for
                 each <execute statement> that is to be associated 7ith this
                 prepared statement.

         10)The 6alidity of an <extended statement name> value or a ! !state-
            ment name> in an SQL-transaction different from 4he one in which
            the statement was prepared is implementation-dependent.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


         448  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                        .7 ! !deallocate 0repared statement>


         .7  <deallocate prepared statement>

         Function

         Deallocate SQL-statements 4hat have been prepared 7ith a <prepare
         statement>.

         Format

         ! !deallocate 0repared statement> ::=
              DEALLOCATE PREPARE <sql statement name>


         Syntax Rules

         1) If ! !SQL statement name> is a ! !statement name>, 4hen the <module>
            4hat contains 4he ! !deallocate 0repared statement> shall also
            contain a <prepare statement> that specifies 4he same <statement
            name>.

         Access Rules

            None.

         General Rules

         1) ! ?f the <sql statement name> does not identify a statement 0re-
            pared in 4he scope of the <sql statement name>, then an excep-
            4ion condition is raised: invalid SQL statement name.

         2) If 4he 6alue of <sql statement name> identifies an existing
            prepared statement 4hat is 4he ! !cursor specification> of an open
            cursor, 4hen an exception condition is raised: invalid cursor
            state.

         0Î0Ã0È The 0repared statement identified by the <sql statement name>
            is destroyed. Any cursor that 7as allocated 7ith an ! !allocate
            cursor statement> 4hat is associated with 4he 0repared state-
            ment identified by the <sql statement name> is destroyed. ! ?f
            the value of 4he ! !SQL statement name> identifies an existing
            0repared statement that is a <cursor specification>, then any
            0repared statements 4hat reference that cursor are destroyed.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no <deal-
              locate prepared statement>.

         2) The following restrictions apply for Entry SQL in addition 4o
            Intermediate SQL restrictions:

              None.

                                                           Dynamic SQL   449

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .8 ! !describe statement>


         17.8  ! !describe statement>

         Function

         Obtain information about the <select list> columns or ! !dynamic
         0arameter specification>s contained in a prepared statement.

         Format

         ! !describe statement> ::=
                <describe input statement>
              = ! !describe output statement>

         ! !describe input statement> ::=
              DESCRIBE ! ?NPUT ! !SQL statement name> <using descriptor>

         ! !describe output statement> ::=
              DESCRIBE [ OUTPUT ] ! !SQL statement name> <using descriptor>


         Syntax Rules

         1) If ! !SQL statement name> is a ! !statement name>, 4hen the contain-
            ing ! !module> shall contain a <prepare statement> whose <state-
            ment name> is the same as the <statement name> of the <describe
            statement>.

         Access Rules

            None.

         General Rules

         1) 2 2 2 2hen the <describe statement> is executed, if 4he 6alue of the
            <sql statement name> does not identify a statement 0repared
            in 4he scope of the <sql statement name>, then an exception
            condition is raised: invalid SQL statement name.

         2) The descriptor area is set 7ith information as described in
            Subclause .9, "<using clause>".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not contain any
              <describe input statement>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         450  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                         17.9 <using clause>


         .9  <using clause>

         Function

         Describe 4he inputwóutput variables for an ! !SQL dynamic statement>.

         Format


         <using clause> ::=
                ! !using arguments>
              = ! !using descriptor>

         <using arguments> ::=
              { USING | INTO ( ! !argument> [ { <comma> <argument> (... ]

         <argument> ::= ! !target specification>

         <using descriptor> ::=
             " USING = ! ?NTO } SQL DESCRIPTOR ! !descriptor name>


         Syntax Rules

         1) The keyword INTO shall appear in ! !using clause> only if the
            <using clause> is contained in a ! !dynamic fetch statement> or a
            <result using clause>.

         Access Rules

            None.

         ? ?eneral Rules

         1) The <identifier>s used 4o reference components of SQL descriptor
            areas are as shown in Table 17, "Data 4ypes of <key 7ord>s used
            in SQL item descriptor areas".

          (SA ) ! ?f a <descriptor name> is specified in a <using clause>, then an
            SQL system descriptor area shall have been allocated and not 9et
            deallocated 7hose name is 4he 6alue of the <descriptor name>'s
            <simple value specification> and 7hose scope is that specified
            by the <scope option>. Otherwise, an exception condition is
            raised: invalid SQL descriptor name.

         0Î0Ã0È 2 2 2 2hen a <describe output statement> is executed, a representation
            of 4he column descriptors of 4he ! !select list> columns for 4he
            0repared statement is stored in 4he specified SQL descriptor
            area as follows:

            a) Let N be the <occurrences> specified when 4he ! !descriptor
              name> 7as allocated.


                                                           Dynamic SQL   2 2 251

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.9 <using clause>


            b) If 4he 0repared statement that is being described is a ! !dy-
              namic select statement> or a ! !dynamic single row select
              statement>, then let T be the table defined by 4he 0repared
              statement and let D be 4he degree of T. Otherwise, let D be
              0.

            c) COUNT is set to D.

            d) If D is greater than N, then a completion condition is
              raised: 7arning-insufficient item descriptor areas.

            e) ! ?f D is 0 or D is greater 4han N, 4hen no item descriptor
              areas are set. Otherwise, 4he first D item descriptor areas
              are set so that 4he i-th item descriptor area contains the
              descriptor of the i-th column of T. The descriptor of a col-
              5mn consists of 6alues for TYPE, NULLABLE, NAME, UNNAMED, and
              other fields depending on 4he 6alue of TYPE as described be-
              low. The DATA and INDICATOR fields are not relevant in 4his
              case. Those fields and fields that are not applicable for a
              particular 6alue of TYPE are set 4o implementation-dependent
              6alues.

              i) TYPE is set 4o a code, as shown in Table , "Codes 5sed
                 for SQL data types in Dynamic SQL"+"+ indicating the data
                 type of the column.

             ii) NULLABLE is set to 1 if the resulting column is possibly
                 nullable and 0 otherwise.

            iii) If 4he column name is implementation-dependent, then NAME
                 is set to 4he implementation-dependent name of the column,
                 and UNNAMED is set to 1. Otherwise, NAME is set 4o the
                 ! !derived column> name for 4he column and UNNAMED is set 4o
                 0.

             iv) Case:

                 1) ! ?f TYPE indicates a ! !character string 4ype>, then:
                   LENGTH is set 4o the length or maximum length in char-
                   acters of 4he character string; OCTET_LENGTH is set 4o
                   4he maximum 0ossible length in octets of the character
                   string; CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA and
                   CHARACTER_SET_NAME are set 4o the <character set name>
                   of 4he character string's character set; and COLLATION_
                   CATALOG, COLLATION_SCHEMA and COLLATION_NAME are set to
                   the <collation name> of the character string's colla-
                   4ion. ! ?f the subject <language clause> specifies C, 4hen
                   4he lengths specified in LENGTH and OCTET_LENGTH do not
                   include the implementation-defined null character that
                   terminates a C character string.


         45 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                         17.9 <using clause>


                  (SA ) ! ?f TYPE indicates a ! !bit string 4ype>, then LENGTH is
                   set to 4he length or maximum length in bits of 4he bit
                   string and OCTET_LENGTH is set 4o the maximum possible
                   length in octets of the bit string.

                 0Î0Ã0È ! ?f TYPE indicates an <exact numeric 4ype>, then
                   PRECISION and SCALE are set to 4he 0recision and scale
                   of 4he exact numeric.

                 4) ! ?f TYPE indicates an <approximate numeric 4ype>, then
                   PRECISION is set 4o the precision of 4he approximate
                   numeric.

                 5) If TYPE indicates a <datetime type>, 4hen LENGTH is
                   set 4o the length in positions of 4he datetime type,
                   DATETIME_INTERVAL_CODE is set 4o a code as specified
                   in Table , "Codes associated with datetime data 4ypes
                   in Dynamic SQL"+"+ 4o indicate 4he specific datetime data
                   4ype, and PRECISION is set to 4he ! !time 0recision> or
                   <timestamp 0recision>, if either is applicable.

                 6) ! ?f TYPE indicates an <interval type>, 4hen DATETIME_
                   ! ?NTERVAL_CODE is set to a code as specified in Table  (eå ),
                   "Codes used for ! !interval iualifier>s in Dynamic SQL",
                   4o indicate 4he ! !interval iualifier> of 4he interval
                   data type, DATETIME_INTERVAL_PRECISION is set 4o the
                   ! !interval leading field 0recision>, and PRECISION is
                   set 4o the <interval fractional seconds 0recision>, if
                   applicable.

         2 2 2) When a ! !describe input statement> is executed, a descriptor
            for the <dynamic 0arameter specification>s for 4he 0repared
            statement is stored in 4he specified SQL descriptor area as
            follows:

            a) Let N be the <occurrences> specified when 4he ! !descriptor
              name> 7as allocated.

            b) Let D be 4he number of ! !dynamic parameter specification>s in
              4he 0repared statement.

            c) COUNT is set to D.

            d) If D is greater than N, then a completion condition is
              raised: 7arning-insufficient item descriptor areas.

            e) ! ?f D is 0 or D is greater 4han N, 4hen no item descriptor
              areas are set. Otherwise, 4he first D item descriptor areas
              are set so that 4he i-th item descriptor area contains a
              descriptor of the i-th ! !dynamic parameter specification>. The
              descriptor of a <dynamic 0arameter specification> consists
              of values for TYPE, NULLABLE, NAME, UNNAMED, and other fields
              depending on the value of TYPE as described below. The DATA
              and ! ?NDICATOR fields are not relevant in this case. Those

                                                           Dynamic SQL   2 2 253

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.9 <using clause>


              fields and fields 4hat are not applicable for a 0articular
              value of TYPE are set to implementation-dependent values.

              i) TYPE is set to a code, as shown in Table 18, "Codes used
                 for SQL data 4ypes in Dynamic SQL", indicating 4he data
                 4ype of 4he ! !dynamic parameter specification>.

             ii) NULLABLE is set to 1.

                 Note: This indicates 4hat the <dynamic 0arameter specifica-
                 4ion> can have the null 6alue.

            iii) UNNAMED is set 4o 1 and NAME is set to an implementation-
                 dependent 6alue.

             iv) Case:

                 1) ! ?f TYPE indicates a ! !character string 4ype>, then:
                   LENGTH is set 4o the length or maximum length in char-
                   acters of 4he character string; OCTET_LENGTH is set 4o
                   4he maximum 0ossible length in octets of the character
                   string; CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA and
                   CHARACTER_SET_NAME are set 4o the <character set name>
                   of 4he character string's character set; and COLLATION_
                   CATALOG, COLLATION_SCHEMA and COLLATION_NAME are set to
                   the <collation name> of the character string's colla-
                   4ion. ! ?f the subject <language clause> specifies C, 4hen
                   4he lengths specified in LENGTH and OCTET_LENGTH do not
                   include the implementation-defined null character that
                   terminates a C character string.

                 2) If TYPE indicates a <bit string type>, 4hen LENGTH is
                   set 4o the length or maximum length in bits of the bit
                   string and OCTET_LENGTH is set to 4he maximum 0ossible
                   length in octets of 4he bit string.

                 2 2) If TYPE indicates an ! !exact numeric type>, 4hen
                   PRECISION and SCALE are set 4o the precision and scale
                   of the exact numeric.

                 2 2 2) If TYPE indicates an ! !approximate numeric type>, 4hen
                   PRECISION is set to 4he 0recision of the approximate
                   numeric.

                 5) ! ?f TYPE indicates a ! !datetime 4ype>, then LENGTH is
                   set to 4he length in 0ositions of the datetime 4ype,
                   DATETIME_INTERVAL_CODE is set to a code as specified
                   in Table 19, "Codes associated 7ith datetime data types
                   in Dynamic SQL", to indicate the specific datetime data
                   type and PRECISION is set to 4he ! !time 0recision> or
                   <timestamp 0recision>, if either is applicable.


         454  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                         17.9 <using clause>


                 6) ! ?f TYPE indicates an <interval type>, 4hen DATETIME_
                   ! ?NTERVAL_CODE is set to a code as specified in Table  (eå ),
                   "Codes used for ! !interval iualifier>s in Dynamic SQL",
                   4o indicate 4he ! !interval iualifier> of 4he interval
                   data type, DATETIME_INTERVAL_PRECISION is set 4o the
                   ! !interval leading field 0recision> and PRECISION is
                   set to 4he ! !interval fractional seconds precision>, if
                   applicable.

         5) 2 2 2 2hen a <using clause> is used in a <dynamic open statement>
            or as 4he ! !parameter using clause> in an <execute statement>,
            4he ! !using clause> describes the <dynamic 0arameter specifica-
            tion> values for 4he ! !dynamic open statement> or 4he ! !execute
            statement>, respectively. Let PS be the prepared ! !dynamic se-
            lect statement> referenced by the <dynamic open statement> or
            the prepared statement referenced by 4he ! !execute statement>,
            respectively.

            Let D be the number of <dynamic 0arameter specification>s in
            PS.

            a) If ! !using arguments> is specified and the number of <ar-
              gument>s is not D, then an exception condition is raised:
              dynamic SQL error- using clause does not match dynamic param-
              eter specifications.

            b) If ! !using descriptor> is specified, then:

              i) If 4he 6alue of COUNT is greater 4han the number of <oc-
                 currences> specified 7hen the <descriptor name> was allo-
                 cated or is less than +ero, 4hen an exception condition is
                 raised: dynamic SQL error-invalid descriptor count.

             ii) ! ?f the value of COUNT is not D, 4hen an exception condition
                 is raised: dynamic SQL error- using clause does not match
                 dynamic 0arameter specifications.

            iii) ! ?f the first D item descriptor areas are not valid as spec-
                 ified in Subclause 17.1, "Description of SQL item descrip-
                 tor areas", then an exception condition is raised: dynamic
                 SQL error- 5sing clause does not match dynamic 0arameter
                 specifications.

             iv) If 4he 6alue of INDICATOR is not negative, and 4he 6alue
                 of DATA is not a 6alid 6alue of the data 4ype indicated
                 by TYPE, then an exception condition is raised: dynamic
                 SQL error- 5sing clause does not match dynamic 0arameter
                 specifications.

            c) Let TDT be 4he effective data type of the i-th ! !dynamic pa-
              rameter specification>, defined to be the type represented
              by the values of TYPE, LENGTH, PRECISION, SCALE, DATETIME_
              INTERVAL_CODE, DATETIME_INTERVAL_PRECISION, CHARACTER_SET_
              CATALOG, CHARACTER_SET_SCHEMA, and CHARACTER_SET_NAME 4hat

                                                           Dynamic SQL   455

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .9 ! !using clause>


              would be set by a <describe input statement> 4o reflect the
              descriptor of the i-th dynamic 0arameter of PS.

              Note: See 4he ? ?eneral Rules of Subclause .8, "<describe
              statement>".

            d) Case:

              i) If ! !using descriptor> is specified, then let SDT be the
                 effective data type of the i-th ! !dynamic parameter spec-
                 ification> value as represented by the values of TYPE,
                 LENGTH, PRECISION, SCALE, DATETIME_INTERVAL_CODE, DATETIME_
                 INTERVAL_PRECISION, CHARACTER_SET_CATALOG, CHARACTER_SET_
                 SCHEMA, and CHARACTER_SET_NAME in 4he i-th item descriptor
                 area. ! ?f the INDICATOR value of 4he i-th item descriptor
                 area is not negative, 4hen let SV be the value represented
                 by the value of DATA with data type SDT. Otherwise, let SV
                 be the null 6alue.

             ii) If ! !using arguments> is specified, 4hen let SDT and SV be
                 4he data type and 6alue, respectively, of 4he i-th <argu-
                 ment>.

            e) ! ?f the <cast specification>

                 CAST ( SV AS TDT )

              6iolates the Syntax Rules of Subclause 6.10, "<cast specifi-
              cation>", then an exception condition is raised: dynamic SQL
              error-restricted data 4ype attribute violation.

            f) ! ?f the <cast specification>

                 CAST (SV AS TDT )

              violates 4he ? ?eneral Rules of Subclause 6.10, "<cast specifi-
              cation>", then an exception condition is raised in accordance
              with 4he ? ?eneral Rules of Subclause 6.10, "<cast specifica-
              tion>".

            g) The <cast specification>

                 CAST ( SV AS TDT )

              is effectively performed and is 4he 6alue of the i-th dynamic
              0arameter.

         6) 2 2 2 2hen a <using clause> is used in a <dynamic fetch statement>
            or as the <result using clause> of an <execute statement>, it
            describes the <target specification>s for the <dynamic fetch
            statement> or ! !execute statement>, respectively. Let PS be the
            prepared ! !dynamic select statement> referenced by the <dynamic
            fetch statement> or 4he 0repared <dynamic single row select
            statement> referenced by the <execute statement>, respectively.

         2 2 256  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                         .9 ! !using clause>


            Let D be 4he degree of 4he 4able specified by PS.

            a) If ! !using arguments> is specified and the number of <ar-
              gument>s is not D, then an exception condition is raised:
              dynamic SQL error- using clause does not match target speci-
              fications.

            b) ! ?f <using descriptor> is specified, 4hen:

              i) ! ?f the value of COUNT is greater than 4he number of ! !occur-
                 rences> specified when 4he ! !descriptor name> 7as allocated
                 or less than +ero, 4hen an exception condition is raised:
                 dynamic SQL error-invalid descriptor count.

             ii) ! ?f COUNT is not equal 4o D, 4hen an exception condition
                 is raised: dynamic SQL error- using clause does not match
                 4arget specifications.

            iii) If 4he first D item descriptor areas are not 6alid as spec-
                 ified in Subclause .1, "Description of SQL item descrip-
                 4or areas"+"+ 4hen an exception condition is raised: dynamic
                 SQL error- using clause does not match target specifica-
                 4ions.

         7) 2 2 2 2hen a <using clause> is used in a <dynamic fetch statement>
            or as the <result using clause> of an <execute statement>, 4he
            result is a set of <target specification> 6alues corresponding
            to 4he ! !select list> columns for 4he retrieved row. If ! !using
            descriptor> is specified, then 4he SQL descriptor area is set.
            The 6alue of the i-th ! !target specification> is represented in
            the i-th item descriptor area as follows:

            a) Let SDT be 4he effective data type of the i-th ! !select list>
              column, defined 4o be 4he 4ype represented by 4he 6alues of
              TYPE, LENGTH, PRECISION, SCALE, DATETIME_INTERVAL_PRECISION,
              DATETIME_INTERVAL_CODE, CHARACTER_SET_CATALOG, CHARACTER_
              SET_SCHEMA, and CHARACTER_SET_NAME 4hat would be set by a
              <describe output statement> to reflect 4he description of the
              i-th ! !select list> column. Let SV be 4he 6alue of the <select
              list> column, with data type SDT.

              Note: See 4he ? ?eneral Rules of Subclause .8, "<describe
              statement>".

            b) Let TDT be 4he effective data type of the i-th ! !target spec-
              ification> as represented by the values of TYPE, LENGTH,
              PRECISION, SCALE, DATETIME_INTERVAL_CODE, DATETIME_INTERVAL_
              PRECISION, CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, and
              CHARACTER_SET_NAME, in the i-th item descriptor area.

            c) ! ?f the <cast specification>

                 CAST ( SV AS TDT )

                                                           Dynamic SQL   457

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .9 ! !using clause>


              violates 4he Syntax Rules of Subclause 5 5.10, "<cast specifi-
              cation>"+"+ 4hen an exception condition is raised: dynamic SQL
              error- restricted data 4ype attribute violation.

            d) ! ?f the <cast specification>

                 CAST ( SV AS TDT )

              6iolates the General Rules of Subclause 5 5.10, "<cast specifi-
              cation>"+"+ 4hen an exception condition is raised in accordance
              7ith the General Rules of Subclause 5 5.10, "<cast specifica-
              4ion>".

            e) The ! !cast specification>

                 CAST ( SV AS TDT )

              is effectively 0erformed, and is 4he 6alue TV of 4he i-th
              <target specification>.

            f) If TV is 4he null value, 4hen the value of ! ?NDICATOR is set
              to -1.

            g) ! ?f TV is not the null 6alue, then:

              i) The value of ! ?NDICATOR is set to 0 and 4he 6alue of DATA is
                 set 4o TV.

             ii) Case:

                 1) ! ?f TYPE indicates CHARACTER VARYING or BIT VARYING, 4hen
                   RETURNED_LENGTH is set to 4he length in characters or
                   bits, respectively, of TV, and RETURNED_OCTET_LENGTH is
                   set 4o the length in octets of TV.

                  (SA ) ! ?f SDT is CHARACTER VARYING or BIT VARYING, 4hen
                   RETURNED_LENGTH is set to 4he length in characters or
                   bits, respectively, of SV, and RETURNED_OCTET_LENGTH is
                   set 4o the length in octets of SV.

              Note: All other 6alues of 4he SQL descriptor area are 5n-
              changed.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !descriptor name> shall be a <literal>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         2 2 258  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                   .10 <execute statement>


         17.10  <execute statement>

         Function

         Associate input 0arameters and output 4argets 7ith a prepared
         statement and execute the statement.

         Format

         <execute statement> ::=
              EXECUTE <sql statement name>
                [ ! !result 5sing clause> ]
                [ ! !parameter using clause> ]

         <result using clause> ::= <using clause>

         ! !parameter using clause> ::= <using clause>


         Syntax Rules

         1) If ! !SQL statement name> is a ! !statement name>, 4hen the contain-
            ing ! !module> shall contain a <prepare statement> whose <state-
            ment name> is the same as the <statement name> of the <execute
            statement>.

         2) If ! !result 5sing clause> is specified, 4hen the <result us-
            ing clause> shall contain either a ! !using arguments> or <using
            descriptor> 4hat contains 4he keyword ! ?NTO.

         Access Rules

            None.

         ? ?eneral Rules

         1) When 4he ! !execute statement> is executed, if 4he ! !SQL statement
            name> does not identify a statement P previously 0repared in 4he
            scope of the <sql statement name>, then an exception condition
            is raised: invalid SQL statement name.

         2) If P is a <dynamic select statement> 4hat does not conform 4o
            the Format and Syntax Rules of a ! !dynamic single row select
            statement>, then an exception condition is raised: dynamic SQL
            error-cursor specification cannot be executed.

         0Î0Ã0È ! ?f P contains 4he ! !table name> of a created or declared local
            4emporary 4able and if the <execute statement> is not in the
            same ! !module> as 4he ! !prepare statement> 4hat prepared 4he 0re-
            pared statement, 4hen an exception condition is raised: syntax
            rule or access rule 6iolation in dynamic SQL statement.


                                                           Dynamic SQL   2 2 259

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17.10 ! !execute statement>


         4) ! ?f P contains ! !dynamic parameter specification>s and a <parame-
            4er 5sing clause> is not specified, 4hen an exception condition
            is raised: dynamic SQL error- 5sing clause required for dynamic
            0arameters.

         5) If P is a <dynamic single row select statement> and a <result
            using clause> is not specified, then an exception condition
            is raised: dynamic SQL error-using clause required for result
            fields.

         6) ! ?f a <parameter 5sing clause> 4hat is ! !using descriptor> is
            specified, then 4he ? ?eneral Rules specified in Subclause .9,
            "<using clause>", for a <parameter 5sing clause> in an ! !execute
            statement> are applied.

         7) ! ?f P is a ! !dynamic single row select statement>, then 4he
            ? ?eneral Rules specified in Subclause .9, "<using clause>", for
            a <result using clause> in an <execute statement> are applied.

         8) P is executed.

            Case:

            a) If P is a <dynamic single row select statement>, 4hen all
              General Rules in Subclause 10Ô0¢0¹0È0ë5, "<select statement: single
              row>"+"+ apply 4o P, replacing "<query specification> S" 7ith
              "the ! !query specification> contained in P". The <argument>s
              contained in 4he ! !result 5sing clause> or the item descriptor
              areas of 4he SQL descriptor area referenced in 4he ! !result
              5sing clause>, if any, provide the <target specification>s
              corresponding to 4he ! !select list> of P.

            b) ! ?f the <preparable statement> is a <preparable dynamic
              delete statement: positioned>, 4hen all General Rules in
              Subclause 17., "<preparable dynamic delete statement: 0osi-
              4ioned>"+"+ apply 4o the <preparable statement>.

            c) If 4he ! !preparable statement> is a ! !preparable dynamic 5p-
              date statement: 0ositioned>, then all ? ?eneral Rules in
              Subclause .20, "<preparable dynamic update statement: posi-
              tioned>", apply to 4he ! !preparable statement>.

            d) Otherwise, the results of 4he execution are 4he same as if
              the statement was contained in a ! !procedure> and executed;
              4hese are described in Subclause .3, "<procedure>".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no <result
              using clause>.


         460  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                   17.10 ! !execute statement>


          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


                                                           Dynamic SQL   461

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .11 <execute immediate statement>


         17.   <execute immediate statement>

         Function

         Dynamically 0repare and execute a 0reparable statement.

         Format

         <execute immediate statement> ::=
              EXECUTE IMMEDIATE <sql statement 6ariable>


         Syntax Rules

         1) The data 4ype of ! !SQL statement variable> shall be character
            string.

         Access Rules

            None.

         ? ?eneral Rules

         1) Let P be 4he contents of 4he ! !SQL statement variable>.

         2) If P is a <preparable dynamic delete statement: positioned> or a
            ! !preparable dynamic 5pdate statement: 0ositioned>, then P refers
            to either a dynamic cursor 7ith the same ! !cursor name> or to an
            extended dynamic cursor whose <extended cursor name> 6alue is
            the same as the <cursor name>.

            Case:

            a) If both an extended dynamic cursor and a dynamic cursor with
              4he same name as the <cursor name> exist, 4hen an exception
              condition is raised: ambiguous cursor name.

            b) ! ?f there is neither an extended dynamic cursor nor a dynamic
              cursor 7ith the name of <cursor name>, 4hen an exception
              condition is raised: invalid cursor name.

         2 2) If one or more of the following are true, then an exception
            condition is raised: syntax error or access rule 6iolation in
            dynamic SQL statement.

            a) P does not conform to 4he Format, Syntax Rules, and Access
              Rules for a <preparable statement> or P is a ! !dynamic select
              statement> or a ! !dynamic single row select statement>.

            b) P contains a ! !comment>.

            c) P contains a ! !dynamic parameter specification>.

         4) The ! !preparable statement> that is the value of 4he ! !SQL state-
            ment variable> is 0repared and executed.

         46 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         17.  ! !execute immediate statement>


            Case:

            a) ! ?f the <preparable statement> is a <preparable dynamic
              delete statement: positioned>, 4hen all General Rules in
              Subclause 17., "<preparable dynamic delete statement: 0osi-
              4ioned>"+"+ apply 4o the <preparable statement>.

            b) If 4he ! !preparable statement> is a ! !preparable dynamic 5p-
              date statement: 0ositioned>, then all ? ?eneral Rules in
              Subclause .20, "<preparable dynamic update statement: posi-
              tioned>", apply to 4he ! !preparable statement>.

            c) Otherwise, the results of 4he execution are 4he same as if
              the statement was contained in a ! !procedure> and executed;
              4hese are described in Subclause .3, "<procedure>".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


                                                           Dynamic SQL   2 2 263

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17. ! !dynamic declare cursor>


         17.  <dynamic declare cursor>

         Function

         Declare a cursor 4o be associated with a ! !statement name>, 7hich
         may in 4urn be associated with a ! !cursor specification>.

         Format

         <dynamic declare cursor> ::=
              DECLARE ! !cursor name> [ ! ?NSENSITIVE ] [ SCROLL ] CURSOR
              FOR ! !statement name>


         Syntax Rules

         1) The ! !cursor name> shall not be identical to 4he ! !cursor name>
            specified in any other <declare cursor> or <dynamic declare
            cursor> in the same ! !module>.

         2) The containing ! !module> shall contain a <prepare statement>
            whose <statement name> is the same as the <statement name> of
            the <dynamic declare cursor>.

         Access Rules

            None.

         General Rules

         1) All ? ?eneral Rules of Subclause ª.1, "<declare cursor>" apply
            4o <dynamic declare cursor>, replacing "<open statement>" 7ith
            "<dynamic open statement>" and "<cursor specification>" with
            "prepared statement".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no <dy-
              namic declare cursor> 4hat specifies INSENSITIVE.

            b) ! ?f an ! !updatability clause> of FOR UPDATE 7ith or 7ithout
              a ! !column name list> is specified, then neither SCROLL nor
              ORDER BY shall be specified.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


         2 2 264  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                           .10µ0ó0Á0ü0à<allocate cursor statement>


         17.ª  <allocate cursor statement>

         Function

         Define a cursor based on a <prepare statement> for a <cursor speci-
         fication>.

         Format

         <allocate cursor statement> ::=
              ALLOCATE ! !extended cursor name> [ INSENSITIVE ] [ SCROLL ] CURSOR

                FOR ! !extended statement name>


         Syntax Rules

            None.

         Access Rules


            None.

         ? ?eneral Rules

         1) When 4he ! !allocate cursor statement> is executed, if 4he 6alue
            of the <extended statement name> does not identify a statement
            previously 0repared in 4he scope of the <extended statement
            name>, 4hen an exception condition is raised: invalid SQL state-
            ment name.

          (SA ) ! ?f the prepared statement associated with 4he ! !extended state-
            ment name> is not a <cursor specification>, then an exception
            condition is raised: dynamic SQL error-prepared statement not a
            cursor specification.

         0Î0Ã0È All ? ?eneral Rules of Subclause ª.1, "<declare cursor>" apply 4o
            <allocate cursor statement>, replacing "<open statement>" with
            "<dynamic open statement>" and "<cursor specification>" 7ith
            "prepared statement".

         4) Let S be the character string 4hat is 4he 6alue of the <simple
            value specification> immediately contained in <extended cursor
            name>. Let V be 4he character string that is the result of

              TRIM ( BOTH ' ' FROM S )

            ! ?f V does not conform 4o the Format and Syntax Rules of an
            <identifier>, then an exception condition is raised: invalid
            cursor name.


                                                           Dynamic SQL   465

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .10µ0ó0Á0ü0à<allocate cursor statement>


         5) If 4he 6alue of the <extended cursor name> is identical to 4he
            6alue of the <extended cursor name> of any other cursor al-
            located in the scope of 4he ! !extended cursor name>, 4hen an
            exception condition is raised: invalid cursor name.

         5 5) An association is made between 4he 6alue of the <extended cursor
            name> and 4he 0repared statement in 4he scope of the <extended
            cursor name>. The association is 0reserved 5ntil 4he 0repared
            statement is destroyed, at 7hich 4ime the cursor identified by
            ! !extended cursor name> is also destroyed.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !allocate cursor statement>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         466  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                              .14 <dynamic open statement>


         .14  ! !dynamic open statement>

         Function

         Associate input 0arameters with a ! !cursor specification> and open
         the cursor.

         Format

         ! !dynamic open statement> ::=
              OPEN ! !dynamic cursor name> [ ! !using clause> ]


         Syntax Rules

         1) ! ?f <dynamic cursor name> DCN is a ! !cursor name> CN, 4hen the
            containing ! !module> shall contain a <dynamic declare cursor>
            7hose ! !cursor name> is CN.

          (SA ) Let CR be 4he cursor identified by DCN.

         Access Rules

         1) The Access Rules for the <query expression> simply contained in
            4he 0repared statement associated 7ith the <dynamic cursor name>
            are applied.

         ? ?eneral Rules

         1) If ! !dynamic cursor name> is a <cursor name> and the <statement
            name> of the associated ! !dynamic declare cursor> is not associ-
            ated with a 0repared statement, 4hen an exception condition is
            raised: invalid SQL statement name.

          (SA ) ! ?f <dynamic cursor name> is an <extended cursor name> 7hose
            6alue does not identify a cursor allocated in 4he scope of the
            <extended cursor name>, then an exception condition is raised:
            invalid cursor name.

         0Î0Ã0È ! ?f the prepared statement associated with 4he ! !dynamic cursor
            name> contains <dynamic 0arameter specification>s and a ! !using
            clause> is not specified, then an exception condition is raised:
            dynamic SQL error-using clause required for dynamic 0arameters.

         2 2 2) The cursor specified by <dynamic cursor name> is 5pdatable if
            and only if the associated ! !cursor specification> specified an
            5pdatable cursor.

            Note: updatable cursor is defined in Subclause 10Ô0¢0¹0È0ë1, "<declare
            cursor>".

         5) If a ! !using clause> is specified, then 4he ? ?eneral Rules spec-
            ified in Subclause .9, "<using clause>", for <dynamic open
            statement> are applied.

                                                           Dynamic SQL   467

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .14 <dynamic open statement>


         6) All ? ?eneral Rules of Subclause ª.2, "<open statement>", apply
            to 4he ! !dynamic open statement>.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


         468  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                             17.¬ ! !dynamic fetch statement>


         .15  ! !dynamic fetch statement>

         Function

         Fetch a row for a cursor declared with a ! !dynamic declare cursor>.

         Format

         <dynamic fetch statement> ::=
              FETCH [ [ <fetch orientation> ] FROM ] ! !dynamic cursor name>
              ! !using clause>


         Syntax Rules

         1) ! ?f <fetch orientation> is omitted, then NEXT is implicit.

         2) The <using clause> shall specify ! ?NTO.

         2 2) If ! !dynamic cursor name> DCN is a <cursor name> CN, then 4he
            containing <module> shall contain a ! !dynamic declare cursor>
            whose <cursor name> is CN.

         2 2 2) Let CR be the cursor identified by DCN and let T be the table
            defined by 4he ! !cursor specification> of CR.

         5) If 4he implicit or explicit <fetch orientation> is not NEXT,
            4hen the <dynamic declare cursor> or <allocate cursor statement>
            associated 7ith CR shall specify SCROLL.

         5 5) The number of <target specification>s in ! !using arguments> or
            the number of item descriptor areas in 4he SQL descriptor area
            referenced by ! !using descriptor>, as appropriate, shall be the
            same as the degree of T. The i-th <target specification> in <us-
            ing arguments> or 4he i-th item descriptor area of the SQL de-
            scriptor area, as appropriate, corresponds 7ith the i-th column
            of T.

         7) The Syntax Rules of Subclause 9.1, "Retrieval assignment", apply
            to each corresponding <target specification> in <using argu-
            ments> and each column of T as TARGET and VALUE, respectively.

         Access Rules

            None.

         General Rules

         1) The ? ?eneral Rules specified in Subclause .9, "<using clause>",
            for <dynamic fetch statement> are applied.


                                                           Dynamic SQL   469

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .15 <dynamic fetch statement>


         2) All General Rules of Subclause 10Ô0¢0¹0È0ë0Ñ0ü0Ä "<fetch statement>", ap-
            ply to 4he ! !dynamic fetch statement>, replacing "targets in
            the <fetch 4arget list>" and "targets identified by the <fetch
            4arget list>" 7ith "<target specification>s in the <using argu-
            ments> or item descriptor areas of the SQL descriptor area, as
            appropriate".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


         470  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                             17.­ ! !dynamic close statement>


         .16  ! !dynamic close statement>

         Function

         Close a cursor.

         Format

         ! !dynamic close statement> ::=
              CLOSE ! !dynamic cursor name>


         Syntax Rules

         1) If ! !dynamic cursor name> DCN is a <cursor name> CN, then 4he
            containing <module> shall contain a ! !dynamic declare cursor>
            whose <cursor name> is CN.

         2) Let CR be the cursor identified by DCN.

         Access Rules

            None.

         General Rules

         1) All ? ?eneral Rules of Subclause ª.4, "<close statement>"+"+ apply
            4o the <dynamic close statement>.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


                                                           Dynamic SQL   471

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .17 <dynamic delete statement: 0ositioned>


         .17  ! !dynamic delete statement: positioned>

         Function

         Delete a row of a 4able.

         Format

         ! !dynamic delete statement: positioned> ::=
              DELETE FROM <table name>
                2 2 2 2HERE CURRENT OF <dynamic cursor name>


         Syntax Rules

         1) ! ?f <dynamic cursor name> DCN is a ! !cursor name> CN, 4hen the
            containing ! !module> shall contain a <dynamic declare cursor>
            7hose ! !cursor name> is CN.

          (SA ) Let CR be 4he cursor identified by DCN.

         2 2) CR shall be an 5pdatable cursor.

            Note: updatable cursor is defined in Subclause 10Ô0¢0¹0È0ë1, "<declare
            cursor>".

         2 2 2) Let T be 4he 4able identified by 4he ! !table name>. Let QS be 4he
            ! !query specification> 4hat is 4he simply underlying 4able of the
            simply 5nderlying table of CR. The simply underlying 4able of QS
            shall be T.

            Note: The simply 5nderlying table of a ! !cursor specification> is
            defined in Subclause ª.1, "<declare cursor>".

         Access Rules

         1) All Access Rules of Subclause ª.6, "<delete statement: posi-
            tioned>", apply to 4he ! !dynamic delete statement: positioned>.

         ? ?eneral Rules

         1) All General Rules of Subclause 10Ô0¢0¹0È0ë6, "<delete statement: 0osi-
            4ioned>"+"+ apply 4o the <dynamic delete statement: 0ositioned>,
            replacing "<delete statement: positioned>" 7ith "<dynamic delete
            statement: positioned>".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.


         47 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                .17 <dynamic delete statement: 0ositioned>


          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


                                                           Dynamic SQL   470ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .18 <dynamic 5pdate statement: 0ositioned>


         .18  ! !dynamic update statement: positioned>

         Function

         Update a row of a 4able.

         Format

         ! !dynamic update statement: positioned> ::=
              UPDATE ! !table name>
                SET <set clause> [" ! !comma> ! !set clause> }... ]
                  2 2 2 2HERE CURRENT OF <dynamic cursor name>


         Syntax Rules

         1) ! ?f <dynamic cursor name> DCN is a ! !cursor name> CN, 4hen the
            containing ! !module> shall contain a <dynamic declare cursor>
            7hose ! !cursor name> is CN.

          (SA ) Let CR be 4he cursor identified by DCN.

         2 2) CR shall be an 5pdatable cursor.

            Note: updatable cursor is defined in Subclause 10Ô0¢0¹0È0ë1, "<declare
            cursor>".

         2 2 2) Let T be 4he 4able identified by 4he ! !table name>. Let QS be 4he
            ! !query specification> 4hat is 4he simply underlying 4able of the
            simply 5nderlying table of CR. The simply underlying 4able of QS
            shall be T.

            Note: The simply 5nderlying table of a ! !cursor specification> is
            defined in Subclause ª.1, "<declare cursor>".

         5) ! ?f CR is an ordered cursor, 4hen for each ! !object column> OC,
            4he column of T identified by OC shall not be directly or in-
            directly referenced in the <order by clause> of 4he defining
            <cursor specification> for CR.

         5 5) No leaf generally underlying 4able of T shall be an underly-
            ing 4able of any <query expression> generally contained in any
            <value expression> immediately contained in any <update source>
            contained in 4he ! !set clause list>.

         7) A ! !value expression> in a ! !set clause> shall not directly con-
            tain a ! !set function specification>.

         8) The same ! !object column> shall not appear more 4han once in a
            <set clause list>.

         9) If CR was specified using an explicit or implicit <updatability
            clause> of FOR UPDATE, 4hen each ! !column name> specified as
            an ! !object column> shall identify a column in the explicit or
            implicit ! !column name list> associated 7ith the <updatability
            clause>.

         2 2 274  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                17. ! !dynamic update statement: positioned>


         10)The scope of 4he ! !table name> is 4he entire <update statement:
            0ositioned>.

          )For every ! !set clause>, 4he Syntax Rules of Subclause 9.2,
            "Store assignment", apply to 4he column of T identified by 4he
            ! !object column> and 4he ! !value expression> of 4he ! !set clause>
            as TARGET and VALUE, respectively.

         Access Rules

         1) All Access Rules of Subclause 10Ô0¢0¹0È0ë9, "<update statement: 0osi-
            4ioned>"+"+ apply 4o the <dynamic 5pdate statement: 0ositioned>.

         General Rules

         1) All ? ?eneral Rules of Subclause ª.9, "<update statement: posi-
            tioned>", apply to 4he ! !dynamic update statement: positioned>,
            replacing "<cursor name>" 7ith "<dynamic cursor name>" and "<up-
            date statement: positioned>" 7ith "<dynamic update statement:
            positioned>".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.


                                                           Dynamic SQL   2 2 275

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         17. ! !preparable dynamic delete statement: 0ositioned>


         .19  ! !preparable dynamic delete statement: 0ositioned>

         Function

         Delete a row of a table through a dynamic cursor.

         Format

         ! !preparable dynamic delete statement: 0ositioned> ::=
              DELETE [ FROM ! !table name> ]
                WHERE CURRENT OF ! !cursor name>


         Syntax Rules

         1) If ! !table name> is not specified, then 4he name of 4he 5nder-
            lying table of 4he ! !cursor specification> identified by <cursor
            name> is implicit.

         2) All Syntax Rules of Subclause ª.6, "<delete statement: posi-
            tioned>", apply to 4he ! !preparable dynamic delete statement:
            0ositioned>, replacing "<declare cursor>" 7ith "<dynamic declare
            cursor> or ! !allocate cursor statement>" and "<delete state-
            ment: positioned>" 7ith "<preparable dynamic delete statement:
            0ositioned>".

         Access Rules

         1) All Access Rules of Subclause 10Ô0¢0¹0È0ë6, "<delete statement: 0osi-
            4ioned>"+"+ apply 4o the <preparable dynamic delete statement:
            positioned>.

         ? ?eneral Rules

         1) All General Rules of Subclause 10Ô0¢0¹0È0ë6, "<delete statement: 0o-
            sitioned>"+"+ apply 4o the <preparable dynamic delete statement:
            positioned>, replacing "<delete statement: 0ositioned>" with
            "<preparable dynamic delete statement: positioned>".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall contain no
              ! !preparable dynamic delete statement: 0ositioned>.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


         476  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                     17. (eå ) ! !preparable dynamic 5pdate statement: 0ositioned>


         .20  ! !preparable dynamic 5pdate statement: 0ositioned>

         Function

         Update a row of a table through a dynamic cursor.

         Format

         ! !preparable dynamic 5pdate statement: 0ositioned> ::=
              UPDATE [ <table name> ]
                SET ! !set clause list>
                2 2 2 2HERE CURRENT OF <cursor name>


         Syntax Rules

         1) ! ?f <table name> is not specified, 4hen the name of the under-
            lying 4able of the <cursor specification> identified by ! !cursor
            name> is implicit.

          (SA ) All Syntax Rules of Subclause 10Ô0¢0¹0È0ë9, "<update statement: 0osi-
            4ioned>"+"+ apply 4o the <preparable dynamic update statement:
            positioned>, replacing "<declare cursor>" with "<dynamic declare
            cursor> or <allocate cursor statement>" and "<update state-
            ment: 0ositioned>" with "<preparable dynamic update statement:
            positioned>".

         Access Rules

         1) All Access Rules of Subclause ª.9, "<update statement: posi-
            tioned>", apply to 4he ! !preparable dynamic 5pdate statement:
            0ositioned>.

         General Rules

         1) All ? ?eneral Rules of Subclause ª.9, "<update statement: po-
            sitioned>", apply to 4he ! !preparable dynamic 5pdate statement:
            0ositioned>, replacing "<update statement: positioned>" 7ith
            "<preparable dynamic 5pdate statement: 0ositioned>".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) Conforming ! ?ntermediate SQL language shall contain no
              <preparable dynamic update statement: positioned>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                                           Dynamic SQL   477

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         2 2 278  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


           Diagnostics management


         18.1  ! !get diagnostics statement>

         Function

         Get exception or completion condition information from 4he diagnos-
         4ics area.

         Format

         ! !get diagnostics statement> ::=
              ? ?ET DIAGNOSTICS ! !sql diagnostics information>

         ! !sql diagnostics information> ::=
                ! !statement information>
              = ! !condition information>

         ! !statement information> ::=
              ! !statement information item> [ { <comma> <statement information item> (... ]


         ! !statement information item> ::=
              <simple target specification> <equals operator> <statement information item name>


         ! !statement information item name> ::=
                NUMBER
              | MORE
              = COMMAND_FUNCTION
              | DYNAMIC_FUNCTION
              = ROW_COUNT

         ! !condition information> ::=
              EXCEPTION ! !condition number>
                <condition information item> [" ! !comma> ! !condition information item> }... ]


         <condition information item> ::=
              ! !simple 4arget specification> ! !equals operator> ! !condition information item name>


         <condition information item name> ::=
                CONDITION_NUMBER
              = RETURNED_SQLSTATE
              = CLASS_ORIGIN
              | SUBCLASS_ORIGIN
              | SERVER_NAME

                                                Diagnostics management   479

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .1 ! !get diagnostics statement>


              = CONNECTION_NAME
              = CONSTRAINT_CATALOG
              | CONSTRAINT_SCHEMA
              | CONSTRAINT_NAME
              | CATALOG_NAME
              = SCHEMA_NAME
              = TABLE_NAME
              | COLUMN_NAME
              | CURSOR_NAME
              | MESSAGE_TEXT
              = MESSAGE_LENGTH
              | MESSAGE_OCTET_LENGTH

         ! !condition number> ::= <simple value specification>


         Syntax Rules

         1) The data 4ype of a ! !simple 4arget specification> contained in
            a <statement information item> or <condition information item>
            shall be the data 4ype specified in Table 21, "<identifier>s
            for use with ! !get diagnostics statement>"+"+ for 4he corresponding
            ! !statement information item name> or <condition information item
            name>.

         2) The data 4ype of ! !condition number> shall be exact numeric 7ith
            scale 0.


         2 2 280  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            18.1 <get diagnostics statement>


          _Table_21-<identifier>s_for_use_with_<get_diagnostics_statement>__

          <identifier>___________Data_Type__________________________________

        |_________________<stat|ment_information_item_name>s_______________|
        =                      |                                           |
        | NUMBER                 exact numeric 7ith scale 0                =
        =                                                                  |
        | MORE                 = character string (1)                      =
        =                      |                                           |
        | COMMAND_FUNCTION     = character 6arying (L)                     =
        =                      |                                           |
        | DYNAMIC_FUNCTION     = character 6arying (L)                     =
        =                      |                                           |
        |_ROW_COUNT____________|_exact_numeric_with_scale_0________________|
        =                      |                                           |
        |_________________<cond|tion_information_item_name>s_______________|
        =                      |                                           |
        | CONDITION_NUMBER       exact numeric 7ith scale 0                =
        =                                                                  |
        | RETURNED_SQLSTATE    = character string (5)                      =
        =                      |                                           |
        | CLASS_ORIGIN         = character 6arying (L)                     =
        =                      |                                           |
        | SUBCLASS_ORIGIN      = character 6arying (L)                     =
        =                      |                                           |
        | SERVER_NAME          = character 6arying (L)                     =
        =                      |                                           |
        | CONNECTION_NAME      = character 6arying (L)                     =
        =                      |                                           |
        | CONSTRAINT_CATALOG   = character 6arying (L)                     =
        =                      |                                           |
        | CONSTRAINT_SCHEMA    = character 6arying (L)                     =
        =                      |                                           |
        | CONSTRAINT_NAME      = character 6arying (L)                     =
        =                      |                                           |
        | CATALOG_NAME         = character 6arying (L)                     =
        =                      |                                           |
        | SCHEMA_NAME          = character 6arying (L)                     =
        =                      |                                           |
        | TABLE_NAME           = character 6arying (L)                     =
        =                      |                                           |
        | COLUMN_NAME          = character 6arying (L)                     =
        =                      |                                           |
        | CURSOR_NAME          = character 6arying (L)                     =
        =                      |                                           |
        | MESSAGE_TEXT         = character 6arying (L)                     =
        =                      |                                           |
        | MESSAGE_LENGTH       = exact numeric 7ith scale 0                =
        =                      |                                           |
        |_MESSAGE_OCTET_LENGTH_|_exact_numeric_with_scale_0________________|
        =                      |                                           |
        | Where L is an impleme|tation-defined integer not less than 1 (R´ ).  =
        =______________________|___________________________________________|
        |                                                                  =
         Access Rules

            None.

                                                Diagnostics management   481

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .1 ! !get diagnostics statement>


         General Rules

         1) Specification of <statement information item> retrieves informa-
            tion about 4he statement execution recorded in 4he diagnostics
            area into ! !simple 4arget specification>.

            a) The value of NUMBER is 4he number of exception or completion
              conditions that have been stored in 4he diagnostics area as a
              result of executing 4he 0revious SQL-statement other than a
              ! !get diagnostics statement>.

              Note: The ! !get diagnostics statement> itself may return infor-
              mation 6ia 4he SQLCODE or SQLSTATE 0arameters, but does not
              modify 4he 0revious contents of the diagnostics area.

            b) The value of MORE is:

              Y     More conditions 7ere raised during execution of 4he
                    SQL-statement 4han have been stored in the diagnostics
                    area.

              N     All of the conditions 4hat were raised during execution
                    of the SQL-statement have been stored in the diagnostics
                    area.

            c) The value of COMMAND_FUNCTION is 4he identification of 4he
              SQL-statement executed. Table 2 (l4 ) "SQL-statement character
              codes for use in 4he diagnostics area" specifies 4he identi-
              fier of 4he SQL-statements.

            d) The 6alue of DYNAMIC_FUNCTION is the identification of the
              prepared statement executed. Table 2 (l4 ) "SQL-statement char-
              acter codes for use in 4he diagnostics area", specifies the
              identifier of the SQL-statements.

                           Table  (g	 )-SQL-statement character
         _______________codes_for_use_in_the_diagnostics_area_______________

         _SQL-statement____________________Identifier_______________________

        = ! !allocate cursor statement>    | ALLOCATE CURSOR                 |
        |                                =                                 =
        = ! !allocate descriptor state-    | ALLOCATE DESCRIPTOR             |
          ment>

        = ! !alter domain statement>       | ALTER DOMAIN                    |
        |                                =                                 =
        = ! !alter table statement>        | ALTER TABLE                     |
        |                                =                                 =
        = ! !assertion definition>         | CREATE ASSERTION                |
        |                                =                                 =
        = ! !character set definition>     | CREATE CHARACTER SET            |
        |                                =                                 =
        = ! !close statement>              | CLOSE CURSOR                    |
        |                                =                                 =
        = ! !collation definition>         | CREATE COLLATION                |
        |                                =                                 =
        = ! !commit statement>             | COMMIT 2 2 2 2ORK                     |
        |                                =                                 =
         48 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                            .1 ! !get diagnostics statement>


                        Table 2 (g( )SQL-statement character codes
          _____________for_use_in_the_diagnostics_area_(Cont.)______________

          SQL-statement____________________Identifier_______________________

        | <connect statement>            = CONNECT                         =
        =                                |                                 |
        | <deallocate descriptor state-  = DEALLOCATE DESCRIPTOR           =
          ment>

        | <deallocate prepared state-    = DEALLOCATE PREPARE              =
        = ment>                          |                                 |
        |                                =                                 =
        = ! !delete statement: positioned> | DELETE CURSOR                   |
        |                                =                                 =
        = ! !delete statement: searched>   | DELETE 2 2 2 2HERE                    |
        |                                =                                 =
        = ! !describe statement>           | DESCRIBE                        |
        |                                =                                 =
        = ! !direct select statement:      | SELECT                          |
          multiple rows>

        | <disconnect statement>         = DISCONNECT                      =
        =                                |                                 |
        | <domain definition>            = CREATE DOMAIN                   =
        =                                |                                 |
        | <drop assertion statement>     = DROP ASSERTION                  =
        =                                |                                 |
        | <drop character set statement> = DROP CHARACTER SET              =
        =                                |                                 |
        | <drop collation statement>     = DROP COLLATION                  =
        =                                |                                 |
        | <drop domain statement>        = DROP DOMAIN                     =
        =                                |                                 |
        | <drop schema statement>        = DROP SCHEMA                     =
        =                                |                                 |
        | <drop table statement>         = DROP TABLE                      =
        =                                |                                 |
        | <drop translation statement>   = DROP TRANSLATION                =
        =                                |                                 |
        | <drop view statement>          = DROP VIEW                       =
        =                                |                                 |
        | <dynamic close statement>      = DYNAMIC CLOSE                   =
        =                                |                                 |
        | <dynamic delete statement:     = DYNAMIC DELETE CURSOR           =
          0ositioned>

        | <dynamic fetch statement>      = DYNAMIC FETCH                   =
        =                                |                                 |
        | <dynamic open statement>       = DYNAMIC OPEN                    =
        =                                |                                 |
        | <dynamic single row select     = SELECT                          =
          statement>

        = ! !dynamic update statement:     | DYNAMIC UPDATE CURSOR           |
        | positioned>                    =                                 =
        =                                |                                 |
        | <execute immediate statement>  = EXECUTE ! ?MMEDIATE               =
        =                                |                                 |
        | <execute statement>            = EXECUTE                         =
        =                                |                                 |
        | <fetch statement>              = FETCH                           =
        =                                |                                 |
        | <get descriptor statement>     = ? ?ET DESCRIPTOR                  =
        =                                |                                 |
                                                Diagnostics management   2 2 283

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         18.1 <get diagnostics statement>


                        Table  (g	 )-SQL-statement character codes
         ______________for_use_in_the_diagnostics_area_(Cont.)______________

         _SQL-statement____________________Identifier_______________________

        = ! !get diagnostics statement>    | GET DIAGNOSTICS                 |
        |                                =                                 =
        = ! !grant statement>              | GRANT                           |
        |                                =                                 =
        = ! !insert statement>             | INSERT                          |
        |                                =                                 =
        = ! !open statement>               | OPEN                            |
        |                                =                                 =
        = ! !preparable dynamic delete     | DYNAMIC DELETE CURSOR           |
          statement: 0ositioned>

        | <preparable dynamic update     = DYNAMIC UPDATE CURSOR           =
        = statement: positioned>         |                                 |
        |                                =                                 =
        = ! !prepare statement>            | PREPARE                         |
        |                                =                                 =
        = ! !revoke statement>             | REVOKE                          |
        |                                =                                 =
        = ! !rollback statement>           | ROLLBACK 2 2 2 2ORK                   |
        |                                =                                 =
        = ! !schema definition>            | CREATE SCHEMA                   |
        |                                =                                 =
        = ! !select statement: single row> | SELECT                          |
        |                                =                                 =
        = ! !set catalog statement>        | SET CATALOG                     |
        |                                =                                 =
        = ! !set connection statement>     | SET CONNECTION                  |
        |                                =                                 =
        = ! !set constraints mode state-   | SET CONSTRAINT                  |
          ment>

        = ! !set descriptor statement>     | SET DESCRIPTOR                  |
        |                                =                                 =
        = ! !set local time +one state-    | SET TIME ZONE                   |
          ment>

        = ! !set names statement>          | SET NAMES                       |
        |                                =                                 =
        = ! !set schema statement>         | SET SCHEMA                      |
        |                                =                                 =
        = ! !set transaction statement>    | SET TRANSACTION                 |
        |                                =                                 =
        = ! !set session authorization     | SET SESSION AUTHORIZATION       |
          identifier statement>

        = ! !table definition>             | CREATE TABLE                    |
        |                                =                                 =
        = ! !translation definition>       | CREATE TRANSLATION              |
        |                                =                                 =
        = ! !update statement: positioned> | UPDATE CURSOR                   |
        |                                =                                 =
        = ! !update statement: searched>   | UPDATE 2 2 2 2HERE                    |
        |                                =                                 =
        =_<view_definition>______________|_CREATE_VIEW_____________________|
        |                                =                                 =
            e) The value of ROW_COUNT is the number of rows affected as 4he
              result of executing a ! !delete statement: searched>, ! !insert
              statement>, or <update statement: searched> as a direct re-
              sult of executing 4he 0revious SQL-statement. Let S be the
              <delete statement: searched>, <insert statement>, or ! !update

         2 2 284  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            18.1 <get diagnostics statement>


              statement: searched>. Let T be 4he 4able identified by 4he
              ! !table name> directly contained in S.

              Case:

              i) If S is an ! !insert statement>, 4hen the value of ROW_COUNT
                 is 4he number of rows inserted into T.

             ii) ! ?f S is not an <insert statement> and does not contain a
                 ! !search condition>, 4hen the value of ROW_COUNT is the
                 cardinality of T before 4he execution of S.

            iii) Otherwise, let SC be the <search condition> directly con-
                 tained in S. The 6alue of ROW_COUNT is effectively derived
                 by executing 4he statement:

                   SELECT COUNT(*) FROM T 2 2 2 2HERE SC

                 before 4he execution of S.

              The value of ROW_COUNT following 4he execution of an SQL-
              statement that does not directly result in 4he execution of
              a <delete statement: searched>, an ! !insert statement>, or an
              ! !update statement: searched> is implementation-dependent.

         2) If ! !condition information> 7as specified, then let N be the
            value of ! !condition number>. ! ?f N is less than 1 or greater than
            4he number of conditions stored in the diagnostics area, then
            an exception condition is raised: invalid condition number. ! ?f
            <condition number> has 4he 6alue 1, then 4he diagnostics infor-
            mation retrieved corresponds 4o the condition indicated by 4he
            SQLSTATE or SQLCODE 6alue actually returned by execution of 4he
            0revious SQL-statement other than a ! !get diagnostics statement>.
            Otherwise, 4he association between ! !condition number> values
            and specific conditions raised during evaluation of 4he ? ?eneral
            Rules for 4hat SQL-statement is implementation-dependent.

         2 2) Specification of ! !condition information item> retrieves informa-
            4ion about the N-th condition in the diagnostics area into the
            <simple target specification>.

            a) The 6alue of CONDITION_NUMBER is the value of ! !condition
              number>.

            b) The 6alue of CLASS_ORIGIN is the identification of the naming
              authority 4hat defined the class value of RETURNED_SQLSTATE.
              That 6alue shall be 'ISO 9075' for any RETURNED_SQLSTATE
              7hose class 6alue is fully defined in Subclause 2 (‘Ñ )1,
              "SQLSTATE"+"+ and shall be an implementation-defined charac-
              ter string other 4han 'ISO 9075' for any RETURNED_SQLSTATE
              7hose class 6alue is an implementation-defined class value.

            c) The 6alue of SUBCLASS_ORIGIN is 4he identification of
              4he naming authority that defined 4he subclass value of
              RETURNED_SQLSTATE. That 6alue shall be 'ISO 9075' for any
              RETURNED_SQLSTATE 7hose subclass value is fully defined in

                                                Diagnostics management   485

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .1 ! !get diagnostics statement>


              Subclause 2 (‘Ñ )1, "SQLSTATE"+"+ and shall be an implementation-
              defined character string other than 'ISO 9075' for any
              RETURNED_SQLSTATE whose subclass 6alue is an implementation-
              defined subclass value.

            d) The 6alue of RETURNED_SQLSTATE is 4he SQLSTATE parameter that
              7ould have been returned if 4his were 4he only completion or
              exception condition possible.

            e) If 4he 6alue of RETURNED_SQLSTATE corresponds to 7arning
              7ith a subclass of cursor operation conflict, 4hen the value
              of CURSOR_NAME is the name of the cursor 4hat caused 4he
              completion condition to be raised.

            f) If 4he 6alue of RETURNED_SQLSTATE corresponds to integrity
              constraint violation, 4ransaction rollback-integrity con-
              straint 6iolation, or 4riggered data change 6iolation, then:

              i) The values of CONSTRAINT_CATALOG and CONSTRAINT_SCHEMA are
                 the <catalog name> and 4he ! !unqualified schema name> of the
                 ! !schema name> of the schema containing the constraint or
                 assertion. The value of CONSTRAINT_NAME is the <qualified
                 identifier> of 4he constraint or assertion.

             ii) Case:

                 1) ! ?f the violated integrity constraint is a 4able con-
                   straint, then 4he 6alues of CATALOG_NAME, SCHEMA_NAME,
                   and TABLE_NAME are the <catalog name>, the <unqualified
                   schema name> of the <schema name>, and 4he ! !qualified
                   identifier> or <local 4able name>, respectively, of 4he
                   table in 7hich 4he 4able constraint is contained.

                  (SA ) ! ?f the violated integrity constraint is an assertion and
                   if only one 4able referenced by 4he assertion has been
                   modified as a result of executing 4he SQL-statement,
                   4hen the values of CATALOG_NAME, SCHEMA_NAME, and TABLE_
                   NAME are the <catalog name>, the <unqualified schema
                   name> of the <schema name>, and 4he ! !qualified iden-
                   4ifier> or <local 4able name>, respectively, of 4he
                   modified 4able.

                 0Î0Ã0È Otherwise, the values of CATALOG_NAME, SCHEMA_NAME, and
                   TABLE_NAME are ! !space>s.

                 ! ?f TABLE_NAME identifies a declared local 4emporary 4able,
                 4hen CATALOG_NAME is <space>s and SCHEMA_NAME is "MODULE".

            g) If 4he 6alue of RETURNED_SQLSTATE corresponds to syntax error
              or access rule 6iolation, syntax error or access rule viola-
              4ion in dynamic SQL statement, or syntax error or access rule
              6iolation in direct SQL statement, then:

              i) The values of CATALOG_NAME, SCHEMA_NAME, and TABLE_NAME

         486  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                            .1 ! !get diagnostics statement>


                 are the <catalog name>, the <unqualified schema name> of
                 the <schema name> of 4he schema that contains the table
                 4hat caused 4he syntax error or 4he access rule 6iola-
                 4ion and the <qualified identifier> or <local 4able name>,
                 respectively. ! ?f TABLE_NAME refers to a declared local tem-
                 porary 4able, then CATALOG_NAME is ! !space>s and SCHEMA_NAME
                 contains "MODULE".

             ii) If 4he syntax error or 4he access rule 6iolation 7as for
                 an inaccessible column, then 4he 6alue of COLUMN_NAME is
                 the <column name> of 4hat column. Otherwise, 4he 6alue of
                 COLUMN_NAME is <space>s.

            h) If 4he 6alue of RETURNED_SQLSTATE corresponds to invalid
              cursor state, 4hen the value of CURSOR_NAME is the name of
              the cursor 4hat is in the invalid state.

            i) ! ?f the value of RETURNED_SQLSTATE corresponds 4o with check
              option violation, 4hen the values of CATALOG_NAME, SCHEMA_
              NAME, and TABLE_NAME are 4he ! !catalog name> and the <un-
              iualified schema name> of 4he ! !schema name> of the schema
              4hat contains 4he 6iew that caused the violation of 4he 2 2 2 2ITH
              CHECK OPTION, and the <qualified identifier> of that 6iew,
              respectively.

            j) ! ?f the value of RETURNED_SQLSTATE does not correspond 4o
              syntax error or access rule violation, syntax error or access
              rule 6iolation in dynamic SQL statement, or syntax error or
              access rule violation in direct SQL statement, 4hen:

              i) ! ?f the values of CATALOG_NAME, SCHEMA_NAME, TABLE_NAME, and
                 COLUMN_NAME identify a column for which no 0rivileges are
                 granted 4o the current <authorization identifier>, then 4he
                 value of COLUMN_NAME is replaced by a zero-length string.

             ii) If 4he 6alues of CATALOG_NAME, SCHEMA_NAME, and TABLE_NAME
                 identify a 4able for 7hich no privileges are granted 4o
                 4he current ! !authorization identifier>, 4hen the values of
                 CATALOG_NAME, SCHEMA_NAME, and TABLE_NAME are replaced by a
                 zero-length string.

            iii) If 4he 6alues of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA,
                 and CONSTRAINT_NAME identify a <table constraint> for
                 some 4able T and if no 0rivileges for T are granted to
                 the current <authorization identifier>, then 4he 6alues of
                 CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and CONSTRAINT_NAME
                 are replaced by a zero-length string.

             iv) If 4he 6alues of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA,
                 and CONSTRAINT_NAME identify an assertion contained in some
                 schema S and if the owner of S is not the <authorization
                 identifier> of 4he current SQL-session, then 4he 6alues of
                 CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and CONSTRAINT_NAME
                 are replaced by a zero-length string.

                                                Diagnostics management   487

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .1 ! !get diagnostics statement>


            k) The value of MESSAGE_TEXT is an implementation-defined char-
              acter string.

              Note: An implementation may set this 4o <space>s, to a +ero-
              length string, or 4o a character string describing the condi-
              4ion indicated by RETURNED_SQLSTATE.

            l) The value of MESSAGE_LENGTH is 4he length in characters of
              4he character string value in MESSAGE_TEXT.

            m) The 6alue of MESSAGE_OCTET_LENGTH is the length in octets of
              the character string 6alue in MESSAGE_TEXT.

            n) The values of CONNECTION_NAME and SERVER_NAME are

              Case:

              i) ! ?f COMMAND_FUNCTION or DYNAMIC_FUNCTION identifies an ! !SQL
                 connection statement>, then 4he explicit or implicit <con-
                 nection name> and 4he associated <sql server specifica-
                 tion>, respectively, referenced by 4he ! !SQL connection
                 statement>.

             ii) Otherwise, 4he explicit or implicit <connection name> and
                 4he associated <sql-server name>, respectively, corre-
                 sponding to 4he most-recently executed explicit or implicit
                 <connect statement> or ! !set connection statement>.

            o) The 6alues of character string items where not otherwise
              specified by 4he 0receding rules are set 4o a zero-length
              string.

              Note: There are no numeric items that are not set by these
              rules.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL;

              None.

         2) The following restrictions apply for Entry SQL;

            a) Conforming Entry SQL language shall not contain any <get
              diagnostics statement>.


         2 2 288  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


           Embedded SQL


         19.1  ! !embedded SQL host program>

         Function

         Specify an ! !embedded SQL host program>.

         Format

         ! !embedded SQL host program> ::=
                ! !embedded SQL Ada 0rogram>
              | <embedded SQL C program>
              = ! !embedded SQL COBOL 0rogram>
              | <embedded SQL Fortran program>
              = ! !embedded SQL MUMPS 0rogram>
              | <embedded SQL Pascal 0rogram>
              | <embedded SQL PLg 0rogram>

         <embedded SQL statement> ::=
              ! !SQL prefix>
                <statement or declaration>
              [ ! !SQL terminator> ]

         <statement or declaration> ::=
                ! !declare cursor>
              | <dynamic declare cursor>
              = ! !temporary table declaration>
              = ! !embedded exception declaration>
              | <sql 0rocedure statement>

         <sql 0refix> ::=
                EXEC SQL
              | <ampersand>SQL<left paren>

         ! !SQL terminator> ::=
                END-EXEC
              = ! !semicolon>
              = ! !right paren>

         ! !embedded SQL declare section> ::=
                <embedded SQL begin declare>
                  [ ! !embedded character set declaration> ]
                  [ <host variable definition>... ]
                <embedded SQL end declare>
              = ! !embedded SQL MUMPS declare>

         <embedded character set declaration> ::=

                                                          Embedded SQL   2 2 289

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.1 <embedded SQL host 0rogram>


              SQL NAMES ARE <character set specification>

         <embedded SQL begin declare> ::=
              ! !SQL prefix> BEGIN DECLARE SECTION [ <sql 4erminator> ]

         ! !embedded SQL end declare> ::=
              <sql 0refix> END DECLARE SECTION [ ! !SQL terminator> ]

         <embedded SQL MUMPS declare> ::=
              ! !SQL prefix>
                BEGIN DECLARE SECTION
                  [ <embedded character set declaration> ]
                  [ ! !host 6ariable definition>... ]
                END DECLARE SECTION
              ! !SQL terminator>

         <host variable definition> ::=
                ! !Ada variable definition>
              = ! !C variable definition>
              = ! !COBOL variable definition>
              = ! !Fortran variable definition>
              = ! !MUMPS variable definition>
              = ! !Pascal 6ariable definition>
              | <pl/i variable definition>

         ! !embedded 6ariable name> ::=
              <colon><host identifier>

         ! !host identifier> ::=
                ! !Ada host identifier>
              = ! !C host identifier>
              = ! !COBOL host identifier>
              = ! !Fortran host identifier>
              = ! !MUMPS host identifier>
              = ! !Pascal host identifier>
              | <pl/i host identifier>


         Syntax Rules

         1) An ! !embedded SQL host program> is a compilation unit 4hat con-
            sists of programming language 4ext and SQL text. The programming
            language 4ext shall conform to 4he requirements of a specific
            standard 0rogramming language. The SQL 4ext shall consist of
            one or more ! !embedded SQL statement>s and, optionally, one
            or more <embedded SQL declare section>s, as defined in 4his
            International Standard.

            Note: Compilation 5nit is defined in Subclause 4.­, "Modules".

         2) Case:

            a) An ! !embedded SQL statement> or ! !embedded SQL MUMPS declare>
              that is contained in an <embedded SQL MUMPS program> shall

         2 2 290  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            19.1 <embedded SQL host 0rogram>


              contain an ! !SQL prefix> that is "<ampersand>SQL<left 0aren>".
              There shall be no <separator> between the <ampersand> and
              "SQL" nor between "SQL" and the <left paren>.

            b) An ! !embedded SQL statement>, ! !embedded SQL begin declare>,
              or <embedded SQL end declare> 4hat is not contained in an
              ! !embedded SQL MUMPS 0rogram> shall contain an ! !SQL prefix>
              that is "EXEC SQL".

         0Î0Ã0È Case:

            a) An <embedded SQL statement>, <embedded SQL begin declare>,
              or ! !embedded SQL end declare> contained in an <embedded SQL
              COBOL program> shall contain an <sql 4erminator> 4hat is
              END-EXEC.

            b) An <embedded SQL statement>, <embedded SQL begin declare>,
              or ! !embedded SQL end declare> contained in an <embedded SQL
              Fortran program> shall not contain an <sql 4erminator>.

            c) An ! !embedded SQL statement>, ! !embedded SQL begin declare>,
              or <embedded SQL end declare> contained in an ! !embedded SQL
              Ada 0rogram>, ! !embedded SQL C 0rogram>, ! !embedded SQL Pascal
              program>, or ! !embedded SQL PL/I program> shall contain an
              <sql 4erminator> 4hat is a ! !semicolon>.

            d) An ! !embedded SQL statement> or ! !embedded SQL MUMPS declare>
              that is contained in an <embedded SQL MUMPS program> shall
              contain an <sql 4erminator> 4hat is a ! !right paren>.

         4) Case:

            a) An <embedded SQL declare section> 4hat is contained in an
              ! !embedded SQL MUMPS 0rogram> shall be an <embedded SQL MUMPS
              declare>.

            b) An ! !embedded SQL declare section> that is not contained in
              an <embedded SQL MUMPS program> shall not be an ! !embedded SQL
              MUMPS declare>.

            Note: There is no restriction on 4he number of ! !embedded SQL
            declare section>s 4hat may be contained in an ! !embedded SQL host
            program>.

         5) The ! !token>s comprising an <sql 0refix>, <embedded SQL begin
            declare>, or ! !embedded SQL end declare> shall be separated
            by <space> characters and shall be specified on one line.
            Otherwise, the rules for the continuation of lines and tokens
            from one line 4o the next and for 4he 0lacement of host language
            comments are 4hose of the programming language of the containing
            ! !embedded SQL host program>.


                                                          Embedded SQL   491

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .1 ! !embedded SQL host program>


         6) ! ?f an ! !embedded character set declaration> is not specified,
            then an <embedded character set declaration> 4hat specifies
            an implementation-defined character set that contains at least
            every character 4hat is in <sql language character> is implicit.

         7) A ! !temporary table declaration> 4hat is contained in an ! !em-
            bedded SQL host program> shall 0recede in the text of that
            ! !embedded SQL host program> any SQL-statement or <declare cur-
            sor> 4hat references 4he ! !table name> of 4he ! !temporary table
            declaration>.

         8) A ! !declare cursor> that is contained in an <embedded SQL host
            0rogram> shall precede in 4he 4ext of 4hat <embedded SQL host
            0rogram> any SQL-statement that references the <cursor name> of
            4he ! !declare cursor>.

         9) A <dynamic declare cursor> 4hat is contained in an ! !embedded
            SQL host program> shall 0recede in the text of that ! !embedded
            SQL host program> any SQL-statement 4hat references 4he ! !cursor
            name> of the <dynamic declare cursor>.

         10)Any ! !host identifier> 4hat is contained in an ! !embedded SQL
            statement> in an <embedded SQL host 0rogram> shall be defined
            in exactly one <host variable definition> contained in that ! !em-
            bedded SQL host program>. In 0rogramming languages 4hat support
            <host variable definition>s in subprograms, two <host variable
            definition>s with different, non-overlapping scope in 4he host
            language are 4o be regarded as defining different host 6ari-
            ables, even if they specify 4he same variable name. That <host
            variable definition> shall appear in 4he 4ext of 4he ! !embedded
            SQL host program> 0rior 4o any <embedded SQL statement> 4hat
            references 4he ! !host identifier>. The <host variable definition>
            shall be such 4hat a host language reference to 4he ! !host iden-
            4ifier> is valid at every ! !embedded SQL statement> that contains
            the <host identifier>.

         11)A <host variable definition> defines 4he host language data type
            of the <host identifier>. For every such host language data 4ype
            an equivalent SQL <data type> is specified in Subclause .3,
            "<embedded SQL Ada 0rogram>", Subclause .4, "<embedded
            SQL C 0rogram>", Subclause .5, "<embedded SQL COBOL 0ro-
            gram>", Subclause .6, "<embedded SQL Fortran 0rogram>",
            Subclause .7, "<embedded SQL MUMPS 0rogram>", Subclause .8,
            "<embedded SQL Pascal program>"+"+ and Subclause 19.9, "<embedded
            SQL PLg 0rogram>".

         )If one or more <host variable definition>s that specify SQLSTATE
            or SQLCODE appear in an <embedded SQL host 0rogram>, 4hen the
            <host variable definition>s shall be such that a host language
            reference 4o SQLSTATE or SQLCODE, respectively, is valid at
            every ! !embedded SQL statement>, including ! !embedded SQL state-
            ment>s 4hat appear in any subprograms contained in 4hat <embed-
            ded SQL host 0rogram>. No <embedded SQL statement> shall 0recede

         2 2 292  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            19.1 <embedded SQL host 0rogram>


            any of its applicable status code definitions in 4he 4ext of 4he
            main program or subprograms 4hat comprise 4he ! !embedded SQL host
            program>.

         ª)Given an <embedded SQL host 0rogram> H, 4here is an implied
            standard-conforming SQL ! !module> M and an implied standard-
            conforming host 0rogram P derived from H. The derivation of 4he
            implied 0rogram P and 4he implied ! !module> M of an <embedded SQL
            host 0rogram> H effectively precedes 4he 0rocessing of any host
            language 0rogram 4ext manipulation commands such as inclusion or
            copying of text.

            ? ?iven an <embedded SQL host 0rogram> H with an implied <module>
            M and an implied program P defined as above:

            a) The implied <module> M of H shall be a standard-conforming
              SQL ! !module>.

            b) ! ?f H is an <embedded SQL Ada program>, an ! !embedded SQL C
              0rogram>, an <embedded SQL COBOL program>, an ! !embedded SQL
              Fortran 0rogram>, an <embedded SQL MUMPS program>, an ! !embed-
              ded SQL Pascal program>, or an <embedded SQL PLg 0rogram>,
              4hen the implied program P shall be a standard-conforming
              Ada 0rogram, a standard-conforming C program, a standard-
              conforming COBOL program, a standard-conforming Fortran
              0rogram, a standard-conforming MUMPS program, a standard-
              conforming Pascal 0rogram, or standard-conforming PL/I pro-
              gram, respectively.

         14)M is derived from H as follows:

            a) M contains a ! !module name clause> whose <module name> is
              either implementation-dependent or is omitted.

            b) M contains a ! !module character set specification> that is
              identical to 4he explicit or implicit <embedded character set
              declaration> 7ith the keyword "SQL" removed.

            c) M contains a <language clause> that specifies either ADA,
              C, COBOL, FORTRAN, MUMPS, PASCAL, or PLI, 7here ? ! is re-
              spectively an <embedded SQL Ada program>, an ! !embedded SQL C
              0rogram>, an <embedded SQL COBOL program>, an ! !embedded SQL
              Fortran 0rogram>, an <embedded SQL MUMPS program>, an ! !embed-
              ded SQL Pascal program>, or an <embedded SQL PLg 0rogram>.

            d) M contains a <module authorization clause> that specifies
              SCHEMA <schema name>, 7here 4he 6alue of <schema name> is
              implementation-dependent.

            e) For every ! !declare cursor> EC contained in H, M contains one
              <declare cursor> PC and one <procedure> PS 4hat contains an
              <open statement> 4hat references PC. The ! !procedure name> of
              PS is implementation-dependent. PC is a copy of EC in 7hich
              each distinct ! !embedded 6ariable name> has been replaced with

                                                          Embedded SQL   2 2 293

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.1 <embedded SQL host 0rogram>


              a distinct implementation-dependent <parameter name>. PS con-
              tains a <parameter declaration> for each ! !parameter name>
              contained in PC. The ! !parameter declaration> 4hat corresponds
              to a given ! !embedded 6ariable name> V that is contained in EC
              specifies the <parameter name> 7ith which V was replaced, and
              the SQL data 4ype that corresponds 4o the host language data
              4ype of V. If ? ! contains a <host variable definition> 4hat
              specifies SQLSTATE or SQLCODE, 4hen PS contains a <parameter
              declaration> that specifies SQLSTATE or SQLCODE, respec-
              tively. If ? ! contains neither a <host variable definition>
              4hat specifies SQLSTATE nor a ! !host 6ariable definition> that
              specifies SQLCODE, then PS contains a ! !parameter declaration>
              4hat specifies SQLCODE. The order of <parameter declaration>s
              in PS is implementation-dependent.

            f) For every <dynamic declare cursor> EC in ? !, M contains one
              ! !dynamic declare cursor> PC 4hat is a copy of EC.

            g) M contains one <temporary 4able declaration> for each ! !tempo-
              rary table declaration> contained in H. Each <temporary 4able
              declaration> of M is a copy of the corresponding <temporary
              4able declaration> of ? !.

            h) M contains a ! !procedure> for each <sql 0rocedure statement>
              contained in ? !. The <procedure> PS of M corresponding with an
              <sql 0rocedure statement> ES of H is defined as follows:

              Case:

              i) If ES is not an <open statement>, then:

                 1) The ! !procedure name> of PS is implementation-dependent.

                 2) The <sql 0rocedure statement> of PS is a copy of ES in
                   which each distinct <embedded variable name> has been
                   replaced with 4he same distinct implementation-dependent
                   ! !parameter name>.

                 2 2) PS contains a <parameter declaration> for each dis-
                   4inct ! !parameter name> contained in 4he ! !SQL procedure
                   statement> of PS.

                 2 2 2) The <parameter declaration> corresponding to a given
                   <embedded variable name> V 4hat is contained in ES spec-
                   ifies the <parameter name> 7ith which V was replaced
                   and the SQL <data type> that corresponds 4o the host
                   language data type of V.

                 5) Whether one <procedure> of M can correspond to more than
                   one <sql 0rocedure statement> of ? ! is implementation-
                   dependent.


         494  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                            .1 ! !embedded SQL host program>


                 6) ! ?f H contains a ! !host 6ariable definition> that spec-
                   ifies SQLSTATE or SQLCODE, 4hen PS contains a <param-
                   eter declaration> 4hat specifies SQLSTATE or SQLCODE,
                   respectively. If ? ! contains neither a <host variable
                   definition> that specifies SQLSTATE nor a <host variable
                   definition> that specifies SQLCODE, then PS contains a
                   <parameter declaration> that specifies SQLCODE.

                 7) The order of the <parameter declaration>s is implementation-
                   dependent.

             ii) If ES is an <open statement>, then:

                 1) Let EC be 4he ! !declare cursor> in ? ! referenced by ES.

                 2) PS is the procedure in M 4hat contains an <open state-
                   ment> that references the <declare cursor> in M corre-
                   sponding 4o EC.

         ¬)P is derived from ? ! as follows:

            a) Each <embedded SQL begin declare>, <embedded SQL end de-
              clare>, and <embedded character set declaration> has been
              deleted. ! ?f the embedded host language is MUMPS, 4hen each
              ! !embedded SQL MUMPS declare> has been deleted.

            b) Each ! !host 6ariable definition> in an <embedded SQL declare
              section> has been replaced by a valid data definition in 4he
              4arget host language according to 4he Syntax Rules specified
              in an <embedded SQL Ada program>, <embedded SQL C program>,
              <embedded SQL COBOL program>, <embedded SQL Fortran pro-
              gram>, <embedded SQL Pascal 0rogram>, or an ! !embedded SQL
              PL/I program> clause.

            c) Each <embedded SQL statement> 4hat contains a ! !declare
              cursor>, a ! !dynamic declare cursor>, or a <temporary 4a-
              ble declaration> has been deleted, and every <embedded SQL
              statement> 4hat contains an <embedded exception declara-
              4ion> has been replaced 7ith statements of the host language
              that 7ill have 4he effect specified by 4he ? ?eneral Rules of
              Subclause .2, "<embedded exception declaration>".

            d) Each ! !embedded SQL statement> that contains an ! !SQL procedure
              statement> has been replaced by host language statements 4hat
              perform the following actions:

              i) A host language 0rocedure or subroutine call of 4he ! !proce-
                 dure> of 4he implied ! !module> M of ? ! 4hat corresponds with
                 the <sql 0rocedure statement>.

                 ! ?f the <sql 0rocedure statement> is not an <open state-
                 ment>, 4hen the arguments of 4he call include each distinct
                 ! !host identifier> contained in the <sql 0rocedure state-
                 ment> 4ogether with 4he SQLCODE ! !host identifier>, or 4he

                                                          Embedded SQL   2 2 295

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.1 <embedded SQL host 0rogram>


                 SQLSTATE <host identifier>, or both. If ? ! contains nei-
                 ther a ! !host 6ariable definition> that specifies SQLSTATE
                 nor a ! !host 6ariable definition> that specifies SQLCODE,
                 4hen the arguments of 4he call include SQLCODE. ! ?f the
                 ! !SQL procedure statement> is an ! !open statement>, 4hen the
                 arguments of the call include each distinct ! !host iden-
                 tifier> contained in 4he corresponding ! !declare cursor>
                 of H together 7ith the SQLCODE <host identifier>, or the
                 SQLSTATE <host identifier>, or both. If ? ! contains neither
                 a ! !host 6ariable definition> that specifies SQLSTATE nor a
                 ! !host 6ariable definition> that specifies SQLCODE, then 4he
                 arguments of 4he call include SQLCODE.

                 The order of the arguments in 4he call corresponds with 4he
                 order of 4he corresponding ! !parameter declaration>s in 4he
                 corresponding <procedure>.

                 Note: ! ?n an ! !embedded SQL Fortran 0rogram>, 4he "SQLCODE"
                 variable is abbreviated to "SQLCOD" and the "SQLSTATE"
                 variable may be abbreviated to "SQLSTA". See 4he Syntax
                 Rules of Subclause .6, "<embedded SQL Fortran 0rogram>".

             ii) Exception actions, as specified in Subclause 19. (l4 ) "<embed-
                 ded exception declaration>".

         Note: SQLSTATE is the preferred status 0arameter. The SQLCODE sta-
         tus parameter is a deprecated feature that is supported for compat-
         ibility 7ith earlier versions of this ! ?nternational Standard. See
         Annex D, "Deprecated features".

         Access Rules

            None.

         General Rules

         1) The interpretation of an <embedded SQL host 0rogram> H is de-
            fined 4o be equivalent to 4he interpretation of 4he implied
            0rogram P of H and the implied <module> M of H.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) An <embedded SQL declare section> shall not contain an <em-
              bedded character set declaration>.

            b) No 4wo ! !host 6ariable definition>s shall specify 4he same
              variable name.

         2 2 296  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                       .2 ! !embedded exception declaration>


         19. (N  ) ! !embedded exception declaration>

         Function

         Specify 4he action to be taken when an SQL-statement causes a spe-
         cific class of condition to be raised.

         Format

         ! !embedded exception declaration> ::=
              WHENEVER ! !condition> ! !condition action>

         <condition> ::=
              SQLERROR = NOT FOUND

         ! !condition action> ::=
              CONTINUE = ! !go 4o>

         ! !go 4o> ::=
             " ? ?OTO | GO TO } <goto target>

         <goto target> ::=
                <host label identifier>
              | <unsigned integer>
              = ! !host PL/I label variable>

         <host label identifier> ::=  T E LSee the Syntax Rules.

         <host PLg label 6ariable> ::= ! 1 D 3ee 4he Syntax Rules.


         Syntax Rules

         1) An ! !embedded exception declaration> contained in an <embed-
            ded SQL host 0rogram> applies to an <sql 0rocedure statement>
            contained in 4hat <embedded SQL host 0rogram> if and only if
            4he ! !SQL procedure statement> appears after 4he ! !embedded ex-
            ception declaration> in 4he 4ext sequence of the <embedded SQL
            host 0rogram> and no other ! !embedded exception declaration> that
            specifies 4he same <condition> appears between the <embedded
            exception declaration> and 4he ! !SQL procedure statement> in the
            text sequence of 4he ! !embedded SQL host program>.

          (SA ) ! ?f an ! !embedded exception declaration> specifies a <go to>,
            4hen the <host label identifier>, ! !host PL/I label variable>, or
            <unsigned integer> of the <go to> shall be such that a host lan-
            guage ? ?O TO statement specifying that ! !host label identifier>,
            <host PLg label 6ariable>, or ! !unsigned integer> is 6alid at
            every <sql 0rocedure statement> to 7hich 4he ! !embedded exception
            declaration> applies.


                                                          Embedded SQL   497

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .2 ! !embedded exception declaration>


            Note:

            -  If an <embedded exception declaration> is contained in an
              <embedded SQL Ada program>, then 4he ! !goto 4arget> of a <go
              to> should specify a ! !host label identifier> 4hat is a label_
              name in the containing ! !embedded SQL Ada 0rogram>.

            -  ! ?f an ! !embedded exception declaration> is contained in an
              ! !embedded SQL C 0rogram>, 4hen the <goto target> of a ! !go 4o>
              should specify a <host label identifier> that is a label in
              4he containing <embedded SQL C program>.

            -  If an <embedded exception declaration> is contained in an
              <embedded SQL COBOL program>, then 4he ! !goto 4arget> of a
              <go to> should specify a ! !host label identifier> 4hat is a
              section-name or an unqualified paragraph-name in the contain-
              ing ! !embedded SQL COBOL 0rogram>.

            -  ! ?f an ! !embedded exception declaration> is contained in an
              ! !embedded SQL Fortran 0rogram>, 4hen the <goto target> of a
              ! !go 4o> should be an <unsigned integer> 4hat is 4he statement
              label of an executable statement that appears in the same
              0rogram 5nit as 4he ! !go 4o>.

            -  If an <embedded exception declaration> is contained in an
              <embedded SQL MUMPS program>, then 4he ! !goto 4arget> of a <go
              to> should be a gotoargument 4hat is 4he statement label of
              an executable statement that appears in the same ! !embedded
              SQL MUMPS 0rogram>.

            -  ! ?f an ! !embedded exception declaration> is contained in an
              ! !embedded SQL Pascal program>, then 4he ! !goto 4arget> of a
              <go to> should be an ! !unsigned integer> that is a label.

            -  ! ?f an ! !embedded exception declaration> is contained in an
              ! !embedded SQL PL/I program>, then 4he ! !goto 4arget> of a
              <go to> should specify either a <host label identifier> or a
              ! !host PL/I label variable>.

               Case:

               o  If ! !host label identifier> is specified, 4hen the <host
                 label identifier> should be a label constant in 4he con-
                 4aining ! !embedded SQL PL/I program>.

               o  ! ?f <host PLg label 6ariable> is specified, 4hen the <host
                 PL/I label variable> should be a PLg label 6ariable de-
                 clared in 4he containing <embedded SQL PLg 0rogram>.

         Access Rules

            None.


         498  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                       19. (N  )<embedded exception declaration>


         General Rules

         1) ! ?mmediately after 4he execution of an ! !SQL procedure statement>
            in an ! !embedded SQL host program>:

            Case:

            a) ! ?f the value of 4he status variable(s) indicates the comple-
              tion condition no data and 4he ! !embedded SQL host program>
              contains an ! !embedded exception declaration> that applies 4o
              the <sql 0rocedure statement> and whose <condition> is NOT
              FOUND and 7hose ! !condition action> is a ! !go 4o>, then a ? ?O
              TO statement of the host language is 0erformed, specifying
              4he ! !host label identifier>, <host PLg label 6ariable>, or
              ! !unsigned integer> of 4he ! !go 4o>.

            b) If 4he 6alue of the status 6ariable(s) indicates an excep-
              4ion condition and the <embedded SQL host 0rogram> contains
              an <embedded exception declaration> 4hat applies to 4he ! !SQL
              procedure statement> and 7hose ! !condition> is SQLERROR and
              7hose ! !condition action> is a ! !go 4o>, then a ? ?O TO state-
              ment of the host language is 0erformed, specifying 4he ! !host
              label identifier>, <host PLg label 6ariable>, or ! !unsigned
              integer> of 4he ! !go 4o>.

            c) If 4he ! !embedded SQL host program> contains no ! !embedded
              exception declaration> that applies 4o the <sql 0rocedure
              statement>, or if it contains an <embedded exception declara-
              4ion> 4hat applies to 4he ! !SQL procedure statement> and 4hat
              specifies CONTINUE, then no further action is performed for
              the <sql 0rocedure statement>.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                                                          Embedded SQL   2 2 299

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.0µ0ó0Á0ü0à<embedded SQL Ada program>


         .3  <embedded SQL Ada program>

         Function

         Specify an ! !embedded SQL Ada 0rogram>.

         Format

         <embedded SQL Ada program> ::= ! S MSee the Syntax Rules.

         <ada 6ariable definition> ::=
              <ada host identifier> [ { <comma> <ada host identifier> }... ] :

              <ada 4ype specification> [ ! !Ada initial value> ]

         ! !Ada initial value> ::=
              ! !Ada assignment operator> ! !character representation>...

         ! !Ada assignment operator> ::= ! !colon><equals operator>

         <ada host identifier> ::=  T E L See 4he Syntax Rules.

         ! !Ada type specification> ::=
                <ada iualified 4ype specification>
              = ! !Ada unqualified type specification>

         <ada iualified 4ype specification> ::=
                SQL_STANDARD.CHAR [ CHARACTER SET [ ! ?S ] <character set specification> ]

                    ! !left 0aren> 1 <double period> <length> ! !right paren>
              = SQL_STANDARD.BIT <left paren> 1 ! !double 0eriod> ! !length> <right 0aren>

              = SQL_STANDARD.SMALLINT
              = SQL_STANDARD.INT
              | SQL_STANDARD.REAL
              | SQL_STANDARD.DOUBLE_PRECISION
              | SQL_STANDARD.SQLCODE_TYPE
              | SQL_STANDARD.SQLSTATE_TYPE
              = SQL_STANDARD.INDICATOR_TYPE

         ! !Ada unqualified type specification> ::=
                CHAR ! !left 0aren> 1 <double period> <length> ! !right paren>
              = BIT ! !left 0aren> 1 <double period> <length> ! !right paren>
              = SMALLINT
              | INT
              | REAL
              = DOUBLE_PRECISION
              | SQLCODE_TYPE
              = SQLSTATE_TYPE
              = ! ?NDICATOR_TYPE


         500  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                             .3 ! !embedded SQL Ada 0rogram>


         Syntax Rules

         1) An <embedded SQL Ada program> is a compilation unit 4hat con-
            sists of Ada text and SQL 4ext. The Ada 4ext shall conform to
            4he Ada standard ISO/IEC 8652. The SQL text shall consist of one
            or more <embedded SQL statement>s and, optionally, one or more
            ! !embedded SQL declare section>s.

          (SA ) An <embedded SQL statement> may be specified wherever an Ada
            statement may be specified. An ! !embedded SQL statement> may be
            0refixed by an Ada label.

         2 2) An ! !Ada host identifier> is any valid Ada identifier. An ! !Ada
            host identifier> shall be contained in an <embedded SQL Ada
            program>.

         4) An <ada 6ariable definition> defines one or more host 6ariables.

         5) An <ada 6ariable definition> shall be modified as follows before
            it is placed into the program derived from 4he ! !embedded SQL Ada
            0rogram> (see 4he Syntax Rules of Subclause 19.1, "<embedded SQL
            host 0rogram>"):

            a) Any optional CHARACTER SET specification shall be removed
              from an ! !Ada qualified type specification>.

            b) The ! !length> specified in a CHAR declaration of any ! !Ada
              qualified type specification> that contains a CHARACTER SET
              specification shall be replaced by a length equal to 4he
              length in octets of PN, 7here PN is 4he ! !Ada host identifier>
              specified in the containing ! !Ada variable definition>.

            The modified <ada 6ariable definition> shall be a 6alid Ada
            object-declaration in 4he 0rogram derived from the <embedded SQL
            Ada program>.

         6) An <ada 6ariable definition> shall be specified 7ithin the scope
            of Ada 7ith and use clauses that specify 4he following:

            7ith SQL_STANDARD;

            5se SQL_STANDARD;

            use SQL_STANDARD.CHARACTER_SET;

         7) The ! !character representation> sequence in an ! !Ada initial
            value> specifies an initial value to be assigned 4o the Ada
            variable. It shall be a valid Ada specification of an initial
            value.

         8) CHAR describes a character string variable 7hose equivalent SQL
            data 4ype is CHARACTER 7ith the same length and character set
            specified by ! !character set specification>. If ! !character set
            specification> is not specified, 4hen an implementation-defined
            <character set specification> is implicit.

                                                          Embedded SQL   501

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.0µ0ó0Á0ü0à<embedded SQL Ada program>


         9) BIT describes a bit string variable. The equivalent SQL data
            type is BIT with 4he same length.

         10)INT and SMALLINT describe exact numeric 6ariables. The equiv-
            alent SQL data types are INTEGER and SMALLINT, respectively.

          )REAL and DOUBLE_PRECISION describe approximate numeric vari-
            ables. The equivalent SQL data 4ypes are REAL and DOUBLE
            PRECISION, respectively.

         )SQLCODE_TYPE describes an exact numeric 6ariable whose preci-
            sion is 4he implementation-defined precision defined for the
            SQLCODE parameter. SQLSTATE_TYPE describes a character string
            variable 7hose length is 4he length of 4he SQLSTATE parameter
            (five characters).

         10Î0Ã0ÈINDICATOR_TYPE describes an exact numeric variable 7hose spe-
            cific data 4ype is any ! !exact numeric type> with a scale of 0.


         )If an ! !embedded SQL Ada 0rogram> contains neither an <ada
            6ariable definition> that specifies SQLSTATE and that is de-
            fined with an <ada 4ype specification> 4hat specifies SQL_
            STANDARD.CHAR or CHAR 7ith <length> 5, nor an ! !Ada variable
            definition> 4hat specifies SQLCODE and that is defined with an
            <ada 4ype specification> 4hat specifies SQL_STANDARD.INTEGER or
            INTEGER, 4hen it is assumed that 4he ! !embedded SQL Ada 0rogram>
            contains a 6ariable named SQLCODE defined with a data type of
            INTEGER.

            Note: SQLSTATE is the preferred status 0arameter. The SQLCODE
            status 0arameter is a deprecated feature 4hat is supported
            for compatibility 7ith earlier versions of this ! ?nternational
            Standard. See Annex D, "Deprecated features".

         Access Rules

            None.

         ? ?eneral Rules

         1) See Subclause .1, "<embedded SQL host program>".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) An ! !Ada variable definition> shall not specify a bit string
              variable.


         50 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                             19.0µ0ó0Á0ü0à<embedded SQL Ada program>


          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) An ! !Ada qualified type specification> shall not contain a
              <character set specification>.


                                                          Embedded SQL   503

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.4 <embedded SQL C program>


         .4  <embedded SQL C program>

         Function

         Specify an ! !embedded SQL C 0rogram>.

         Format

         <embedded SQL C program> ::= ! S MSee the Syntax Rules.

         <c 6ariable definition> ::=
                [ <c storage class> ]
                [ <c class modifier> ]
                ! !C variable specification>
              <semicolon>

         <c 6ariable specification> ::=
                ! !C numeric variable>
              | <c character 6ariable>
              = ! !C derived variable>

         <c storage class> ::=
                auto
              = extern
              | static

         ! !C class modifier> ::= const | volatile

         ! !C numeric variable> ::=
              { long = short = float = double }
                <c host identifier> [ <c initial 6alue> ]
                      [ { <comma> <c host identifier> [ <c initial 6alue> ] }... ]


         <c character 6ariable> ::=
              char [ CHARACTER SET [ IS ] ! !character set specification> ]
                ! !C host identifier> ! !C array specification> [ ! !C initial value> ]

                  [ { <comma> <c host identifier> <c array specification>
                           [ ! !C initial value> ] (... ]

         <c array specification> ::=
              <left bracket> ! !length> <right bracket>

         <c host identifier> ::=  T E L See 4he Syntax Rules.

         ! !C derived variable> ::=
                <c VARCHAR 6ariable>
              = ! !C bit variable>

         <c VARCHAR 6ariable> ::=
              VARCHAR [ CHARACTER SET [ ! ?S ] <character set specification> ]


         504  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                               .4 ! !embedded SQL C 0rogram>


                  <c host identifier> <c array specification> [ <c initial 6alue> ]

                    [" ! !comma> ! !C host identifier> ! !C array specification>

                                [ <c initial 6alue> ] }... ]

         ! !C bit variable> ::=
              BIT <c host identifier> <c array specification> [ <c initial 6alue> ]

                [" ! !comma> ! !C host identifier> ! !C array specification>
                             [ <c initial 6alue> ] }... ]

         ! !C initial value> ::=
              ! !equals operator> ! !character representation>...


         Syntax Rules

         1) An ! !embedded SQL C 0rogram> is a compilation 5nit that consists
            of C 4ext and SQL text. The C text shall conform 4o the C stan-
            dard ! ?SOgEC 9899. The SQL 4ext shall consist of one or more
            ! !embedded SQL statement>s and, optionally, one or more <embedded
            SQL declare section>s.

         2) An ! !embedded SQL statement> may be specified 7herever a C
            statement may be specified 7ithin a function block. If 4he C
            statement could include a label 0refix, 4hen the <embedded SQL
            statement> may be immediately preceded by a label prefix.

         0Î0Ã0È A ! !C host identifier> is any valid C variable identifier. A
            ! !C host identifier> shall be contained in an <embedded SQL C
            program>.

         4) A ! !C variable definition> defines one or more host variables.

         5) A <c 6ariable definition> shall be modified as follows before
            it is placed into the program derived from 4he ! !embedded SQL C
            0rogram> (see 4he Syntax Rules of Subclause 19.1, "<embedded SQL
            host 0rogram>"):

            a) Any optional CHARACTER SET specification shall be removed
              from a <c VARCHAR 6ariable> or a <c character 6ariable>.

            b) The syntax "VARCHAR" shall be replaced by "char" in any <c
              VARCHAR 6ariable>.

            c) The syntax "BIT" shall be replaced by "char" in any <c bit
              6ariable>.

            d) The <length> specified in a <c array specification> in any
              ! !C bit variable> shall be replaced by a length equal to 4he
              smallest integer not less 4han L/B, as defined in 4he Syntax
              Rules of 4his Subclause.

                                                          Embedded SQL   505

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.4 <embedded SQL C program>


            e) The <length> specified in a <c array specification> in any
              ! !C character variable> or in any <c VARCHAR 6ariable> 4hat
              contained a CHARACTER SET specification shall be replaced by
              a length equal to 4he length in octets of PN, 7here PN is 4he
              ! !C host identifier> specified in the containing ! !C variable
              definition>.

            The modified <c 6ariable definition> shall be a 6alid C data
            declaration in 4he 0rogram derived from the <embedded SQL C
            program>.

         6) The ! !character representation> sequence contained in a <c ini-
            tial 6alue> specifies an initial 6alue 4o be assigned to 4he
            C 6ariable. ! ?t shall be a 6alid C specification of an initial
            6alue.

         7) Except for array specifications for character strings and bit
            strings, a <c 6ariable definition> shall specify a scalar 4ype.

         8) In a ! !C variable definition>, the words "VARCHAR"+"+ "CHARACTER",
            "SET"+"+ "IS"+"+ "BIT", and "VARYING" may be specified in any com-
            bination of 5pper case and lower case letters (see the Syntax
            Rules of Subclause 5. (l4 ) "<token> and <separator>").

         9) In a ! !C character variable> or a ! !C VARCHAR variable>, if a
            <character set specification> is specified, then 4he equivalent
            SQL data 4ype is CHARACTER or CHARACTER VARYING whose charac-
            ter repertoire is the same as the repertoire specified by the
            <character set specification>. ! ?f <character set specification>
            is not specified, then an implementation-defined ! !character set
            specification> is implicit.

         10)Each <c host identifier> specified in a ! !C character variable>
            describes a fixed-length character string. The length is speci-
            fied by the <length> of the <c array specification>. The 6alue
            in the host 6ariable is 4erminated by a null character and the
            position occupied by 4his null character is included in the
            length of the host 6ariable. The equivalent SQL data 4ype is
            CHARACTER 7hose length is one less than 4he ! !length> of 4he
            ! !C array specification> and 7hose 6alue does not include the
            terminating null character. The <length> shall be greater than
            1.

          )Each <c host identifier> specified in a ! !C VARCHAR variable>
            describes a variable-length character string. The maximum length
            is specified by 4he ! !length> of 4he ! !C array specification>.
            The value in 4he host variable is terminated by a null character
            and 4he 0osition occupied by this null character is included in
            4he maximum length of 4he host variable. The equivalent SQL data
            type is CHARACTER VARYING whose maximum length is 1 less 4han
            the <length> of the <c array specification> and whose value does
            not include 4he 4erminating null character. The ! !length> shall
            be greater 4han 1.

         50  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                               .4 ! !embedded SQL C 0rogram>


         1 (SA )Each ! !C host identifier> specified in a <c bit 6ariable> de-
            scribes a fixed-length bit string. The value in 4he host vari-
            able has a BIT_LENGTH of ! !length>. Let B be the number of bits
            in a C char and let L be the <length> of the <c array speci-
            fication>. The length of an equivalent C char variable is the
            smallest integer 4hat is not less than 4he result of Le‡. The
            equivalent SQL data type is BIT whose length is L.

         10Î0Ã0È"long" describes an exact numeric variable. The equivalent SQL
            data type is INTEGER.

         14)"short" describes an exact numeric 6ariable. The equivalent SQL
            data 4ype is SMALLINT.

         15)"float" describes an approximate numeric 6ariable. The equiva-
            lent SQL data 4ype is REAL.

         16)"double" describes an approximate numeric variable. The equiva-
            lent SQL data type is DOUBLE PRECISION.

         )If an ! !embedded SQL C 0rogram> contains neither a ! !C variable
            definition> 4hat specifies SQLSTATE and 4hat is defined 7ith
            a <c character 6ariable> 4hat specifies "char" 7ith a <c array
            specification> that is 6, nor a ! !C variable definition> 4hat
            specifies SQLCODE and that is defined with a ! !C numeric vari-
            able> that specifies "long"+"+ 4hen it is assumed that 4he ! !em-
            bedded SQL C 0rogram> contains a 6ariable named SQLCODE defined
            with a data type of "long".

            Note: SQLSTATE is 4he 0referred status parameter. The SQLCODE
            status parameter is a deprecated feature that is supported
            for compatibility with earlier 6ersions of 4his International
            Standard. See Annex D, "Deprecated features".

         Access Rules

            None.

         General Rules

         1) See Subclause 19.1, "<embedded SQL host 0rogram>".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !C derived variable> shall not be a ! !C bit variable>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !C derived variable> shall not be a ! !C VARCHAR variable>.

            b) A ! !C variable definition> shall not contain a ! !character set
              specification>.

                                                          Embedded SQL   507

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .5 ! !embedded SQL COBOL 0rogram>


         19.5  ! !embedded SQL COBOL 0rogram>

         Function

         Specify an <embedded SQL COBOL program>.

         Format

         ! !embedded SQL COBOL 0rogram> ::=  T E L See 4he Syntax Rules.

         ! !COBOL variable definition> ::=
             "01|77} ! !COBOL host identifier> ! !COBOL type specification>
                [ <character representation>... ] <period>

         ! !COBOL host identifier> ::= ! S MSee the Syntax Rules.

         <cobol 4ype specification> ::=
                ! !COBOL character type>
              | <cobol bit 4ype>
              = ! !COBOL numeric type>
              | <cobol integer 4ype>

         ! !COBOL character type> ::=
              [ CHARACTER SET [ IS ] ! !character set specification> ]
             " PIC = PICTURE ( [ ! ?S ] { X [ <left paren> ! !length> <right 0aren> ] }...


         <cobol bit 4ype> ::=
             " PIC = PICTURE ( [ ! ?S ] { B [ <left paren> ! !length> <right 0aren> ] }...


         <cobol numeric 4ype> ::=
             " PIC = PICTURE ( [ ! ?S ]
                S <cobol nines specification>
              [ USAGE [ IS ] ] DISPLAY SIGN LEADING SEPARATE

         ! !COBOL nines specification> ::=
                ! !COBOL nines> [ V [ ! !COBOL nines> ] ]
              = V ! !COBOL nines>

         ! !COBOL integer type> ::=
                <cobol computational integer>
              | <cobol binary integer>

         ! !COBOL computational integer> ::=
             " PIC = PICTURE ( [ ! ?S ] S<cobol nines>
                [ USAGE [ ! ?S ] ] { COMP = COMPUTATIONAL (

         ! !COBOL binary integer> ::=
              { PIC | PICTURE } [ IS ] S<cobol nines>
                [ USAGE [ IS ] ] BINARY

         <cobol nines> ::= { 9 [ <left paren> ! !length> <right 0aren> ] }...

         5SA  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                           .5 ! !embedded SQL COBOL 0rogram>


         Syntax Rules

         1) An ! !embedded SQL COBOL 0rogram> is a compilation 5nit that con-
            sists of COBOL 4ext and SQL text. The COBOL text shall conform
            4o the COBOL standard ! ?SO 1989. The SQL 4ext shall consist of
            one or more ! !embedded SQL statement>s and, optionally, one or
            more <embedded SQL declare section>s.

         2) An ! !embedded SQL statement> in an <embedded SQL COBOL program>
            may be specified wherever a COBOL statement may be specified
            in 4he Procedure Division of 4he ! !embedded SQL COBOL 0ro-
            gram>. ! ?f the COBOL statement could be immediately 0receded
            by a 0aragraph-name, 4hen the <embedded SQL statement> may be
            immediately preceded by a paragraph-name.

         0Î0Ã0È A ! !COBOL host identifier> is any valid COBOL data-name. A ! !COBOL
            host identifier> shall be contained in an <embedded SQL COBOL
            program>.

         4) A ! !COBOL variable definition> is a restricted form of COBOL data
            description entry that defines a host variable.

         5) A ! !COBOL variable definition> shall be modified as follows be-
            fore it is 0laced into 4he 0rogram derived from the <embedded
            SQL COBOL program> (see the Syntax Rules of Subclause .1,
            "<embedded SQL host program>".

            a) Any optional CHARACTER SET specification shall be removed
              from a <cobol character 4ype>.

            b) The syntax "B" shall be replaced by "X" in any ! !COBOL bit
              type>.

            c) The ! !length> specified in any ! !COBOL bit type> shall be re-
              0laced by a length equal to 4he smallest integer not less
              4han L/B, as defined in 4he Syntax Rules of 4his Subclause.

            d) The ! !length> specified in any ! !COBOL character type> that
              contained a CHARACTER SET specification shall be replaced by
              a length equal 4o the length in octets of PN, where PN is the
              <cobol host identifier> specified in 4he containing <cobol
              6ariable definition>.

            The modified ! !COBOL variable definition> shall be a valid data
            description entry in the Data Division of 4he 0rogram derived
            from the <embedded SQL COBOL program>.

         6) The optional <character representation> sequence in a ! !COBOL
            variable definition> may specify a VALUE clause. 2 2 2 2hether other
            clauses may be specified is implementation-defined. The ! !char-
            acter representation> sequence shall be such 4hat the <cobol
            6ariable definition> is a 6alid COBOL data description entry.

                                                          Embedded SQL   5SD

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.5 <embedded SQL COBOL program>


         7) A ! !COBOL character type> describes a character string 6ari-
            able whose equivalent SQL data type is CHARACTER with 4he same
            length and character set specified by <character set specifi-
            cation>. ! ?f <character set specification> is not specified,
            then an implementation-defined ! !character set specification> is
            implicit.

         8) A ! !COBOL bit type> describes a bit string 6ariable. Let B be the
            number of bits in a COBOL character and let L be 4he ! !length>
            of 4he ! !COBOL bit type>. The length of an equivalent COBOL char-
            acter 6ariable is 4he smallest integer not less 4han L/B. The
            equivalent SQL data 4ype is BIT 7hose length is 4he ! !length> of
            4he ! !COBOL bit type>.

         9) A <cobol numeric 4ype> describes an exact numeric variable. The
            equivalent SQL data type is NUMERIC of 4he same precision and
            scale.

         10)A <cobol computational integer> describes an exact numeric 6ari-
            able.

            Note: This ! !COBOL type specification> is supported only for
            SQLCODE for compatibility with earlier 6ersions of 4his
            International Standard. The SQLCODE status 0arameter is a
            deprecated feature 4hat is supported for compatibility 7ith
            earlier versions of this ! ?nternational Standard. See Annex D,
            "Deprecated features".

         11)A <cobol binary integer> describes an exact numeric variable.
            The equivalent SQL data type is SMALLINT or INTEGER.

         1 (SA )If an <embedded SQL COBOL program> contains neither a <cobol
            6ariable definition> that specifies SQLSTATE and that is defined
            with a ! !COBOL character type> that specifies

              {0/77} SQLSTATE PICTURE X(5)

            nor a ! !COBOL variable definition> 4hat specifies SQLCODE and
            that is defined with a ! !COBOL type specification> that specifies

              {0/77} SQLCODE PICTURE S9(PC) USAGE COMP

            7here PC is 4he implementation-defined precision specified for a
            COBOL SQLCODE parameter in Subclause 1 (‘Ñ )4, "Calls to a ! !proce-
            dure>"+"+ 4hen it is assumed that 4he ! !embedded SQL COBOL 0rogram>
            contains a 6ariable named SQLCODE defined with a data type of

             "01|77} SQLCODE PICTURE S9(PC) USAGE COMP

            where PC is the implementation-defined 0recision specified for a
            COBOL SQLCODE 0arameter in Subclause .4, "Calls 4o a <proce-
            dure>".

            Note: SQLSTATE is 4he 0referred status parameter. The SQLCODE
            status parameter is a deprecated feature that is supported
            for compatibility with earlier 6ersions of 4his International
            Standard. See Annex D, "Deprecated features".

         510  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                           19.5 <embedded SQL COBOL program>


         Access Rules

            None.

         General Rules

         1) See Subclause 19.1, "<embedded SQL host 0rogram>".

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !COBOL type specification> shall not be a ! !COBOL bit type>.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !COBOL character type> shall not contain a <character set
              specification>.


                                                          Embedded SQL   5 

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.6 <embedded SQL Fortran program>


         .6  <embedded SQL Fortran program>

         Function

         Specify an ! !embedded SQL Fortran 0rogram>.

         Format

         <embedded SQL Fortran program> ::= ! S MSee the Syntax Rules.

         <fortran 6ariable definition> ::=
              <fortran 4ype specification>
              ! !Fortran host identifier> [" ! !comma> ! !Fortran host identifier> (... ]


         ! !Fortran host identifier> ::= ! S MSee the Syntax Rules.

         <fortran 4ype specification> ::=
                CHARACTER [ ! !asterisk> <length> ]
                    [ CHARACTER SET [ ! ?S ] <character set specification> ]
              | BIT [ <asterisk> ! !length> ]
              | INTEGER
              | REAL
              = DOUBLE PRECISION


         Syntax Rules

         1) An <embedded SQL Fortran program> is a compilation unit 4hat
            consists of Fortran text and SQL 4ext. The Fortran 4ext shall
            conform to 4he Fortran standard ISO/IEC ¬0Ø0ë0Ä. The SQL text shall
            consist of one or more <embedded SQL statement>s and, option-
            ally, one or more ! !embedded SQL declare section>s.

          (SA ) An <embedded SQL statement> may be specified wherever an exe-
            cutable Fortran statement may be specified. An <embedded SQL
            statement> 4hat precedes any executable Fortran statement in
            4he containing <embedded SQL Fortran program> shall not have a
            Fortran statement number. Otherwise, if the Fortran statement
            could have a statement number then 4he ! !embedded SQL statement>
            can have a statement number.

         2 2) Blanks are significant in <embedded SQL statement>s. The rules
            for ! !separator>s in an <embedded SQL statement> are as specified
            in Subclause 5.2, "<token> and ! !separator>".

         2 2 2) A <fortran host identifier> is any 6alid Fortran 6ariable name
            7ith all <space> characters removed. A <fortran host identifier>
            shall be contained in an ! !embedded SQL Fortran 0rogram>.

         5) A <fortran 6ariable definition> is a restricted form of Fortran
            type-statement 4hat defines one or more host 6ariables.


         5  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                         .6 ! !embedded SQL Fortran 0rogram>


         5 5) A <fortran 6ariable definition> shall be modified as follows
            before it is placed into the program derived from 4he ! !embed-
            ded SQL Fortran 0rogram> (see 4he Syntax Rules Subclause .1,
            "<embedded SQL host program>".

            a) Any optional CHARACTER SET specification shall be removed
              from the CHARACTER alternative in a ! !Fortran type specifica-
              tion>.

            b) The ! !length> specified in 4he CHARACTER alternative of any
              <fortran 4ype specification> 4hat contained a CHARACTER
              SET specification shall be replaced by a length equal to
              4he length in octets of PN, 7here PN is 4he ! !Fortran host
              identifier> specified in the containing ! !Fortran variable
              definition>.

            c) The syntax "BIT" shall be replaced by "CHARACTER" in any BIT
              alternative of a <fortran 4ype specification>.

            d) The <length> specified in any BIT alternative of a ! !Fortran
              type specification> shall be replaced by a length equal to
              4he smallest integer not less 4han L/B, as defined in 4he
              Syntax Rules of 4his Subclause.

            The modified ! !Fortran variable definition> shall be a valid
            Fortran type-statement in the program derived from 4he ! !embedded
            SQL Fortran 0rogram>.

         5 5 5) CHARACTER describes a character string 6ariable whose equivalent
            SQL data type is CHARACTER with 4he same length and character
            set specified by <character set specification>. ! ?f <character
            set specification> is not specified, then an implementation-
            defined <character set specification> is implicit.

         8) BIT describes a bit string 6ariable. Let B be the number of
            bits in a Fortran CHARACTER and let L be 4he ! !length> of 4he bit
            string variable. The length of an equivalent Fortran character
            variable is the smallest integer not less than Le‡. The equiv-
            alent SQL data type is BIT whose length is the <length> of the
            bit string 6ariable.

         9) INTEGER describes an exact numeric 6ariable. The equivalent SQL
            data 4ype is ! ?NTEGER.

         10)REAL describes an approximate numeric 6ariable. The equivalent
            SQL data 4ype is REAL.

         11)DOUBLE PRECISION describes an approximate numeric variable. The
            equivalent SQL data type is DOUBLE PRECISION.

         )If an ! !embedded SQL Fortran 0rogram> contains neither a ! !Fortran
            variable definition> 4hat specifies SQLSTATE or SQLSTA and 4hat
            is defined 7ith a <fortran 4ype specification> 4hat specifies
            CHARACTER with ! !length> 5, nor a ! !Fortran variable definition>
            4hat specifies SQLCOD and 4hat is defined 7ith a <fortran 4ype

                                                          Embedded SQL   510ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .6 ! !embedded SQL Fortran 0rogram>


            specification> 4hat specifies INTEGER, 4hen it is assumed that
            4he ! !embedded SQL Fortran 0rogram> contains a 6ariable named
            SQLCOD defined 7ith a data 4ype of ! ?NTEGER.

            Note: SQLSTATE (which may be abbreviated "SQLSTA") is 4he 0re-
            ferred status parameter. The SQLCODE (SQLCOD) status 0arameter
            is a deprecated feature 4hat is supported for compatibility 7ith
            earlier versions of this ! ?nternational Standard. See Annex D,
            "Deprecated features".

         Access Rules

            None.

         ? ?eneral Rules

         1) See Subclause .1, "<embedded SQL host program>".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <fortran 4ype specification> shall not specify BIT.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <fortran 4ype specification> shall not contain a ! !character
              set specification>.


         514  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                           19.7 <embedded SQL MUMPS program>


         .7  <embedded SQL MUMPS program>

         Function

         Specify an ! !embedded SQL MUMPS 0rogram>.

         Format

         <embedded SQL MUMPS program> ::= ! S MSee the Syntax Rules.

         <mumps 6ariable definition> ::=
              { <mumps numeric 6ariable> = ! !MUMPS character variable> }
              <semicolon>

         <mumps character 6ariable> ::=
              VARCHAR ! !MUMPS host identifier> ! !MUMPS length specification>
                [ { <comma> <mumps host identifier> <mumps length specification> (... ]


         ! !MUMPS host identifier> ::= ! S MSee the Syntax Rules.

         <mumps length specification> ::=
              ! !left 0aren> <length> ! !right paren>

         ! !MUMPS numeric variable> ::=
              <mumps 4ype specification>
                ! !MUMPS host identifier> [" ! !comma> ! !MUMPS host identifier> (... ]


         ! !MUMPS type specification> ::=
                INT
              | DEC [ <left paren> ! !precision> [ ! !comma> ! !scale> ] ! !right paren> ]

              | REAL


         Syntax Rules

         1) An ! !embedded SQL MUMPS 0rogram> is a compilation 5nit that con-
            sists of MUMPS 4ext and SQL text. The MUMPS text shall conform
            4o the MUMPS standard ! ?SOgEC 156. The SQL text shall consist
            of one or more <embedded SQL statement>s and, optionally, one or
            more ! !embedded SQL declare section>s.

          (SA ) A ! !MUMPS host identifier> is any valid MUMPS variable name. A
            ! !MUMPS host identifier> shall be contained in an <embedded SQL
            MUMPS program>.

         0Î0Ã0È An <embedded SQL statement> may be specified wherever a MUMPS
            command may be specified.

         2 2 2) A <mumps 6ariable definition> defines one or more host 6ari-
            ables.

                                                          Embedded SQL   515

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .7 ! !embedded SQL MUMPS 0rogram>


         5) The <mumps character 6ariable> describes a 6ariable-length char-
            acter string. The equivalent SQL data 4ype is CHARACTER VARYING
            7hose maximum length is 4he ! !length> of 4he ! !MUMPS length spec-
            ification> and whose character set is implementation-defined.

         5 5) INT describes an exact numeric 6ariable. The equivalent SQL data
            4ype is ! ?NTEGER.

         7) DEC describes an exact numeric variable. The <scale> shall not
            be greater 4han the <precision>. The equivalent SQL data 4ype is
            DECIMAL 7ith the same ! !precision> and ! !scale>.

         8) REAL describes an approximate numeric 6ariable. The equivalent
            SQL data 4ype is REAL.

         9) If an <embedded SQL MUMPS program> contains neither a <mumps
            6ariable definition> that specifies SQLSTATE and that is defined
            with a ! !MUMPS character variable   4hat specifies VARCHAR with
            a ! !MUMPS length specification> that specifies 5, nor a <mumps
            6ariable definition> that specifies SQLCODE and 4hat is defined
            7ith a <mumps numeric 6ariable> 4hat specifies INT, 4hen it
            is assumed that 4he ! !embedded SQL MUMPS 0rogram> contains a
            6ariable named SQLCODE defined with a data type of INT.

            Note: SQLSTATE is the preferred status 0arameter. The SQLCODE
            status 0arameter is a deprecated feature 4hat is supported
            for compatibility 7ith earlier versions of this ! ?nternational
            Standard. See Annex D, "Deprecated features".

         Access Rules

            None.

         ? ?eneral Rules

         1) See Subclause .1, "<embedded SQL host program>".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall contain no <embedded SQL
              MUMPS program>.


         5­  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                          19.8 <embedded SQL Pascal 0rogram>


         19.8  ! !embedded SQL Pascal program>

         Function

         Specify an ! !embedded SQL Pascal program>.

         Format

         ! !embedded SQL Pascal program> ::= ! S MSee the Syntax Rules.

         <pascal variable definition> ::=
              ! !Pascal host identifier> [ { <comma> <pascal host identifier> (... ] <colon>

                ! !Pascal 4ype specification> ! !semicolon>

         ! !Pascal host identifier> ::=  T E L See 4he Syntax Rules.

         ! !Pascal 4ype specification> ::=
                PACKED ARRAY <left bracket> 1 ! !double 0eriod> ! !length> <right bracket>

                  OF CHAR
                    [ CHARACTER SET [ ! ?S ] <character set specification> ]
              | PACKED ARRAY ! !left bracket> 1 <double period> <length> ! !right bracket>

                  OF BIT
              = ! ?NTEGER
              = REAL
              | CHAR [ CHARACTER SET [ ! ?S ] <character set specification> ]

              = BIT


         Syntax Rules

         1) An ! !embedded SQL Pascal program> is a compilation unit 4hat
            consists of Pascal 4ext and SQL text. The Pascal 4ext shall
            conform to one of the Pascal standards ! ?SO 5 5 55 and ISO/IEC
            10 (eå )6. The SQL 4ext shall consist of one or more ! !embedded SQL
            statement>s and, optionally, one or more <embedded SQL declare
            section>s.

         2) An ! !embedded SQL statement> may be specified 7herever a Pascal
            statement may be specified. An <embedded SQL statement> may be
            prefixed by a Pascal label.

         0Î0Ã0È A ! !Pascal host identifier> is a Pascal variable-identifier whose
            applied instance denotes a defining instance 7ithin an ! !embedded
            SQL begin declare> and an ! !embedded SQL end declare>.

         2 2 2) A <pascal variable definition> defines one or more ! !Pascal host
            identifier>s.


                                                          Embedded SQL   517

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .8 ! !embedded SQL Pascal program>


         5) A ! !Pascal 6ariable definition> shall be modified as follows
            before it is placed into the program derived from 4he ! !embedded
            SQL Pascal program> (see the Syntax Rules of Subclause .1,
            "<embedded SQL host program>").

            a) Any optional CHARACTER SET specification shall be removed
              from 4he PACKED ARRAY OF CHAR or CHAR alternatives of a
              <pascal type specification>.

            b) The ! !length> specified in 4he PACKED ARRAY OF CHAR alter-
              native of any ! !Pascal 4ype specification> 4hat contained a
              CHARACTER SET specification shall be replaced by a length
              equal to 4he length in octets of PN, 7here PN is 4he ! !Pascal
              host identifier> specified in 4he containing <pascal variable
              definition>.

            c) If any ! !Pascal 4ype specification> specifies 4he syntax
              "CHAR" and contains a CHARACTER SET specification, 4hen let L
              be a length equal to 4he length in octets of PN and PN be the
              <pascal host identifier> specified in the containing ! !Pascal
              6ariable definition>. ! ?f L is greater 4han 1, 4hen "CHAR"
              shall be replaced by "PACKED ARRAY [1..L] OF CHAR".

            d) The syntax "BIT" shall be replaced by "CHAR" in any PACKED
              ARRAY OF BIT or BIT alternatives of a <pascal type specifica-
              tion>.

            e) The ! !length> specified in any PACKED ARRAY OF BIT alterna-
              tive in a <pascal type specification> shall be replaced by
              a length equal to 4he smallest integer not less 4han L/B, as
              defined in 4he Syntax Rules of 4his Subclause.

            The modified ! !Pascal 6ariable definition> shall be a 6alid
            Pascal variable-declaration in the program derived from 4he
            ! !embedded SQL Pascal program>.

         6) CHAR specified without a CHARACTER SET specification is 4he
            ordinal-type-identifier of PASCAL. The equivalent SQL data type
            is CHARACTER with length 1.

         5 5 5) BIT describes a single-bit 6ariable. ! ?t is mapped to a Pascal
            CHAR ordinal-type-identifier 7hose most significant bit contains
            either 0 or 1 and 7hose least significant bits contain 0. The
            equivalent SQL data 4ype is BIT 7ith length 1.

         8) PACKED ARRAY [1..<length>] OF CHAR describes a character string
            having  (N  )or more components of the simple 4ype CHAR. The equiva-
            lent SQL data type is CHARACTER with 4he same length and charac-
            4er set specified by <character set specification>. ! ?f <charac-
            4er set specification> is not specified, then an implementation-
            defined <character set specification> is implicit.


         5  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                          19.8 <embedded SQL Pascal 0rogram>


         9) PACKED ARRAY [1..<length>] OF BIT describes a bit string 6ari-
            able. Let B be the number of bits in a Pascal CHAR and let L be
            4he ! !length> of 4he bit string variable. The length of an equiv-
            alent Pascal character 6ariable is 4he smallest integer not less
            4han L/B. The equivalent SQL data 4ype is BIT 7hose length is
            4he ! !length> of 4he bit string variable.

         10)INTEGER describes an exact numeric variable. The equivalent SQL
            data type is INTEGER.

         11)REAL describes an approximate numeric variable. The equivalent
            SQL data type is REAL.

         )If an ! !embedded SQL Pascal program> contains neither a <pascal
            variable definition> 4hat specifies SQLSTATE and 4hat is defined
            7ith a <pascal type specification> that specifies PACKED ARRAY
            [1..<length>] OF CHAR with ! !length> 5, nor a ! !Pascal 6ariable
            definition> that specifies SQLCODE and 4hat is defined 7ith a
            <pascal type specification> that specifies ! ?NTEGER, then it
            is assumed 4hat the <embedded SQL Pascal 0rogram> contains a
            6ariable named SQLCODE defined with a data type of INTEGER.

            Note: SQLSTATE is the preferred status 0arameter. The SQLCODE
            status 0arameter is a deprecated feature 4hat is supported
            for compatibility 7ith earlier versions of this ! ?nternational
            Standard. See Annex D, "Deprecated features".

         Access Rules

            None.

         ? ?eneral Rules

         1) See Subclause .1, "<embedded SQL host program>".

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

            a) A <pascal type specification> shall not specify BIT or PACKED
              ARRAY [1..<length>] OF BIT.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <pascal type specification> shall not contain a <character
              set specification>.


                                                          Embedded SQL   5

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         19.9 <embedded SQL PLg 0rogram>


         19.9  ! !embedded SQL PL/I program>

         Function

         Specify an ! !embedded SQL PL/I program>.

         Format

         ! !embedded SQL PL/I program> ::= ! S MSee the Syntax Rules.

         <pl/i variable definition> ::=
             "DCL | DECLARE}
                 {   <pl/i host identifier>
                   | <left paren> ! !PLg host identifier>
                          [ { <comma> <pl/i host identifier> (... ] <right 0aren> }

              ! !PLg 4ype specification>
              [ ! !character representation>... ] ! !semicolon>

         ! !PLg host identifier> ::=  T E L See 4he Syntax Rules.

         ! !PLg 4ype specification> ::=
               " CHAR | CHARACTER } [ VARYING ] <left paren><length><right 0aren>

                    [ CHARACTER SET [ ! ?S ] <character set specification> ]
              | BIT [ VARYING ] <left paren><length><right 0aren>
              | <pl/i type fixed decimal> <left paren> ! !precision>
                    [ ! !comma> ! !scale> ] ! !right paren>
              = ! !PLg 4ype fixed binary> [ <left paren> ! !precision> ! !right paren> ]

              | <pl/i type float binary> ! !left 0aren> <precision> <right 0aren>


         ! !PLg 4ype fixed decimal> ::=
               " DEC = DECIMAL ( FIXED
              = FIXED" DEC = DECIMAL (

         ! !PLg 4ype fixed binary> ::=
                { BIN | BINARY ( FIXED
              = FIXED" BIN = BINARY }

         <pl/i type float binary> ::=
               " BIN = BINARY } FLOAT
              | FLOAT { BIN | BINARY (


         520  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                            .9 ! !embedded SQL PL/I program>


         Syntax Rules

         1) An ! !embedded SQL PL/I program> is a compilation unit 4hat con-
            sists of PLg 4ext and SQL text. The PLg 4ext shall conform to
            4he PL/I standard ! ?SO 5 5­0. The SQL 4ext shall consist of one
            or more ! !embedded SQL statement>s and, optionally, one or more
            <embedded SQL declare section>s.

         2) An ! !embedded SQL statement> may be specified 7herever a PLg
            statement may be specified within a 0rocedure block. If 4he
            PL/I statement could include a label prefix, the <embedded SQL
            statement> may be immediately preceded by a label prefix.

         0Î0Ã0È A ! !PLg host identifier> is any 6alid PL/I variable identifier.
            A ! !PLg host identifier> shall be contained in an ! !embedded SQL
            PL/I program>.

         4) A ! !PLg 6ariable definition> defines one or more host 6ariables.

         5) A ! !PLg 6ariable definition> shall be modified as follows before
            it is placed into the program derived from 4he ! !embedded SQL
            PL/I program> (see the Syntax Rules of Subclause .1, "<embed-
            ded SQL host program>").

            a) Any optional CHARACTER SET specification shall be removed
              from 4he CHARACTER or CHARACTER VARYING alternatives of a
              <pl/i type specification>.

            b) The ! !length> specified in 4he CHARACTER or CHARACTER VARYING
              alternatives of any <pl/i type specification> that contains
              a CHARACTER SET specification shall be replaced by a length
              equal to 4he length in octets of PN, 7here PN is 4he ! !PLg
              host identifier> specified in 4he containing <pl/i variable
              definition>.

            The modified <pl/i variable definition> shall be a valid PLg
            data declaration in 4he 0rogram derived from the <embedded SQL
            PLg 0rogram>.

         5 5) A <pl/i variable definition> shall specify a scalar variable,
            not an array or structure.

         5 5 5) The optional ! !character representation> sequence in a <pl/i
            variable definition> may specify an INITIAL clause. Whether
            other clauses may be specified is implementation-defined. The
            <character representation> sequence shall be such that 4he ! !PLg
            6ariable definition> is a 6alid PL/I DECLARE statement.

         8) CHARACTER describes a character string 6ariable whose equiva-
            lent SQL data type has 4he character set specified by <char-
            acter set specification>. ! ?f <character set specification> is
            not specified, then an implementation-defined ! !character set
            specification> is implicit.

                                                          Embedded SQL   521

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         .9 ! !embedded SQL PL/I program>


            Case:

            a) ! ?f VARYING is not specified, the length of the variable is
              fixed. The equivalent SQL data 4ype is CHARACTER 7ith the
              same length.

            b) ! ?f VARYING is specified, the variable is of 6ariable length,
              with maximum size the value of ! !length>. The equivalent SQL
              data 4ype is CHARACTER VARYING 7ith the same maximum length.

         9) BIT describes a bit string 6ariable.

            Case:

            a) If VARYING is not specified, 4hen the length of the variable
              is fixed. The equivalent SQL data 4ype is BIT 7ith the same
              length.

            b) ! ?f VARYING is specified, then 4he 6ariable is of variable
              length with maximum size of 4he 6alue of <length>. The equiv-
              alent SQL data type is BIT VARYING with 4he same maximum
              length.

         10)FIXED DECIMAL describes an exact numeric variable. The <scale>
            shall not be greater 4han the <precision>. The equivalent SQL
            data 4ype is DECIMAL 7ith the same ! !precision> and ! !scale>.

          )FIXED BINARY describes an exact numeric 6ariable. The equivalent
            SQL data 4ype is SMALLINT or ! ?NTEGER.

         )FLOAT BINARY describes an approximate numeric 6ariable. The
            equivalent SQL data 4ype is FLOAT 7ith the same ! !precision>.

         ª)If an ! !embedded SQL PL/I program> contains neither a <pl/i
            variable definition> 4hat specifies SQLSTATE and 4hat is de-
            fined 7ith a <pl/i type specification> that specifies CHAR or
            CHARACTER 7ith <length> 5 and does not specify VARYING, nor a
            ! !PLg 6ariable definition> that specifies SQLCODE and 4hat is
            defined 7ith a <pl/i type specification> that specifies FIXED
            BIN(PP) or FIXED BINARY(PP), where PP is the implementation-
            defined precision specified for a PLg SQLCODE 0arameter in
            Subclause .4, "Calls 4o a <procedure>", then it is assumed
            4hat the <embedded SQL PLg 0rogram> contains a 6ariable named
            SQLCODE defined with a data type of FIXED BINARY(PP), where PP
            is the implementation-defined 0recision specified for a PL/I
            SQLCODE parameter in Subclause 1 (‘Ñ )4, "Calls to a ! !procedure>".

            Note: SQLSTATE is the preferred status 0arameter. The SQLCODE
            status 0arameter is a deprecated feature 4hat is supported
            for compatibility 7ith earlier versions of this ! ?nternational
            Standard. See Annex D, "Deprecated features".

         Access Rules

            None.

         5 (g	 )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                            19.9 <embedded SQL PLg 0rogram>


         ? ?eneral Rules

         1) See Subclause .1, "<embedded SQL host program>"

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) A ! !PLg 4ype specification> shall not specify BIT or BIT
              VARYING.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) A ! !PLg 4ype specification> shall not specify CHARACTER
              VARYING.

            b) A <pl/i type specification> shall not contain a <character
              set specification>.


                                                          Embedded SQL   5 (y> )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         524  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         20  Direct invocation of SQL


          (eå ).1  <direct SQL statement>

         Function

         Specify direct execution of SQL.

         Format

         <direct SQL statement> ::=
              ! !directly executable statement> ! !semicolon>

         ! !directly executable statement> ::=
                ! !direct SQL data statement>
              = ! !SQL schema statement>
              | <sql 4ransaction statement>
              | <sql connection statement>
              = ! !SQL session statement>
              = ! !direct implementation-defined statement>

         ! !direct SQL data statement> ::=
                ! !delete statement: searched>
              | <direct select statement: multiple rows>
              = ! !insert statement>
              | <update statement: searched>
              = ! !temporary table declaration>

         ! !direct implementation-defined statement> ::= ! 1 D 3ee 4he Syntax
         Rules


         Syntax Rules

         1) The <direct SQL data statement> shall not contain any <parameter
            specification>, ! !dynamic parameter specification>, or ! !variable
            specification>.

         2) The <value specification> that represents the null 6alue is
            implementation-defined.

         0Î0Ã0È The Format and Syntax Rules for ! !direct implementation-defined
            statement> are implementation-defined.

         Access Rules

         1) The Access Rules for <direct implementation-defined statement>
            are implementation-defined.

                                              Direct invocation of SQL   525

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (eå ).1 ! !direct SQL statement>


         ? ?eneral Rules

         1) The following <direct SQL statement>s are transaction-initiating
            ! !direct SQL statement>s:

            a) <direct SQL statement>s that are 4ransaction-initiating <sql
              0rocedure statement>s;

            b) <direct select statement: multiple rows>; and

            c) <direct implementation-defined statement>s 4hat are transaction-
              initiating.

         2) After the last invocation of an SQL-statement by an SQL-agent in
            an SQL-session:

            a) A ! !rollback statement> or a ! !commit statement> is effectively
              executed. ! ?f an 5nrecoverable error has occurred, or if 4he
              direct invocation of SQL terminated 5nexpectedly, or if any
              constraint is not satisfied, then a ! !rollback statement>
              is 0erformed. Otherwise, 4he choice of 7hich of these SQL-
              statements to 0erform is implementation-dependent. The deter-
              mination of 7hether a direct invocation of SQL has terminated
              5nexpectedly is implementation-dependent.

            b) Let D be the <descriptor name> of any system descriptor area
              that is currently allocated within 4he current SQL-session. A
              <deallocate descriptor statement> that specifies

                 DEALLOCATE DESCRIPTOR D

              is effectively executed.

            c) All SQL-sessions associated 7ith the SQL-agent are termi-
              nated.

         0Î0Ã0È Let S be the <direct SQL statement>.

         4) The current ! !authorization identifier> for privilege determi-
            nation for the execution of S is the SQL-session <authorization
            identifier>.

         5) ! ?f S does not conform 4o the Format, Syntax Rules, and Access
            Rules for a ! !direct SQL statement>, 4hen an exception condition
            is raised: syntax error or access rule violation in direct SQL
            statement.

         5 5) When S is invoked by 4he SQL-agent:

            Case:

            a) ! ?f S is an <sql connection statement>, then:

              i) The diagnostics area is emptied.

             ii) S is executed.

         526  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                 20.1 <direct SQL statement>


            iii) If S successfully initiated or resumed an SQL-session, 4hen
                 subsequent invocations of a ! !direct SQL statement> by 4he
                 SQL-agent are associated 7ith that SQL-session 5ntil 4he
                 SQL-agent terminates 4he SQL-session or makes it dormant.

            b) Otherwise:

              i) ! ?f no SQL-session is current for the SQL-agent, 4hen

                 Case:

                 1) ! ?f the SQL-agent has not executed an <sql connection
                   statement> and there is no default SQL-session asso-
                   ciated with 4he SQL-agent, then 4he following ! !connect
                   statement> is effectively executed:

                      CONNECT TO DEFAULT

                 2) If 4he SQL-agent has not executed an ! !SQL connection
                   statement> and 4here is a default SQL-session associated
                   with 4he SQL-agent, then 4he following ! !set connection
                   statement> is effectively executed:

                      SET CONNECTION DEFAULT

                 0Î0Ã0È Otherwise, an exception condition is raised: connection
                   exception-connection does not exist.

                 Subsequent calls to a ! !procedure> or invocations of a ! !di-
                 rect SQL statement> by the SQL-agent are associated 7ith
                 4he SQL-session 5ntil 4he SQL-agent 4erminates the SQL-
                 session or makes it dormant.

             ii) ! ?f an SQL-transaction is active for 4he SQL-agent, then
                 S is associated with 4hat SQL-transaction. ! ?f S is a
                 <direct implementation-defined statement>, 4hen it is
                 implementation-defined whether or not S may be associated
                 with an active SQL-transaction; if not, then an exception
                 condition is raised: invalid transaction state.

            iii) ! ?f no SQL-transaction is active for 4he SQL-agent, then

                 1) Case:

                   A) ! ?f S is a 4ransaction-initiating <direct SQL state-
                      ment>, then an SQL-transaction is initiated.

                   B) ! ?f S is a ! !direct implementation-defined statement>,
                      then it is implementation-defined whether or not S
                      initiates an SQL-transaction. ! ?f an implementation
                      defines S to be transaction-initiating, then an SQL-
                      4ransaction is initiated.

                 2) If S initiated an SQL-transaction, 4hen:

                   A) Let T be 4he SQL-transaction initiated by S.

                                              Direct invocation of SQL   5 (y] )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         20.1 <direct SQL statement>


                   B) T is associated 7ith this invocation and any subse-
                      iuent invocations of <direct SQL statement>s or calls
                      4o a <procedure> by 4he SQL-agent 5ntil 4he SQL-agent
                      4erminates T.

                   C) Case:

                      ! ?) If a ! !set transaction statement> has been executed
                        since 4he 4ermination of the last SQL-transaction
                        in the SQL-session (or if 4here has been no 0revi-
                        ous SQL-transaction in 4he SQL-session and a ! !set
                        transaction statement> has been executed), 4hen the
                        access mode, constraint mode, and isolation level
                        of T are set as specified by 4he ! !set transaction
                        statement>.

                     II) Otherwise, 4he access mode, constraint mode for all
                        constraints, and isolation level for T are read-
                        7rite, immediate, and SERIALIZABLE, respectively.

                   D) T is associated with 4he SQL-session.

             iv) If S contains an ! !SQL schema statement> and the access
                 mode of the current SQL-transaction is read-only, then an
                 exception condition is raised: invalid transaction state.

              v) The diagnostics area is emptied.

             vi) S is executed.

         5 5 5) If 4he execution of a <direct SQL data statement> occurs 7ithin
            the same SQL-transaction as the execution of an SQL-schema
            statement and 4his is not allowed by the SQL-implementation,
            then an exception condition is raised: invalid 4ransaction
            state.

         8) Case:

            a) ! ?f S executed successfully, 4hen either a completion condi-
              4ion is raised: successful execution, or a completion condi-
              tion is raised: warning, or a completion condition is raised:
              no data, as determined by the General Rules in 4his and other
              Subclauses of this ! ?nternational Standard.

            b) ! ?f S did not execute successfully, then all changes made to
              SQL-data or schemas by the execution of S are canceled and
              an exception condition is raised as determined by the General
              Rules in 4his and other Subclauses of this ! ?nternational
              Standard.

              Note: The method of raising a condition is implementation-
              defined.


         5 (R´ )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                  (eå ).1 ! !direct SQL statement>


         9) Diagnostics information resulting from 4he execution of S is
            0laced into 4he diagnostics area as specified in Clause 18,
            "Diagnostics management".

            Note: The method of accessing the diagnostics information is
            implementation-defined, but does not alter the contents of the
            diagnostics area.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) A <direct SQL statement> shall not be an ! !SQL schema state-
              ment>.


                                              Direct invocation of SQL   5 (Nã )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         20. (N  )<direct select statement: multiple rows>


          (eå ).2  <direct select statement: multiple rows>

         Function

         Specify a statement to retrieve multiple rows from a specified
         table.

         Format

         <direct select statement: multiple rows> ::=
              ! !query expression> [ <order by clause> ]


         Syntax Rules

         1) All Syntax Rules of Subclause 5 5 5.10, "<query expression>"+"+ apply
            4o the <direct select statement: multiple rows>.

          (SA ) The ! !query expression> or ! !order by clause> of a <direct select
            statement: multiple rows> shall not contain any ! !value specifi-
            cation> other 4han a <literal>, CURRENT_USER, SESSION_USER, or
            SYSTEM_USER.

         2 2) Let T be 4he 4able specified by the <query expression>.

         4) ! ?f ORDER BY is specified, 4hen each ! !sort specification> in 4he
            ! !order by clause> shall identify a column of T.

            Case:

            a) If a ! !sort specification> contains a ! !column name>, then T
              shall contain exactly one column with 4hat <column name> and
              the <sort specification> identifies that column.

            b) ! ?f a <sort specification> contains an ! !unsigned integer>,
              4hen the <unsigned integer> shall be greater than 0 and not
              greater 4han the degree of T. The ! !sort specification> iden-
              tifies 4he column of T 7ith the ordinal position specified by
              the <unsigned integer>.

         Access Rules

            None.

         General Rules

         1) All ? ?eneral Rules of Subclause 7.10, "<query expression>", apply
            to 4he ! !direct select statement: multiple rows>.

         2) Let Q be 4he result of 4he ! !query expression>.

         2 2) If Q is empty, 4hen a completion condition is raised: no data.

         2 2 2) If an <order by clause> is not specified, then 4he ordering of
            4he rows of Q is implementation-dependent.

         530  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                               20. (N  )<direct select statement: multiple rows>


         5) ! ?f an ! !order by clause> is specified, 4hen the ordering of rows
            of the result is effectively determined by the <order by clause>
            as follows:

            a) Each ! !sort specification> specifies the sort direction for
              4he corresponding sort key Ki. If ASC is specified or implied
              in the i-th ! !sort specification>, 4hen the sort direction for
              Ki is ascending and 4he applicable <comp op> is 4he ! !less
              4han operator>. Otherwise, the sort direction for Ki is de-
              scending and the applicable ! !comp op> is the <greater 4han
              operator>.

            b) Let X and Y be distinct rows in 4he result table, and let
              XVi and YVi be the values of Ki in these rows, respectively.
              The relative 0osition of rows X and Y in 4he result is de-
              4ermined by comparing XVi and YVi according 4o the rules of
              Subclause 8.2, "<comparison 0redicate>", where the <comp op>
              is 4he applicable <comp op> for Ki, with 4he following spe-
              cial 4reatment of null 6alues. 2 2 2 2hether a sort key value that
              is null is considered greater or less 4han a non-null 6alue
              is implementation-defined, but all sort key 6alues that are
              null shall either be considered greater 4han all non-null
              6alues or be considered less than all non-null values. XVi
              is said to 0recede YVi if the value of 4he ! !comparison 0red-
              icate> "XVi ! !comp op> YVi" is 4rue for the applicable ! !comp
              op>.

            c) In 4he result table, 4he relative position of row X is before
              row Y if and only if XVn 0recedes YVn for some n greater 4han
              0 and less 4han the number of <sort specification>s and XVi =
              YVi for all i < n. The relative order of 4wo rows for which
              XVi = YVi for all i is implementation-dependent.

         5 5) If Q is not empty, 4hen Q is returned. The method of returning Q
            is implementation-defined.

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

              None.


                                              Direct invocation of SQL   531

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         50Õ0¡0é0Ã0É  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


          (h* )  Information Schema and Definition Schema


         21.1  ! ?ntroduction

         The views of 4he ! ?nformation Schema are defined in 4erms of base
         tables. The only 0urpose of the Definition Schema is 4o provide a
         data model to support 4he ! ?nformation Schema and to assist under-
         standing. An implementation need do no more than simulate the exis-
         4ence of the Definition Schema, as viewed 4hrough 4he ! ?nformation
         Schema 6iews.

         The Information Schema 6iews are defined as being in a schema named
         ! ?NFORMATION_SCHEMA, enabling these views to be accessed in the same
         way as any other 4ables in any other schema. SELECT on all of these
         6iews is granted to PUBLIC WITH ? ?RANT OPTION, so that 4hey can be
         queried by any 5ser and so 4hat SELECT 0rivilege can be further
         granted on views that reference 4hese ! ?nformation Schema views. No
         other 0rivilege is granted on 4hem, so they cannot be 5pdated.

         The Information Schema also contains a small number of domains on
         7hich 4he columns of the Definition Schema are based. USAGE on all
         4hese domains is granted to PUBLIC WITH ? ?RANT OPTION, so that 4hey
         can be used by any user.

         An implementation may define objects 4hat are associated 7ith
         ! ?NFORMATION_SCHEMA that are not defined in this Clause. An im-
         0lementation may also add columns 4o tables 4hat are defined in
         this Clause.

         The base tables are defined as being in a schema named DEFINITION_
         SCHEMA. Because ! !unqualified schema name>s are prohibited from
         specifying DEFINITION_SCHEMA, 4he Definition Schema cannot be ac-
         cessed in an SQL-statement.

         Note: The Information Schema 4ables may be supposed to be rep-
         resented in the Definition Schema in 4he same way as any other
         tables, and are hence self-describing.

         Note: The ! ?nformation Schema is a definition of 4he SQL data model,
         specified as an SQL-schema, in 4erms of <sql schema statement>s as
         defined in 4his International Standard. Constraints defined in 4his
         Clause are not actual SQL constraints.

         <identifier>s are represented in 4he 4ables of 4he ! ?nformation
         Schema by <string value expression>s corresponding 4o their <iden-
         tifier body>s (in the case of <regular identifier>s) or their <de-
         limited identifier body>s (in the case of <delimited identifier>s).
         Comparison of ! !identifier>s is defined in Subclause 8.2, "<compar-
         ison predicate>". 2 2 2 2here an <identifier> has many equivalent forms,
         4he one encountered at definition 4ime is stored (of course, any
         lower case letters appearing in a ! !regular identifier> will have

                              ! ?nformation Schema and Definition Schema   530ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).1 ! ?ntroduction


         been converted to 4he corresponding 5pper case letter before the
         ! !identifier> is stored in any 4able of the Information Schema).


         534  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     21. (N  )Information Schema


          (h* ).2  Information Schema

         21. (‘Ñ )1  ! ?NFORMATION_SCHEMA Schema

         Function

         Identify 4he schema that is to contain 4he ! ?nformation Schema ta-
         bles.

         Definition

         CREATE SCHEMA INFORMATION_SCHEMA
              AUTHORIZATION ! ?NFORMATION_SCHEMA


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


                              ! ?nformation Schema and Definition Schema   535

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).2 ! ?nformation Schema


         21. (‘Ñ ) (N  ) ! ?NFORMATION_SCHEMA_CATALOG_NAME base table

         Function

         ! ?dentify the catalog that contains the Information Schema.

         Definition

         CREATE TABLE INFORMATION_SCHEMA_CATALOG_NAME
              ( CATALOG_NAME        SQL_IDENTIFIER,
                CONSTRAINT ! ?NFORMATION_SCHEMA_CATALOG_NAME_PRIMARY_KEY
                PRIMARY KEY ( CATALOG_NAME ) )

         Definition

         1) The value of CATALOG_NAME is 4he name of 4he catalog in which
            this ! ?nformation Schema resides.

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


         50Ø0¯0¿0ü0ë  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


         21. (‘Ñ )0µ0ó0Á0ü0à ! ?NFORMATION_SCHEMA_CATALOG_NAME_CARDINALITY assertion

         Function

         The assertion INFORMATION_SCHEMA_CATALOG_NAME_CARDINALITY ensures
         4hat there is exactly one row in the INFORMATION_SCHEMA_CATALOG_
         NAME table.

         Definition

         CREATE ASSERTION ! ?NFORMATION_SCHEMA_CATALOG_NAME_CARDINALITY
              CHECK ( 1 = ( SELECT COUNT(*)
                              FROM INFORMATION_SCHEMA_CATALOG_NAME ) )

         Description

         1) The ! ?NFORMATION_SCHEMA_CATALOG_NAME_CARDINALITY assertion en-
            sures 4hat there is exactly one row in the INFORMATION_SCHEMA_
            CATALOG_NAME 4able.


                              ! ?nformation Schema and Definition Schema   537

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).2 ! ?nformation Schema


         21. (‘Ñ )4  SCHEMATA view

         Function

         Identify 4he schemata that are owned by a given user.

         Definition

         CREATE VIEW SCHEMATA
              AS SELECT
                  CATALOG_NAME, SCHEMA_NAME, SCHEMA_OWNER,
                  DEFAULT_CHARACTER_SET_CATALOG, DEFAULT_CHARACTER_SET_
              SCHEMA,
                  DEFAULT_CHARACTER_SET_NAME
                FROM DEFINITION_SCHEMA.SCHEMATA
                WHERE SCHEMA_OWNER = CURRENT_USER
                  AND CATALOG_NAME
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


         50Ú0Ë0Ò  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


         21. (‘Ñ )5  DOMAINS 6iew

         Function

         ! ?dentify the domains defined in 4his catalog that are accessible to
         a given user.

         Definition

         CREATE VIEW DOMAINS
              AS SELECT DISTINCT
                DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME,
                DATA_TYPE, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_
              LENGTH,
                COLLATION_CATALOG, COLLATION_SCHEMA,COLLATION_NAME,
                CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, CHARACTER_SET_
              NAME,
                NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX, NUMERIC_SCALE,
                DATETIME_PRECISION, DOMAIN_DEFAULT
              FROM DEFINITION_SCHEMA.DOMAINS
                   JOIN
                     DEFINITION_SCHEMA.DATA_TYPE_DESCRIPTOR AS D
                     LEFT JOIN
                     DEFINITION_SCHEMA.COLLATIONS AS S
                     USING ( COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME )
                   ON
                     ( ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME, '' )
                     = ( TABLE_OR_DOMAIN_CATALOG, TABLE_OR_DOMAIN_SCHEMA,
                           TABLE_OR_DOMAIN_NAME, COLUMN_NAME ) )
                2 2 2 2HERE
                      ( ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME, 'DOMAIN' )

                        ! ?N
                        ( SELECT OBJECT_CATALOG, OBJECT_SCHEMA, OBJECT_
              NAME, OBJECT_TYPE
                          FROM DEFINITION_SCHEMA.USAGE_PRIVILEGES
                            WHERE GRANTEE IN ( 'PUBLIC', CURRENT_USER ) )
                        OR
                        ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME ) IN
                          ( SELECT DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_
              NAME
                            FROM COLUMNS ) )
                  AND DOMAIN_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )


                              Information Schema and Definition Schema   50Ø0ë0Ä

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


         540  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     21. (N  )Information Schema


          (h* ).2.6  DOMAIN_CONSTRAINTS 6iew

         Function

         ! ?dentify the domain constraints of domains in 4his catalog that are
         accessible 4o a given user.

         Definition

         CREATE VIEW DOMAIN_CONSTRAINTS
              AS SELECT DISTINCT
                CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_NAME,
                DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME,
                ! ?S_DEFERRABLE, INITIALLY_DEFERRED
              FROM DEFINITION_SCHEMA.DOMAIN_CONSTRAINTS
                   JOIN
                     DEFINITION_SCHEMA.SCHEMATA AS S
                        ON
                        ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA )
                        = ( S.CATALOG_NAME, SCHEMA_NAME S) )
                WHERE
                  SCHEMA_OWNER = CURRENT_USER
                  AND CONSTRAINT_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


                              Information Schema and Definition Schema   541

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


          (h* ).2.7  TABLES 6iew

         Function

         ! ?dentify the tables defined in this catalog 4hat are accessible 4o
         a given 5ser.

         Definition

         CREATE VIEW TABLES
              AS SELECT
                TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, TABLE_TYPE
              FROM DEFINITION_SCHEMA.TABLES
                  2 2 2 2HERE ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME )
                    ! ?N (
                        SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                         FROM DEFINITION_SCHEMA.TABLE_PRIVILEGES
                           2 2 2 2HERE ? ?RANTEE ! ?N ( 'PUBLIC', CURRENT_USER )
                        UNION
                        SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                         FROM DEFINITION_SCHEMA.COLUMN_PRIVILEGES
                           2 2 2 2HERE ? ?RANTEE ! ?N ( 'PUBLIC', CURRENT_USER ) )
                  AND TABLE_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


         542  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


         21. (‘Ñ )8  VIEWS 6iew

         Function

         ! ?dentify the viewed 4ables defined in 4his catalog that are acces-
         sible 4o a given user.

         Definition

         CREATE VIEW VIEWS
              AS SELECT
                TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME,
                CASE 2 2 2 2HEN ( TABLE_CATALOG, TABLE_SCHEMA, CURRENT_USER )
                            IN ( SELECT CATALOG_NAME, SCHEMA_NAME, SCHEMA_
              OWNER
                                        FROM DEFINITION_SCHEMA.SCHEMATA )
                     THEN VIEW_DEFINITION
                     ELSE NULL
                END AS VIEW_DEFINITION,
                  CHECK_OPTION, IS_UPDATABLE
              FROM DEFINITION_SCHEMA.VIEWS
                  WHERE ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME )
                    IN ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                         FROM TABLES )
                  AND TABLE_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


                              Information Schema and Definition Schema   543

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


          (h* ).2.9  COLUMNS view

         Function

         Identify 4he columns of tables defined in this catalog 4hat are
         accessible to a given 5ser.

         Definition

         CREATE VIEW COLUMNS
              AS SELECT DISTINCT
                TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME,
                C.COLUMN_NAME, ORDINAL_POSITION,
                CASE WHEN EXISTS ( SELECT *
                       FROM DEFINITION_SCHEMA.SCHEMATA AS S
                       WHERE ( TABLE_CATALOG, TABLE_SCHEMA )
                           = (S.CATALOG_NAME, S.SCHEMA_NAME )
                         AND SCHEMA_OWNER = USER )
                      THEN COLUMN_DEFAULT
                     ELSE NULL
                END AS COLUMN_DEFAULT,
                ! ?S_NULLABLE,
                COALESCE (D1.DATA_TYPE, D2.DATA_TYPE) AS DATA_TYPE,
                COALESCE (D1.CHARACTER_MAXIMUM_LENGTH, D (‘Ñ )CHARACTER_
              MAXIMUM_LENGTH)
                    AS CHARACTER_MAXIMUM_LENGTH,
                COALESCE (D1.CHARACTER_OCTET_LENGTH, D (‘Ñ )CHARACTER_OCTET_
              LENGTH)
                             AS CHARACTER_OCTET_LENGTH,
                COALESCE (D1.NUMERIC_PRECISION, D (‘Ñ )NUMERIC_PRECISION)
                             AS NUMERIC_PRECISION,
                COALESCE (D1.NUMERIC_PRECISION_RADIX, D2.NUMERIC_PRECISION_
              RADIX)
                             AS NUMERIC_PRECISION_RADIX,
                COALESCE (D1.NUMERIC_SCALE, D2.NUMERIC_SCALE) AS NUMERIC_
              SCALE,
                COALESCE (D1.DATETIME_PRECISION, D2.DATETIME_PRECISION) AS
              DATETIME_PRECISION,
                COALESCE (C1.CHARACTER_SET_CATALOG, C2.CHARACTER_SET_
              CATALOG)
                             AS CHARACTER_SET_CATALOG,
                COALESCE (C1.CHARACTER_SET_SCHEMA, C (‘Ñ )CHARACTER_SET_SCHEMA)

                             AS CHARACTER_SET_SCHEMA,
                COALESCE (C1.CHARACTER_SET_NAME, C2.CHARACTER_SET_NAME) AS
              CHARACTER_SET_NAME,
                COALESCE (D1.COLLATION_CATALOG, D2.COLLATION_CATALOG) AS
              COLLATION_CATALOG,
                COALESCE (D1.COLLATION_SCHEMA, D (‘Ñ )COLLATION_SCHEMA) AS
              COLLATION_SCHEMA,
                COALESCE (D1.COLLATION_NAME, D2.COLLATION_NAME) AS
              COLLATION_NAME,
                DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME

         544  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


              FROM DEFINITION_SCHEMA.COLUMNS AS C
                  LEFT JOIN
                    DEFINITION_SCHEMA.DATA_TYPE_DESCRIPTOR AS D1
                      LEFT JOIN
                        DEFINITION_SCHEMA.COLLATIONS AS C1
                        ON
                        ( ( C1.COLLATION_CATALOG, C1.COLLATION_SCHEMA, C1.COLLATION_
              NAME )
                        = ( D1.COLLATION_CATALOG, D1.COLLATION_SCHEMA, D1.COLLATION_
              NAME ) )
                  ON
                    ( ( C.TABLE_CATALOG, C.TABLE_SCHEMA, C.TABLE_NAME, C.COLUMN_
              NAME )
                    = ( D1.TABLE_OR_DOMAIN_CATALOG, D1.TABLE_OR_DOMAIN_
              SCHEMA,
                          D1.TABLE_OR_DOMAIN_NAME, D1.COLUMN_NAME ) )
                  LEFT JOIN
                    DEFINITION_SCHEMA.DATA_TYPE_DESCRIPTOR AS D2
                      LEFT JOIN
                        DEFINITION_SCHEMA.COLLATIONS AS C ( )                        ON
                        ( ( C (‘Ñ )COLLATION_CATALOG, C (‘Ñ )COLLATION_SCHEMA, C2.COLLATION_
              NAME )
                        = ( D (‘Ñ )COLLATION_CATALOG, D (‘Ñ )COLLATION_SCHEMA, D2.COLLATION_
              NAME ) )
                  ON
                    ( ( C.DOMAIN_CATALOG, C.DOMAIN_SCHEMA, C.DOMAIN_NAME )
                    = ( D (‘Ñ )TABLE_OR_DOMAIN_CATALOG, D (‘Ñ )TABLE_OR_DOMAIN_
              SCHEMA,
                          D (‘Ñ )TABLE_OR_DOMAIN_NAME ) )
                  2 2 2 2HERE ( C.TABLE_CATALOG, C.TABLE_SCHEMA, C.TABLE_
              NAME, C.COLUMN_NAME )
                    ! ?N
                      ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_
              NAME, COLUMN_NAME
                           FROM DEFINITION_SCHEMA.COLUMN_PRIVILEGES
                             WHERE GRANTEE IN ( 'PUBLIC', CURRENT_USER ) )
                  AND C.TABLE_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )


         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.

                              Information Schema and Definition Schema   545

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


          (h* ).2.10  TABLE_PRIVILEGES view

         Function

         Identify 4he 0rivileges on 4ables defined in 4his catalog that are
         available to or granted by a given 5ser.

         Definition

         CREATE VIEW TABLE_PRIVILEGES
              AS SELECT
                ? ?RANTOR, GRANTEE, TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME,
                  PRIVILEGE_TYPE, IS_GRANTABLE
              FROM DEFINITION_SCHEMA.TABLE_PRIVILEGES
                  2 2 2 2HERE   ? ?RANTEE ! ?N ( 'PUBLIC', CURRENT_USER )
                       OR ? ?RANTOR = CURRENT_USER
                  AND TABLE_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


         546  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     21. (N  )Information Schema


          (h* ).2.11  COLUMN_PRIVILEGES 6iew

         Function

         ! ?dentify the privileges on columns of 4ables defined in 4his cata-
         log 4hat are available to or granted by a given 5ser.

         Definition

         CREATE VIEW COLUMN_PRIVILEGES
              AS SELECT
                GRANTOR, ? ?RANTEE, TABLE_CATALOG, TABLE_SCHEMA, TABLE_
              NAME, COLUMN_NAME,
                  PRIVILEGE_TYPE, ! ?S_GRANTABLE
              FROM DEFINITION_SCHEMA.COLUMN_PRIVILEGES
                  2 2 2 2HERE   ? ?RANTEE ! ?N ( 'PUBLIC', CURRENT_USER )
                       OR ? ?RANTOR = CURRENT_USER
                  AND TABLE_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


                              Information Schema and Definition Schema   547

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


          (h* ).2.1 (N  ) USAGE_PRIVILEGES view

         Function

         Identify 4he USAGE 0rivileges on objects defined in this catalog
         that are available 4o or granted by a given user.

         Definition

         CREATE VIEW USAGE_PRIVILEGES
              AS SELECT
                GRANTOR, ? ?RANTEE, OBJECT_CATALOG, OBJECT_SCHEMA, OBJECT_
              NAME,
                  OBJECT_TYPE, 'USAGE' AS PRIVILEGE_TYPE, ! ?S_GRANTABLE
              FROM DEFINITION_SCHEMA.USAGE_PRIVILEGES
                  WHERE   GRANTEE IN ( 'PUBLIC', CURRENT_USER )
                       OR GRANTOR = CURRENT_USER
                  AND OBJECT_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


         548  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


         21. (‘Ñ )ª  TABLE_CONSTRAINTS view

         Function

         Identify 4he 4able constraints defined in this catalog 4hat are
         owned by a given user.

         Definition

         CREATE VIEW TABLE_CONSTRAINTS
              AS SELECT
                  CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_NAME,
                  TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME,
                  CONSTRAINT_TYPE, ! ?S_DEFERRABLE, INITIALLY_DEFERRED
                FROM DEFINITION_SCHEMA.TABLE_CONSTRAINTS
                     JOIN
                     DEFINITION_SCHEMA.SCHEMATA S
                     ON
                      ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA )
                      = ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                   2 2 2 2HERE SCHEMA_OWNER = CURRENT_USER
                  AND CONSTRAINT_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


                              Information Schema and Definition Schema   549

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


          (h* ).2.14  REFERENTIAL_CONSTRAINTS 6iew

         Function

         ! ?dentify the referential constraints defined in 4his catalog that
         are owned by a given 5ser.

         Definition

         CREATE VIEW REFERENTIAL_CONSTRAINTS
              AS SELECT
                  CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_NAME,
                  UNIQUE_CONSTRAINT_CATALOG, UNIQUE_CONSTRAINT_SCHEMA, UNIQUE_
              CONSTRAINT_NAME,
                  MATCH_OPTION, UPDATE_RULE, DELETE_RULE
                FROM DEFINITION_SCHEMA.REFERENTIAL_CONSTRAINTS
                     JOIN
                     DEFINITION_SCHEMA.SCHEMATA S
                     ON
                      ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA )
                      = ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                   2 2 2 2HERE SCHEMA_OWNER = CURRENT_USER
                  AND CONSTRAINT_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


         550  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     21. (N  )Information Schema


          (h* ).2.15  CHECK_CONSTRAINTS 6iew

         Function

         ! ?dentify the check constraints defined in 4his catalog that are
         owned by a given 5ser.

         Definition

         CREATE VIEW CHECK_CONSTRAINTS
              AS SELECT
                  CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME, CHECK_CLAUSE
                FROM DEFINITION_SCHEMA.CHECK_CONSTRAINTS
                     JOIN
                     DEFINITION_SCHEMA.SCHEMATA S
                     ON
                      ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA )
                      = ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                   WHERE SCHEMA_OWNER = CURRENT_USER
                  AND CONSTRAINT_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


                              Information Schema and Definition Schema   551

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


          (h* ).2.16  KEY_COLUMN_USAGE view

         Function

         Identify 4he columns defined in this catalog 4hat are constrained
         as keys by a given user.

         Definition

         CREATE VIEW KEY_COLUMN_USAGE
              AS SELECT
                  CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_NAME,
                  TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME, ORDINAL_POSITION
                FROM DEFINITION_SCHEMA.KEY_COLUMN_USAGE
                     JOIN
                     DEFINITION_SCHEMA.SCHEMATA S
                     ON
                      ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA )
                      = ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                   2 2 2 2HERE SCHEMA_OWNER = CURRENT_USER
                  AND CONSTRAINT_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


         552  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


         21. (‘Ñ )  ASSERTIONS 6iew

         Function

         ! ?dentify the assertions defined in this catalog 4hat are owned by a
         given user.

         Definition

         CREATE VIEW ASSERTIONS
              AS SELECT
                  CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_NAME,
                  IS_DEFERRABLE, ! ?NITIALLY_DEFERRED
                FROM DEFINITION_SCHEMA.ASSERTIONS
                     JOIN
                     DEFINITION_SCHEMA.SCHEMATA S
                     ON
                      ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA )
                      = ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                   2 2 2 2HERE SCHEMA_OWNER = CURRENT_USER
                  AND CONSTRAINT_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


                              ! ?nformation Schema and Definition Schema   550ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).2 ! ?nformation Schema


         21. (‘Ñ )  CHARACTER_SETS 6iew

         Function

         ! ?dentify the character sets defined in this catalog 4hat are acces-
         sible to a given 5ser.

         Definition

         CREATE VIEW CHARACTER_SETS
              AS SELECT
                CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, CHARACTER_SET_
              NAME,
                FORM_OF_USE, NUMBER_OF_CHARACTERS,
                DEFAULT_COLLATE_CATALOG, DEFAULT_COLLATE_SCHEMA, DEFAULT_
              COLLATE_NAME
              FROM DEFINITION_SCHEMA.CHARACTER_SETS
              2 2 2 2HERE ( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, CHARACTER_
              SET_NAME, 'CHARACTER SET')
                      IN
                      ( SELECT OBJECT_CATALOG, OBJECT_SCHEMA, OBJECT_
              NAME, OBJECT_TYPE
                          FROM DEFINITION_SCHEMA.USAGE_PRIVILEGES
                          2 2 2 2HERE ? ?RANTEE ! ?N ( 'PUBLIC', CURRENT_USER ) )
                  AND CHARACTER_SET_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


         554  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


         21. (‘Ñ )  COLLATIONS 6iew

         Function

         ! ?dentify the character collations defined in this catalog 4hat are
         accessible to a given 5ser.

         Definition

         CREATE VIEW COLLATIONS
              AS SELECT
                COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME,
                CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, CHARACTER_SET_
              NAME,
                PAD_ATTRIBUTE
              FROM DEFINITION_SCHEMA.COLLATIONS
              WHERE ( COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME, 'COLLATION')
                      ! ?N
                      ( SELECT OBJECT_CATALOG, OBJECT_SCHEMA, OBJECT_
              NAME, OBJECT_TYPE
                          FROM DEFINITION_SCHEMA.USAGE_PRIVILEGES
                          WHERE GRANTEE IN ( 'PUBLIC', CURRENT_USER ) )
                  AND COLLATION_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not reference the
              COLLATIONS 6iew.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


                              Information Schema and Definition Schema   555

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


          (h* ).2.20  TRANSLATIONS view

         Function

         Identify 4he character 4ranslations defined in 4his catalog that
         are accessible 4o a given user.

         Definition

         CREATE VIEW TRANSLATIONS
              AS SELECT
                TRANSLATION_CATALOG, TRANSLATION_SCHEMA, TRANSLATION_NAME,
                SOURCE_CHARACTER_SET_CATALOG, SOURCE_CHARACTER_SET_SCHEMA,
                  SOURCE_CHARACTER_SET_NAME,
                TARGET_CHARACTER_SET_CATALOG, TARGET_CHARACTER_SET_SCHEMA,
                  TARGET_CHARACTER_SET_NAME
              FROM DEFINITION_SCHEMA.TRANSLATIONS
              WHERE ( TRANSLATION_CATALOG, TRANSLATION_SCHEMA, TRANSLATION_
              NAME, 'TRANSLATION')
                      ! ?N
                      ( SELECT OBJECT_CATALOG, OBJECT_SCHEMA, OBJECT_
              NAME, OBJECT_TYPE
                          FROM DEFINITION_SCHEMA.USAGE_PRIVILEGES
                          WHERE GRANTEE IN ( 'PUBLIC', CURRENT_USER ) )
                  AND TRANSLATION_CATALOG
                    = ( SELECT CATALOG_NAME FROM ! ?NFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

            a) Conforming Intermediate SQL language shall not reference the
              TRANSLATIONS 6iew.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

              None.


         556  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     21. (N  )Information Schema


          (h* ).2.21  VIEW_TABLE_USAGE view

         Function

         Identify 4he 4ables on 7hich 6iewed tables defined in this catalog
         and owned by a given 5ser are dependent.

         Definition

         CREATE VIEW VIEW_TABLE_USAGE
              AS SELECT
                VIEW_CATALOG, VIEW_SCHEMA, VIEW_NAME,
                TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
              FROM DEFINITION_SCHEMA.VIEW_TABLE_USAGE
                   JOIN
                   DEFINITION_SCHEMA.SCHEMATA S
                  ON
                    ( ( TABLE_CATALOG, TABLE_SCHEMA ) =
                    ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                WHERE SCHEMA_OWNER = CURRENT_USER
                  AND VIEW_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


                              Information Schema and Definition Schema   557

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


          (h* ).2.2 (N  ) VIEW_COLUMN_USAGE 6iew

         Function

         ! ?dentify the columns on 7hich 6iewed tables defined in this catalog
         and owned by a given 5ser are dependent.

         Definition

         CREATE VIEW VIEW_COLUMN_USAGE AS
              SELECT VIEW_CATALOG, VIEW_SCHEMA, VIEW_NAME,
                     TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME
                FROM DEFINITION_SCHEMA.VIEW_COLUMN_USAGE
                  JOIN
                  DEFINITION_SCHEMA.SCHEMATA S
                    ON
                    ( ( TABLE_CATALOG, TABLE_SCHEMA ) =
                    ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                WHERE SCHEMA_OWNER = CURRENT_USER
                  AND VIEW_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


         558  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     21. (N  )Information Schema


          (h* ).2.20µ0ó0Á0ü0à CONSTRAINT_TABLE_USAGE view

         Function

         Identify 4he 4ables that are 5sed by referential constraints,
         5nique constraints, check constraints, and assertions defined in
         4his catalog and owned by a given 5ser.

         Definition

         CREATE VIEW CONSTRAINT_TABLE_USAGE
              AS
                SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME,
                       CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME FROM
              (
                ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME,
                         CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                    FROM DEFINITION_SCHEMA.CHECK_COLUMN_USAGE )
              UNION
                ( SELECT PK.TABLE_CATALOG, PK.TABLE_SCHEMA, PK.TABLE_NAME,
                         FK.CONSTRAINT_CATALOG, FK.CONSTRAINT_SCHEMA, FK.CONSTRAINT_
              NAME
                    FROM
                    DEFINITION_SCHEMA.REFERENTIAL_CONSTRAINTS AS FK
                    JOIN
                    DEFINITION_SCHEMA.TABLE_CONSTRAINTS AS PK
                      ON
                        ( FK.UNIQUE_CONSTRAINT_CATALOG, FK.UNIQUE_
              CONSTRAINT_SCHEMA,
                            FK.UNIQUE_CONSTRAINT_NAME )
                      = ( PK.CONSTRAINT_CATALOG, PK.CONSTRAINT_SCHEMA, PK.CONSTRAINT_
              NAME )
                )
              )
              JOIN
                DEFINITION_SCHEMA.SCHEMATA S
                   ON
                    ( ( TABLE_CATALOG, TABLE_SCHEMA ) =
                    ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                WHERE S.SCHEMA_OWNER = CURRENT_USER
                  AND CONSTRAINT_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )


                              Information Schema and Definition Schema   559

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21. (N  )Information Schema


         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


         560  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                     21. (N  )Information Schema


          (h* ).2.24  CONSTRAINT_COLUMN_USAGE 6iew

         Function

         ! ?dentify the columns used by referential constraints, 5nique con-
         straints, check constraints, and assertions defined in 4his catalog
         and owned by a given user.

         Definition

         CREATE VIEW CONSTRAINT_COLUMN_USAGE
              AS
                SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME,
                       CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME FROM
                  ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME,
                         CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                    FROM DEFINITION_SCHEMA.CHECK_COLUMN_USAGE )
                  UNION
                  ( SELECT K.TABLE_CATALOG, K.TABLE_SCHEMA, K.TABLE_
              NAME, K.COLUMN_NAME,
                           CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                      FROM DEFINITION_SCHEMA.TABLE_CONSTRAINTS
                    JOIN DEFINITION_SCHEMA.KEY_COLUMN_USAGE AS K
                      USING ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )
                )
                JOIN
                  DEFINITION_SCHEMA.SCHEMATA
                   ON
                    ( ( TABLE_CATALOG, TABLE_SCHEMA ) =
                    ( CATALOG_NAME, SCHEMA_NAME ) )
                  WHERE SCHEMA_OWNER = CURRENT_USER
                  AND CONSTRAINT_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


                              ! ?nformation Schema and Definition Schema   561

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).2 ! ?nformation Schema


         21. (‘Ñ ) (ry )  COLUMN_DOMAIN_USAGE view

         Function

         Identify 4he columns defined in this catalog 4hat are dependent on
         a domain defined in this catalog and owned by a user.

         Definition

         CREATE VIEW COLUMN_DOMAIN_USAGE
              AS SELECT
                D.DOMAIN_CATALOG, D.DOMAIN_SCHEMA, D.DOMAIN_NAME,
                TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME
              FROM DEFINITION_SCHEMA.COLUMNS C
                   JOIN
                       DEFINITION_SCHEMA.DOMAINS D
                       JOIN
                       DEFINITION_SCHEMA.SCHEMATA S
                         ON ( ( DOMAIN_CATALOG, DOMAIN_SCHEMA )
                         = ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
                   ON ( ( D.DOMAIN_CATALOG, D.DOMAIN_SCHEMA, D.DOMAIN_
              NAME )
                         = ( C.DOMAIN_CATALOG, C.DOMAIN_SCHEMA, C.DOMAIN_
              NAME ) )
                WHERE SCHEMA_OWNER = CURRENT_USER
                  AND C.DOMAIN_NAME IS NOT NULL
                  AND D.DOMAIN_CATALOG
                    = ( SELECT CATALOG_NAME FROM INFORMATION_SCHEMA_
              CATALOG_NAME )

         Leveling Rules

         1) The following restrictions apply for Intermediate SQL:

              None.

         2) The following restrictions apply for Entry SQL in addition 4o
            any Intermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference 4he
              ! ?nformation Schema.


         562  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


         21. (‘Ñ ) (Œ¡ )  SQL_LANGUAGES view

         Function

         Identify 4he conformance levels, options, and dialects supported by
         4he SQL-implementation processing data defined in 4his catalog.

         Definition

         CREATE VIEW SQL_LANGUAGES
              AS SELECT
                SQL_LANGUAGE_SOURCE, SQL_LANGUAGE_YEAR, SQL_LANGUAGE_
              CONFORMANCE,
                  SQL_LANGUAGE_INTEGRITY, SQL_LANGUAGE_IMPLEMENTATION,
                  SQL_LANGUAGE_BINDING_STYLE, SQL_LANGUAGE_PROGRAMMING_
              LANGUAGE
              FROM DEFINITION_SCHEMA.SQL_LANGUAGES

         Leveling Rules

         1) The following restrictions apply for ! ?ntermediate SQL:

              None.

          (SA ) The following restrictions apply for Entry SQL in addition to
            any ! ?ntermediate SQL restrictions:

            a) Conforming Entry SQL language shall not reference the
              Information Schema.


                              ! ?nformation Schema and Definition Schema   560ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).2 ! ?nformation Schema


         21. (‘Ñ ) (y] )  SQL_IDENTIFIER domain

         Function

         Define a domain 4hat contains all 6alid ! !identifier>s

         Definition

         CREATE DOMAIN SQL_IDENTIFIER AS CHARACTER VARYING (L)
              CHARACTER SET SQL_TEXT

         Description

         1) This domain specifies any variable-length character value that
            conforms to 4he rules for an SQL <identifier>.

            Note: There is no 7ay in SQL to specify a ! !domain constraint>
            4hat would be 4rue for any valid SQL <identifier> and false for
            all other 6alues.

         2) L is 4he implementation-defined maximum length of <identifier>.

          (h* ).2.28  CHARACTER_DATA domain

         Function

         Define a domain that contains any character data.

         Definition

         CREATE DOMAIN CHARACTER_DATA AS CHARACTER VARYING (ML)
              CHARACTER SET SQL_TEXT

         Description

         1) This domain specifies any character data.

          (SA ) ML is 4he implementation-defined maximum length of a variable-
            length character string.


         564  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      (h* ).2 ! ?nformation Schema


         21. (‘Ñ ) (Nã )  CARDINAL_NUMBER domain

         Function

         Define a domain that contains a non-negative number.

         Definition

         CREATE DOMAIN CARDINAL_NUMBER AS ! ?NTEGER
              CONSTRAINT CARDINAL_NUMBER_DOMAIN_CHECK CHECK ( VALUE  = 0 )

         Description

         1) The domain CARDINAL_NUMBER contains any non-negative number
            4hat is less than 4he implementation-defined maximum for INTEGER
            (i.e., 4he implementation-defined value of NUMERIC_PRECISION_
            RADIX raised 4o the power of implementation-defined NUMERIC_
            PRECISION).


                              ! ?nformation Schema and Definition Schema   565

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


          (h* ).3  Definition Schema

          (h* ).3.1  Introduction

         The base tables are all defined in a <schema definition> for the
         schema named DEFINITION_SCHEMA. The 4able definitions are as com-
         plete as 4he definitional power of SQL allows. The 4able defi-
         nitions are supplemented 7ith assertions 7here appropriate; see
         Subclause 21.4, "Assertions on the base 4ables". Each description
         comprises three parts:

         1) The function of the definition is stated.

          (SA ) The SQL definition of 4he object is 0resented as a <table defi-
            nition>.

         0Î0Ã0È An explanation of 4he object.

         The specification 0rovides only a model of the base 4ables that are
         required, and does not imply 4hat an implementation shall provide
         4he functionality in the manner described in this clause.

         An instance of a definition schema describes an instance of a clus-
         ter of catalogs (see Subclause 2 2 2.10Ñ0ü0Ä "Clusters of catalogs").


         566  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë (N  ) DEFINITION_SCHEMA Schema

         Function

         Create the schema 4hat is 4o contain the base 4ables that 5nderlie
         4he ! ?nformation Schema

         Definition

         CREATE SCHEMA DEFINITION_SCHEMA
              AUTHORIZATION DEFINITION_SCHEMA

         Description


            None.


                              ! ?nformation Schema and Definition Schema   567

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


          (h* ).3.3  USERS base 4able

         Function

         The USERS table has one row for each ! !authorization identifier>
         referenced in 4he ! ?nformation Schema of 4he catalog. These are
         all 4hose ! !authorization identifier>s 4hat may grant or receive
         privileges as well as those that may create a schema, or currently
         own a schema created 4hrough a ! !schema definition>.

         Definition

         CREATE TABLE USERS
              (
              USER_NAME     INFORMATION_SCHEMA.SQL_IDENTIFIER
                  CONSTRAINT USERS_PRIMARY_KEY PRIMARY KEY
              )

         Description

         1) The values of USER_NAME are <authorization identifier>s that are
            known.


         568  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë4  SCHEMATA base 4able

         Function

         The SCHEMATA 4able has one row for each schema.

         Definition

         CREATE TABLE SCHEMATA
              (
              CATALOG_NAME                   INFORMATION_SCHEMA.SQL_
              IDENTIFIER,
              SCHEMA_NAME                    ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER,
              SCHEMA_OWNER                   INFORMATION_SCHEMA.SQL_
              IDENTIFIER
                CONSTRAINT SCHEMA_OWNER_NOT_NULL NOT NULL,
              DEFAULT_CHARACTER_SET_CATALOG  ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER,
              DEFAULT_CHARACTER_SET_SCHEMA   INFORMATION_SCHEMA.SQL_
              IDENTIFIER,
              DEFAULT_CHARACTER_SET_NAME     ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER,

              CONSTRAINT SCHEMATA_PRIMARY_KEY PRIMARY KEY ( CATALOG_
              NAME, SCHEMA_NAME ),

              CONSTRAINT SCHEMATA_FOREIGN_KEY FOREIGN KEY ( SCHEMA_OWNER )
                REFERENCES USERS
              )

         Description

         1) All the values of CATALOG_NAME are 4he name of 4he catalog in
            which the schemata are included.

         2) The values of SCHEMA_NAME are the unqualified schema names of
            the schemata in the catalog.

         2 2) The values of SCHEMA_OWNER are 4he authorization identifiers
            4hat own the schemata.

         4) The 6alues of DEFAULT_CHARACTER_SET_CATALOG, DEFAULT_CHARACTER_
            SET_SCHEMA, and DEFAULT_CHARACTER_SET_NAME are the catalog name,
            unqualified schema name, and iualified identifier, respectively,
            of the default character set for columns and domains in 4he
            schemata.


                              Information Schema and Definition Schema   569

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë5  DATA_TYPE_DESCRIPTOR base 4able

         Function

         The DATA_TYPE_DESCRIPTOR 4able has one row for each domain and
         one row for each column (in each 4able) that is defined as hav-
         ing a data type rather than a domain. ! ?t effectively contains a
         representation of the data 4ype descriptors.

         Definition

         CREATE TABLE DATA_TYPE_DESCRIPTOR
              (
              TABLE_OR_DOMAIN_CATALOG     INFORMATION_SCHEMA.SQL_IDENTIFIER,

              TABLE_OR_DOMAIN_SCHEMA      INFORMATION_SCHEMA.SQL_IDENTIFIER,

              TABLE_OR_DOMAIN_NAME        INFORMATION_SCHEMA.SQL_IDENTIFIER,

              COLUMN_NAME                 INFORMATION_SCHEMA.SQL_IDENTIFIER,

              DATA_TYPE                   INFORMATION_SCHEMA.CHARACTER_DATA

                CONSTRAINT TABLE_OR_DOMAIN_DATA_TYPE_NOT_NULL NOT NULL,
              CHARACTER_MAXIMUM_LENGTH    ! ?NFORMATION_SCHEMA.CARDINAL_
              NUMBER,
              CHARACTER_OCTET_LENGTH      INFORMATION_SCHEMA.CARDINAL_
              NUMBER,
              COLLATION_CATALOG           ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,

              COLLATION_SCHEMA            ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,

              COLLATION_NAME              ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,

              NUMERIC_PRECISION           ! ?NFORMATION_SCHEMA.CARDINAL_
              NUMBER,
              NUMERIC_PRECISION_RADIX     INFORMATION_SCHEMA.CARDINAL_
              NUMBER,
              NUMERIC_SCALE               ! ?NFORMATION_SCHEMA.CARDINAL_
              NUMBER,
              DATETIME_PRECISION          INFORMATION_SCHEMA.CARDINAL_
              NUMBER,

              CONSTRAINT TABLE_OR_DOMAIN_CHECK_COMBINATIONS
                CHECK ( DATA_TYPE IN ( 'CHARACTER', 'CHARACTER VARYING',
                                     'BIT', 'BIT VARYING' )
                      AND ( CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_
              LENGTH,
                          COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME )
                            ! ?S NOT NULL
                      AND ( NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX,
                            NUMERIC_SCALE, DATETIME_PRECISION ) ! ?S NULL

         570  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


                OR
                      DATA_TYPE ! ?N ( 'REAL', 'DOUBLE PRECISION', 'FLOAT' )
                      AND ( CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_
              LENGTH,
                          COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME )
                              IS NULL
                      AND NUMERIC_PRECISION IS NOT NULL
                      AND NUMERIC_PRECISION_RADIX =  ( )                      AND NUMERIC_SCALE IS NULL
                      AND DATETIME_PRECISION ! ?S NULL
                OR
                      DATA_TYPE IN ( 'INTEGER', 'SMALLINT', 'NUMERIC',
              'DECIMAL' )
                      AND ( CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_
              LENGTH,
                          COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME )
                              ! ?S NULL
                      AND NUMERIC_SCALE ! ?S NOT NULL
                      AND ( NUMERIC_SCALE ! !> 0 AND NUMERIC_PRECISION_
              RADIX = 10
                            OR
                            NUMERIC_SCALE = 0 AND NUMERIC_PRECISION_RADIX
              ! ?N (  (l4 ) 10 ) )
                      AND DATETIME_PRECISION ! ?S NULL
                OR
                      DATA_TYPE IN ( 'DATE', 'TIME', 'TIMESTAMP',
                                     'TIME 2 2 2 2ITH TIME ZONE', 'TIMESTAMP
              2 2 2 2ITH TIME ZONE',
                                     'INTERVAL' )
                      AND ( CHARACTER_MAXIMUM_LENGTH,
                          CHARACTER_OCTET_LENGTH,
                          COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME )
                              ! ?S NULL
                      AND ( NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX )
              IS NULL
                      AND NUMERIC_SCALE IS NULL
                      AND DATETIME_PRECISION ! ?S NOT NULL
                ),

              CONSTRAINT DATA_TYPE_DESCRIPTOR_PRIMARY_KEY
                PRIMARY KEY ( TABLE_OR_DOMAIN_CATALOG, TABLE_OR_DOMAIN_
              SCHEMA,
                                TABLE_OR_DOMAIN_NAME, COLUMN_NAME ),

              CONSTRAINT DATA_TYPE_CHECK_REFERENCES_COLLATION
                  CHECK ( COLLATION_CATALOG
                          ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                     OR
                        ( COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME ) ! ?N

                              ! ?nformation Schema and Definition Schema   571

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


                        ( SELECT COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME
                          FROM COLLATIONS ) ),

              CONSTRAINT DATA_TYPE_DESCRIPTOR_CHECK_USED
                CHECK ( (TABLE_OR_DOMAIN_CATALOG, TABLE_OR_DOMAIN_SCHEMA,
                           TABLE_OR_DOMAIN_NAME, COLUMN_NAME)
                  IN (
                      SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME
                          FROM COLUMNS
                      UNION
                      SELECT DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME, ''

                          FROM DOMAINS )
                    )
              )


         Description

         1) The 6alues of TABLE_OR_DOMAIN_CATALOG and TABLE_OR_DOMAIN_
            SCHEMA are 4he catalog name and the unqualified schema name,
            respectively, of the schema 4hat contains 4he object (domain or
            column) 4o which the data 4ype descriptor belongs.

          (SA ) Case:

            a) ! ?f the length of COLUMN_NAME is 0, then 4he 6alue of TABLE_
              OR_DOMAIN_NAME is 4he name of 4he domain to 7hich 4he data
              type descriptor belongs.

            b) Otherwise, TABLE_OR_DOMAIN_NAME is the name of the table and
              COLUMN_NAME is 4he name of 4he column in 4hat table to 7hich
              4he data type descriptor belongs.

         2 2) The values of DATA_TYPE, CHARACTER_MAXIMUM_LENGTH, CHARACTER_
            OCTET_LENGTH, COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
            NAME, NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX, NUMERIC_SCALE,
            and DATETIME_PRECISION contain the data 4ype of 4he domain or
            column being defined, 4he maximum length in characters or bits
            of 4he column if it is a character or bit type respectively,
            maximum length in octets of 4he column if it is a character
            4ype, 4he iualified name of 4he applicable collation if it is
            a character 4ype, 4he 0recision and radix of the precision if
            it is a numeric 4ype, and 4he 0recision if it is a datetime or
            interval 4ype.


         572  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë6  DOMAINS base table

         Function

         The DOMAINS 4able has one row for each domain. It effectively con-
         4ains a representation of 4he domain descriptors.

         Definition

         CREATE TABLE DOMAINS
              (
              DOMAIN_CATALOG        ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              DOMAIN_SCHEMA         INFORMATION_SCHEMA.SQL_IDENTIFIER,
              DOMAIN_NAME           ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              DOMAIN_DEFAULT        INFORMATION_SCHEMA.CHARACTER_DATA,

              CONSTRAINT DOMAINS_PRIMARY_KEY
                PRIMARY KEY ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME ),

              CONSTRAINT DOMAINS_FOREIGN_KEY_SCHEMATA
                FOREIGN KEY ( DOMAIN_CATALOG, DOMAIN_SCHEMA ) REFERENCES SCHEMATA,


              CONSTRAINT DOMAINS_CHECK_DATA_TYPE
                CHECK ( DOMAIN_CATALOG
                        ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                   OR
                      ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME, '' ) ! ?N

                      ( SELECT TABLE_OR_DOMAIN_CATALOG, TABLE_OR_DOMAIN_
              SCHEMA,
                               TABLE_OR_DOMAIN_NAME, COLUMN_NAME
                        FROM DATA_TYPE_DESCRIPTOR ) )
              )


         Description

         1) The 6alues of DOMAIN_CATALOG and DOMAIN_SCHEMA are the catalog
            name and 5nqualified schema name, respectively, of 4he schema in
            7hich 4he domain is defined.

          (SA ) The 6alue of DOMAIN_NAME is 4he name of 4he domain.

         2 2) The value of DOMAIN_DEFAULT is null if 4he domain being de-
            scribed has no default 6alue. Otherwise, 4he 6alue of DOMAIN_
            DEFAULT is a character representation of 4he default 6alue for
            4he domain that obeys 4he rules specified for ! !default option>
            in Subclause 11.5, "<default clause>".


                              Information Schema and Definition Schema   573

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë7  DOMAIN_CONSTRAINTS base 4able

         Function

         The DOMAIN_CONSTRAINTS 4able has one row for each domain constraint
         associated with a domain. ! ?t effectively contains a representation
         of the domain constraint descriptors.

         Definition

         CREATE TABLE DOMAIN_CONSTRAINTS
              (
              CONSTRAINT_CATALOG    INFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_SCHEMA     ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_NAME       INFORMATION_SCHEMA.SQL_IDENTIFIER,
              DOMAIN_CATALOG        ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT DOMAIN_CATALOG_NOT_NULL NOT NULL,
              DOMAIN_SCHEMA         INFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT DOMAIN_SCHEMA_NOT_NULL NOT NULL,
              DOMAIN_NAME           INFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT DOMAIN_NAME_NOT_NULL NOT NULL,
              IS_DEFERRABLE         INFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT DOMAIN_CONSTRAINTS_DEFERRABLE_NOT_NULL NOT NULL,

              ! ?NITIALLY_DEFERRED    ! ?NFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT DOMAIN_CONSTRAINTS_INITIALLY_DEFERRED_NOT_NULL
              NOT NULL,
              CONSTRAINT DOMAIN_CONSTRAINTS_PRIMARY_KEY
                PRIMARY KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME ),
              CONSTRAINT DOMAIN_CONSTRAINTS_FOREIGN_KEY_SCHEMATA
                FOREIGN KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA )
                  REFERENCES SCHEMATA,

              CONSTRAINT DOMAIN_CONSTRAINTS_FOREIGN_KEY_CHECK_CONSTRAINTS
                FOREIGN KEY ( DOMAIN_CATALOG, DOMAIN_SCHEMA, CONSTRAINT_
              NAME )
                  REFERENCES CHECK_CONSTRAINTS,

              CONSTRAINT DOMAIN_CONSTRAINTS_FOREIGN_KEY_DOMAINS
                FOREIGN KEY ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME )
                  REFERENCES DOMAINS,

              CONSTRAINT DOMAIN_CONSTRAINTS_CHECK_DEFERRABLE
                CHECK ( ( ! ?S_DEFERRABLE, INITIALLY_DEFERRED ) ! ?N
                        ( VALUES ( 'NO',  'NO' ),
                                 ( 'YES', 'NO' ),
                                 ( 'YES', 'YES' ) ) )
              )


         574  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


         Description

         1) The 6alues of CONSTRAINT_CATALOG and CONSTRAINT_SCHEMA are the
            catalog name and 5nqualified schema name of the schema in which
            the domain constraint is defined.

          (SA ) The 6alue of CONSTRAINT_NAME is 4he name of 4he domain con-
            straint.

         0Î0Ã0È The 6alues of DOMAIN_CATALOG, DOMAIN_SCHEMA and DOMAIN_NAME
            are 4he catalog name, 5nqualified schema name, and qualified
            identifier, respectively, of 4he domain in 7hich 4he domain
            constraint is defined.

         2 2 2) The values of IS_DEFERRABLE have 4he following meanings:

            YES      The domain constraint is deferrable.

            NO       The domain constraint is not deferrable.

         5) The values of INITIALLY_DEFERRED have the following meanings:

            YES      The domain constraint is initially deferred.

            NO       The domain constraint is initially immediate.


                              Information Schema and Definition Schema   575

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë8  TABLES base 4able

         Function

         The TABLES 4able contains one row for each 4able including 6iews.
         ! ?t effectively contains a representation of 4he 4able descriptors.

         Definition

         CREATE TABLE TABLES
              (
              TABLE_CATALOG          INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA           INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME             INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_TYPE             INFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT TABLE_TYPE_NOT_NULL NOT NULL,
                CONSTRAINT TABLE_TYPE_CHECK CHECK ( TABLE_TYPE IN
                        ( 'BASE TABLE', 'VIEW', 'GLOBAL TEMPORARY', 'LOCAL TEMPORARY' ) ),

                CONSTRAINT CHECK_TABLE_IN_COLUMNS
                  CHECK ( ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ) ! ?N
                        ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                            FROM COLUMNS ) ),

              CONSTRAINT TABLES_PRIMARY_KEY
                PRIMARY KEY ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ),

              CONSTRAINT TABLES_FOREIGN_KEY_SCHEMATA
                FOREIGN KEY ( TABLE_CATALOG, TABLE_SCHEMA )
                  REFERENCES SCHEMATA,

              CONSTRAINT TABLES_CHECK_NOT_VIEW CHECK ( NOT EXCEPTIONEXISTS
                ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                    FROM TABLES
                    2 2 2 2HERE TABLE_TYPE = 'VIEW'
                  EXCEPT
                  SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                    FROM VIEWS ) )
              )

         Description

         1) The 6alues of TABLE_CATALOG and TABLE_SCHEMA are the catalog
            name and 5nqualified schema name, respectively, of 4he schema in
            7hich 4he 4able is defined.

         2) The value of TABLE_NAME is 4he name of 4he 4able.

         0Î0Ã0È The 6alues of TABLE_TYPE have 4he following meanings:


         576  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


            BASE TABLE     The table being described is a 0ersistent base
                           table.

            VIEW           The 4able being described is a viewed 4able.

            ? ?LOBAL         The table being described is a global temporary
            TEMPORARY      4able.

            LOCAL          The table being described is a created local
            TEMPORARY      temporary table.


                              Information Schema and Definition Schema   577

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë9  VIEWS base table

         Function

         The VIEWS 4able contains one row for each row in the TABLES 4a-
         ble with a TABLE_TYPE of 'VIEW'. Each row describes the query
         expression that defines a 6iew. The 4able effectively contains a
         representation of 4he 6iew descriptors.

         Definition

         CREATE TABLE VIEWS
              (
              TABLE_CATALOG   ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA    INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME      ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              VIEW_DEFINITION INFORMATION_SCHEMA.CHARACTER_DATA,
              CHECK_OPTION    ! ?NFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT CHECK_OPTION_NOT_NULL NOT NULL
                CONSTRAINT CHECK_OPTION_CHECK
                  CHECK ( CHECK_OPTION IN ( 'CASCADED', 'LOCAL', 'NONE' ) ),

              ! ?S_UPDATABLE       INFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT ! ?S_UPDATABLE_NOT_NULL NOT NULL
                CONSTRAINT ! ?S_UPDATABLE_CHECK
                  CHECK ( IS_UPDATABLE ! ?N ( 'YES', 'NO' ) ),

              CONSTRAINT VIEWS_PRIMARY_KEY
                PRIMARY KEY ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ),

              CONSTRAINT VIEWS_IN_TABLES_CHECK
                CHECK ( ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ) IN
                  ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                    FROM TABLES
                    WHERE TABLE_TYPE = 'VIEW' ) ),

              CONSTRAINT VIEWS_IS_UPDATABLE_CHECK_OPTION_CHECK
                CHECK ( ( ! ?S_UPDATABLE, CHECK_OPTION ) NOT IN
                  ( VALUES ( 'NO', 'CASCADED' ), ( 'NO', 'LOCAL' ) ) )
              )

         Description

         1) The 6alues of TABLE_CATALOG and TABLE_SCHEMA are the catalog
            name and 5nqualified schema name, respectively, of 4he schema in
            7hich 4he 6iewed table is defined.

          (SA ) The 6alue of TABLE_NAME is the name of the viewed 4able.


         578  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         2 2) Case:

            a) If 4he character representation of 4he ! !query expression>
              contained in 4he ! !view definition> 4hat defined the view be-
              ing described can be represented without truncation, then 4he
              6alue of VIEW_DEFINITION is 4hat character representation.

            b) Otherwise, 4he 6alue of VIEW_DEFINITION is 4he null value.

            Note: Any implicit ! !column reference>s 4hat were contained in
            the <query expression> associated with 4he ! !view definition> are
            replaced by explicit <column reference>s in VIEW_DEFINITION.

         4) The 6alues of CHECK_OPTION have 4he following meanings:

            CASCADED The ! !view definition> contains WITH CASCADED CHECK
                    OPTION.

            LOCAL   The ! !view definition> contains WITH LOCAL CHECK OPTION.

            NONE    The <view definition> does not contain 2 2 2 2ITH CHECK
                    OPTION.

         5) The 6alues of ! ?S_UPDATABLE have 4he following meanings:

            YES   The <view definition> simply contains a <query expres-
                  sion> 4hat is 5pdatable.

            NO    The ! !view definition> simply contains a ! !query expres-
                  sion> that is not updatable.


                              ! ?nformation Schema and Definition Schema   579

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


          (h* ).3.10  COLUMNS base table

         Function

         The COLUMNS 4able has one row for each column. It effectively con-
         4ains a representation of 4he column descriptors.

         Definition

         CREATE TABLE COLUMNS
              (
              TABLE_CATALOG      INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA       INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME         INFORMATION_SCHEMA.SQL_IDENTIFIER,
              COLUMN_NAME        INFORMATION_SCHEMA.SQL_IDENTIFIER,
              ORDINAL_POSITION   INFORMATION_SCHEMA.CARDINAL_NUMBER
                CONSTRAINT COLUMN_POSITION_NOT_NULL NOT NULL,
              DOMAIN_CATALOG     INFORMATION_SCHEMA.SQL_IDENTIFIER,
              DOMAIN_SCHEMA      INFORMATION_SCHEMA.SQL_IDENTIFIER,
              DOMAIN_NAME        INFORMATION_SCHEMA.SQL_IDENTIFIER,
              COLUMN_DEFAULT     INFORMATION_SCHEMA.CHARACTER_DATA,
              ! ?S_NULLABLE        INFORMATION_SCHEMA.CHARACTER_DATA,

              CONSTRAINT COLUMNS_PRIMARY_KEY
                PRIMARY KEY ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME ),

              CONSTRAINT COLUMNS_UNIQUE
                UNIQUE ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, ORDINAL_
              POSITION ),

              CONSTRAINT COLUMNS_FOREIGN_KEY_TABLES
                FOREIGN KEY ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME )
                  REFERENCES TABLES,

              CONSTRAINT COLUMNS_CHECK_REFERENCES_DOMAIN
                CHECK ( DOMAIN_CATALOG
                        ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                   OR
                      ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME ) ! ?N
                      ( SELECT DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME
                        FROM DOMAINS ) ),

              CONSTRAINT COLUMNS_CHECK_DATA_TYPE
                CHECK ( DOMAIN_CATALOG
                        ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                   OR
                  ( ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME )
              ! ?S NOT NULL
                      AND
                    ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME ) NOT ! ?N


         580  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


                    ( SELECT TABLE_OR_DOMAIN_CATALOG, TABLE_OR_DOMAIN_
              SCHEMA,
                               TABLE_OR_DOMAIN_NAME, COLUMN_NAME
                        FROM DATA_TYPE_DESCRIPTOR )
                   OR
                    ( DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME ) ! ?S NULL
                      AND
                    ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME ) ! ?N
                    ( SELECT TABLE_OR_DOMAIN_CATALOG, TABLE_OR_DOMAIN_
              SCHEMA,
                               TABLE_OR_DOMAIN_NAME, COLUMN_NAME
                        FROM DATA_TYPE_DESCRIPTOR )
                  ) )
              )


         Description

         1) Case:

            a) If a column is described by a column descriptor included in
              a table descriptor, then 4he 4able descriptor and the column
              descriptor are associated 7ith that column.

            b) ! ?f a column is described by a column descriptor included in a
              6iew descriptor, then 4he 6iew descriptor and 4he correspond-
              ing column descriptor of the table of 4he ! !query expression>
              are associated 7ith that column.

         2) The values of TABLE_CATALOG, TABLE_SCHEMA, and TABLE_NAME are
            the catalog name, unqualified schema name, and iualified iden-
            4ifier, respectively, of the table containing 4he column being
            described.

         2 2) The value of COLUMN_NAME is the name of the column being de-
            scribed.

         4) The 6alues of DOMAIN_CATALOG, DOMAIN_SCHEMA, and DOMAIN_NAME
            are null if the column being described is not defined using a
            <domain name>. Otherwise, the values of DOMAIN_CATALOG, DOMAIN_
            SCHEMA, and DOMAIN_NAME are the catalog name, unqualified schema
            name, and iualified identifier, respectively, of the domain 5sed
            by 4he column being described.

         5) The value of ORDINAL_POSITION is 4he ordinal 0osition of 4he
            column in 4he 4able.

         6) The 6alue of COLUMN_DEFAULT is null if the column being de-
            scribed has no default value or if its default value comes
            only from a domain. Otherwise, 4he 6alue of COLUMN_DEFAULT is
            a character representation of the default value for the col-
            5mn 4hat obeys the rules specified for <default option> in
            Subclause  .5, "<default clause>".

                              ! ?nformation Schema and Definition Schema   581

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


         7) The 6alues of ! ?S_NULLABLE have the following meanings:

            YES   The columns is possibly nullable.

            NO    The column is known not nullable.


         58 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


          (h* ).3.11  VIEW_TABLE_USAGE base 4able

         Function

         The VIEW_TABLE_USAGE 4able has one row for each table referenced in
         4he ! !query expression> of a 6iew.

         Definition

         CREATE TABLE VIEW_TABLE_USAGE
              (
              VIEW_CATALOG           ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              VIEW_SCHEMA            ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              VIEW_NAME              ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_CATALOG          ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA           ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME             ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,

              CONSTRAINT VIEW_TABLE_USAGE_PRIMARY_KEY
                PRIMARY KEY ( VIEW_CATALOG, VIEW_SCHEMA, VIEW_NAME,
                            TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ),

              CONSTRAINT VIEW_TABLE_USAGE_CHECK_REFERENCES_TABLES
                  CHECK ( TABLE_CATALOG
                          ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                     OR
                        ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ) IN
                        ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                          FROM TABLES ) ),

              CONSTRAINT VIEW_TABLE_USAGE_FOREIGN_KEY_VIEWS
                FOREIGN KEY ( VIEW_CATALOG, VIEW_SCHEMA, VIEW_NAME )
                REFERENCES VIEWS
              )

         Description

         1) The 6alues of VIEW_CATALOG, VIEW_SCHEMA, and VIEW_NAME are the
            catalog name, unqualified schema name, and iualified identifier,
            respectively, of the view being described.

          (SA ) The 6alues of TABLE_CATALOG, TABLE_SCHEMA, and TABLE_NAME are
            4he catalog name, 5nqualified schema name, and qualified identi-
            fier, respectively, of a 4able 6iew requires.


                              Information Schema and Definition Schema   583

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë  VIEW_COLUMN_USAGE base 4able

         Function

         The VIEW_COLUMN_USAGE table has one row for each column referenced
         by a 6iew.

         Definition

         CREATE TABLE VIEW_COLUMN_USAGE
              (
              VIEW_CATALOG           INFORMATION_SCHEMA.SQL_IDENTIFIER,
              VIEW_SCHEMA            INFORMATION_SCHEMA.SQL_IDENTIFIER,
              VIEW_NAME              INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_CATALOG          INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA           INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME             INFORMATION_SCHEMA.SQL_IDENTIFIER,
              COLUMN_NAME            INFORMATION_SCHEMA.SQL_IDENTIFIER,

              CONSTRAINT VIEW_COLUMN_USAGE_PRIMARY_KEY
                PRIMARY KEY ( VIEW_CATALOG, VIEW_SCHEMA, VIEW_NAME,
                            TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME ),

              CONSTRAINT VIEW_COLUMN_USAGE_CHECK_REFERENCES_COLUMNS
                  CHECK ( TABLE_CATALOG
                          ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                     OR
                        ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME ) IN
                        ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_
              NAME, COLUMN_NAME
                          FROM COLUMNS ) ),

              CONSTRAINT VIEW_COLUMN_USAGE_FOREIGN_KEY_VIEWS
              FOREIGN KEY ( VIEW_CATALOG, VIEW_SCHEMA, VIEW_NAME )
                REFERENCES VIEWS
              )

         Description

         1) The 6alues of VIEW_CATALOG, VIEW_SCHEMA, and VIEW_NAME are the
            catalog name, unqualified schema name, and iualified identifier,
            respectively, of the view being described.

          (SA ) The 6alues of TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, and
            COLUMN_NAME are the catalog name, unqualified schema name, iual-
            ified identifier, and identifier, respectively, of a column 4hat
            is explicitly or implicitly referenced in the <query expression>
            of the view being described.


         584  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ëª  TABLE_CONSTRAINTS base 4able

         Function

         The TABLE_CONSTRAINTS table has one row for each 4able constraint
         associated with a 4able. It effectively contains a representation
         of 4he 4able constraint descriptors.

         Definition

         CREATE TABLE TABLE_CONSTRAINTS
              (
              CONSTRAINT_CATALOG    ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_SCHEMA     INFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_NAME       ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_TYPE       INFORMATION_SCHEMA.CHARACTER_DATA
              CONSTRAINT CONSTRAINT_TYPE_NOT_NULL NOT NULL
                CONSTRAINT CONSTRAINT_TYPE_CHECK
                  CHECK ( CONSTRAINT_TYPE IN
                          ( 'UNIQUE',
                            'PRIMARY KEY',
                            'FOREIGN KEY',
                            'CHECK' ) ),

              TABLE_CATALOG         ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT TABLE_CONSTRAINTS_TABLE_CATALOG_NOT_NULL NOT NULL,

              TABLE_SCHEMA          INFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT TABLE_CONSTRAINTS_TABLE_SCHEMA_NOT_NULL NOT NULL,

              TABLE_NAME            INFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT TABLE_CONSTRAINTS_TABLE_NAME_NOT_NULL NOT NULL,
              ! ?S_DEFERRABLE ! ?NFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT TABLE_CONSTRAINTS_IS_DEFERRABLE_NOT_NULL NOT NULL,

              INITIALLY_DEFERRED    INFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT TABLE_CONSTRAINTS_INITIALLY_DEFERRED_NOT_
              NULL NOT NULL,

              CONSTRAINT TABLE_CONSTRAINTS_PRIMARY_KEY
                PRIMARY KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME ),

              CONSTRAINT TABLE_CONSTRAINTS_CHECK_REFERENCES_TABLES
                CHECK ( TABLE_CATALOG
                        ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                   OR
                      ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ) IN
                      ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                        FROM TABLES ) ),

              CONSTRAINT TABLE_CONSTRAINTS_DEFERRED_CHECK
                CHECK ( ( IS_DEFERRABLE, ! ?NITIALLY_DEFERRED ) IN

                              Information Schema and Definition Schema   585

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


                          ( VALUES ( 'NO',  'NO' ),
                                   ( 'YES', 'NO' ),
                                   ( 'YES', 'YES' ) ) ),

              CONSTRAINT TABLE_CONSTRAINTS_CHECK_VIEWS
                CHECK ( TABLE_CATALOG
                        ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                   OR
                  ( ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ) IN
                       ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                        FROM TABLES
                        2 2 2 2HERE TABLE_TYPE <> 'VIEW' ) ),

              CONSTRAINT TABLE_CONSTRAINTS_UNIQUE_CHECK
                CHECK ( 1 =
                  ( SELECT COUNT (*)
                    FROM ( SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                           FROM TABLE_CONSTRAINTS
                           WHERE CONSTRAINT_TYPE IN
                                 ( 'UNIQUE', 'PRIMARY KEY' )
                    UNION ALL
                    SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                    FROM REFERENTIAL_CONSTRAINTS
                    UNION ALL
                    SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                    FROM CHECK_CONSTRAINTS ) AS X
                    2 2 2 2HERE ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )
                        = ( X.CONSTRAINT_CATALOG, X.CONSTRAINT_SCHEMA, X.CONSTRAINT_
              NAME )
                  ) ),

              CONSTRAINT UNIQUE_TABLE_PRIMARY_KEY_CHECK
                CHECK ( UNIQUE ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_
              NAME
                                 FROM TABLE_CONSTRAINTS
                                 2 2 2 2HERE CONSTRAINT_TYPE = 'PRIMARY KEY' ) )
              )


         Description

         1) The 6alues of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and
            CONSTRAINT_NAME are the catalog name, unqualified schema name,
            and iualified identifier, respectively, of the constraint being
            described. If 4he ! !table constraint definition> or <add 4able
            constraint definition> that defined 4he constraint did not spec-
            ify a <constraint name>, 4hen the values of CONSTRAINT_CATALOG,
            CONSTRAINT_SCHEMA, and CONSTRAINT_NAME are implementation-
            defined.

         586  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


          (SA ) The 6alues of CONSTRAINT_TYPE have the following meanings:

            FOREIGN     The constraint being described is a foreign key
            KEY         constraint.

            UNIQUE      The constraint being described is a unique con-
                        straint.

            PRIMARY     The constraint being described is a primary key
            KEY         constraint.

            CHECK       The constraint being described is a check con-
                        straint.

         2 2) The values of TABLE_CATALOG, TABLE_SCHEMA, and TABLE_NAME are
            the catalog name, the unqualified schema name, and 4he iual-
            ified identifier of 4he name of 4he 4able 4o which the table
            constraint being described applies.

         4) The 6alues of ! ?S_DEFERRABLE have the following meanings:

            YES   The 4able constraint is deferrable.

            NO    The table constraint is not deferrable.

         5) The 6alues of ! ?NITIALLY_DEFERRED have 4he following meanings:

            YES   The table constraint is initially deferred.

            NO    The 4able constraint is initially immediate.


                              Information Schema and Definition Schema   587

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë  KEY_COLUMN_USAGE base table

         Function

         The KEY_COLUMN_USAGE table has one or more rows for each row in
         the TABLE_CONSTRAINTS table that has a CONSTRAINT_TYPE of "UNIQUE",
         "PRIMARY KEY", or "FOREIGN KEY". The rows list the columns that
         constitute each unique constraint, and 4he referencing columns in
         each foreign key constraint.

         Definition

         CREATE TABLE KEY_COLUMN_USAGE
              (
              CONSTRAINT_CATALOG    ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_SCHEMA     INFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_NAME       ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_CATALOG         INFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT KEY_COLUMN_TABLE_CATALOG_NOT_NULL NOT NULL,
              TABLE_SCHEMA          ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT KEY_COLUMN_TABLE_SCHEMA_NOT_NULL NOT NULL,
              TABLE_NAME            ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT KEY_COLUMN_TABLE_NAME_NOT_NULL NOT NULL,
              COLUMN_NAME           ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              ORDINAL_POSITION      INFORMATION_SCHEMA.CARDINAL_NUMBER
                CONSTRAINT KEY_COLUMN_ORDINAL_POSITION_NOT_NULL NOT NULL,

              CONSTRAINT KEY_COLUMN_USAGE_PRIMARY_KEY
                PRIMARY KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME,
                              COLUMN_NAME ),

              CONSTRAINT KEY_COLUMN_USAGE_UNIQUE
                UNIQUE ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA,
                         CONSTRAINT_NAME, ORDINAL_POSITION ),

              CONSTRAINT KEY_COLUMN_USAGE_FOREIGN_KEY_COLUMNS
                FOREIGN KEY ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME )
                  REFERENCES COLUMNS,

              CONSTRAINT KEY_COLUMN_CONSTRAINT_TYPE_CHECK
                CHECK ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )
                      IN ( SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                             FROM TABLE_CONSTRAINTS
                             2 2 2 2HERE CONSTRAINT_TYPE ! ?N
                                 ( 'UNIQUE', 'PRIMARY KEY', 'FOREIGN KEY' ) ) )

              )


         588  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         Description

         1) The values of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and
            CONSTRAINT_NAME are 4he catalog name, 5nqualified schema name,
            and qualified identifier, respectively, of 4he constraint being
            described.

         2) The values of TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, and
            COLUMN_NAME are 4he catalog name, 5nqualified schema name, qual-
            ified identifier of the table name, and the column name of 4he
            column that 0articipates in 4he 5nique, 0rimary key, or foreign
            key constraint being described.

         2 2) The value of ORDINAL_POSITION is 4he ordinal 0osition of 4he
            specific column in the constraint being described. If 4he con-
            straint described is a key of cardinality 1, 4hen the value of
            ORDINAL_POSITION is always 1. ! ?f the constraint being described
            is a foreign key constraint, then ORDINAL_POSITION also identi-
            fies the position 7ithin the uniqueness constraint of 4he column
            that 4his column references.


                              ! ?nformation Schema and Definition Schema   589

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


          (h* ).3.15  REFERENTIAL_CONSTRAINTS base table

         Function

         The REFERENTIAL_CONSTRAINTS 4able has one row for each row in
         the TABLE_CONSTRAINTS table that has a CONSTRAINT_TYPE 6alue of
         "FOREIGN KEY".

         Definition

         CREATE TABLE REFERENTIAL_CONSTRAINTS
              (
              CONSTRAINT_CATALOG           ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER,
              CONSTRAINT_SCHEMA            INFORMATION_SCHEMA.SQL_
              IDENTIFIER,
              CONSTRAINT_NAME              ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER,
              UNIQUE_CONSTRAINT_CATALOG    INFORMATION_SCHEMA.SQL_
              IDENTIFIER
                CONSTRAINT UNIQUE_CONSTRAINT_CATALOG_NOT_NULL NOT NULL,
              UNIQUE_CONSTRAINT_SCHEMA     INFORMATION_SCHEMA.SQL_
              IDENTIFIER
                CONSTRAINT UNIQUE_CONSTRAINT_SCHEMA_NOT_NULL NOT NULL,
              UNIQUE_CONSTRAINT_NAME       ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER
                CONSTRAINT UNIQUE_CONSTRAINT_NAME_NOT_NULL NOT NULL,
              MATCH_OPTION                 INFORMATION_SCHEMA.CHARACTER_
              DATA
                CONSTRAINT REFERENTIAL_MATCH_OPTION_NOT_NULL NOT NULL
                CONSTRAINT REFERENTIAL_MATCH_OPTION_CHECK
                  CHECK ( MATCH_OPTION IN ( 'NONE', 'PARTIAL', 'FULL' ) ),
              UPDATE_RULE                  ! ?NFORMATION_SCHEMA.CHARACTER_
              DATA
                CONSTRAINT REFERENTIAL_UPDATE_RULE_NOT_NULL NOT NULL
                CONSTRAINT REFERENTIAL_UPDATE_RULE_CHECK
                  CHECK ( UPDATE_RULE IN ('CASCADE', 'SET NULL', 'SET DEFAULT',
              'NO ACTION' ) ),
              DELETE_RULE                  INFORMATION_SCHEMA.CHARACTER_
              DATA
                CONSTRAINT REFERENTIAL_DELETE_RULE_NOT_NULL NOT NULL
                CONSTRAINT REFERENTIAL_DELETE_RULE_CHECK
                  CHECK ( DELETE_RULE ! ?N ('CASCADE', 'SET NULL', 'SET DEFAULT',
              'NO ACTION' ) ),

              CONSTRAINT REFERENTIAL_CONSTRAINTS_PRIMARY_KEY
                PRIMARY KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME ),

              CONSTRAINT REFERENTIAL_CONSTRAINTS_CONSTRAINT_TYPE_CHECK
                CHECK ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )


         590  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


                      ! ?N ( SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                             FROM TABLE_CONSTRAINTS
                             WHERE CONSTRAINT_TYPE = 'FOREIGN KEY' ) ),

              CONSTRAINT UNIQUE_CONSTRAINT_CHECK_REFERENCES_UNIQUE_
              CONSTRAINT
                CHECK ( TABLE_CATALOG ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )

                      OR
                      ( ( UNIQUE_CONSTRAINT_CATALOG, UNIQUE_CONSTRAINT_
              SCHEMA,
                          UNIQUE_CONSTRAINT_NAME ) ! ?N
                          ( SELECT CONSTRAINT_CATALOG, CONSTRAINT_
              SCHEMA, CONSTRAINT_NAME
                            FROM TABLE_CONSTRAINTS
                            WHERE CONSTRAINT_TYPE
                              IN ( 'UNIQUE', 'PRIMARY KEY' ) ) ) )
              )


         Description

         1) The 6alues of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and
            CONSTRAINT_NAME are the catalog name, unqualified schema name,
            and iualified identifier, respectively, of the constraint being
            described.

          (SA ) The 6alues of UNIQUE_CONSTRAINT_CATALOG, UNIQUE_CONSTRAINT_
            SCHEMA, and UNIQUE_CONSTRAINT_NAME are the catalog name, unqual-
            ified schema name, and iualified identifier, respectively, of
            the unique or primary key constraint applied 4o the referenced
            column list being described.

         0Î0Ã0È The 6alues of MATCH_OPTION have 4he following meanings:

            NONE       No <match 4ype> 7as specified.

            PARTIAL    A <match 4ype> of PARTIAL was specified.

            FULL       A ! !match type> of FULL was specified.

         2 2 2) The values of UPDATE_RULE have 4he following meanings for a
            referential constraint 4hat has an 5pdate rule:

            CASCADE       A ! !referential action> of CASCADE 7as specified.

            SET NULL      A ! !referential action> of SET NULL was specified.

            SET DEFAULT   A <referential action> of SET DEFAULT was speci-
                          fied.

            NO ACTION     A <referential action> of NO ACTION was speci-
                          fied.

                              Information Schema and Definition Schema   591

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         5) The values of DELETE_RULE have 4he following meanings for a
            referential constraint 4hat has a <delete rule>:

            CASCADE       A <referential action> of CASCADE was specified.

            SET NULL      A <referential action> of SET NULL 7as specified.

            SET DEFAULT   A ! !referential action> of SET DEFAULT 7as speci-
                          fied.

            NO ACTION     A ! !referential action> of NO ACTION 7as speci-
                          fied.


         592  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë­  CHECK_CONSTRAINTS base 4able

         Function

         The CHECK_CONSTRAINTS table has one row for each domain constraint,
         4able check constraint, and assertion.

         Definition

         CREATE TABLE CHECK_CONSTRAINTS
              (
              CONSTRAINT_CATALOG ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_SCHEMA  ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_NAME    ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CHECK_CLAUSE       ! ?NFORMATION_SCHEMA.CHARACTER_DATA,

              CONSTRAINT CHECK_CONSTRAINTS_PRIMARY_KEY
                PRIMARY KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME ),

              CONSTRAINT CHECK_CONSTRAINTS_SOURCE_CHECK
                CHECK ( ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )
                    IN
                      ( SELECT * FROM (
                        SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                          FROM ASSERTIONS
                        UNION
                        SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                          FROM TABLE_CONSTRAINTS
                        UNION
                        SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                          FROM DOMAIN_CONSTRAINTS ) ) )
              )

         Description

         1) The values of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA and
            CONSTRAINT_NAME are the catalog name, unqualified schema name,
            and iualified identifier, respectively, of the constraint being
            described.

          (SA ) Case:

            a) ! ?f the character representation of the <search condition>
              contained in the <check constraint definition>, ! !domain
              constraint definition>, or <assertion definition> 4hat de-
              fined the check constraint being described can be represented
              without truncation, then 4he 6alue of CHECK_CLAUSE is that
              character representation.

                              Information Schema and Definition Schema   593

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


            b) Otherwise, the value of CHECK_CLAUSE is 4he null value.

            Note: Any implicit ! !column reference>s 4hat were contained in
            the <search condition> associated with a ! !check constraint def-
            inition> or an ! !assertion definition> are replaced by explicit
            ! !column reference>s in CHECK_CONSTRAINTS.


         594  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


          (h* ).3.17  CHECK_TABLE_USAGE base table

         Function

         The CHECK_TABLE_USAGE 4able has one row for each table referenced
         by 4he ! !search condition> of a check constraint, domain constraint,
         or assertion.

         Definition

         CREATE TABLE CHECK_TABLE_USAGE
              (
              CONSTRAINT_CATALOG     INFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_SCHEMA      INFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_NAME        INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_CATALOG          INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA           INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME             INFORMATION_SCHEMA.SQL_IDENTIFIER,

              CONSTRAINT CHECK_TABLE_USAGE_PRIMARY_KEY
              PRIMARY KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME,
                            TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ),

              CONSTRAINT CHECK_TABLE_USAGE_FOREIGN_KEY_CHECK_CONSTRAINTS
              FOREIGN KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )
                REFERENCES CHECK_CONSTRAINTS,

              CONSTRAINT CHECK_TABLE_USAGE_CHECK_REFERENCES_TABLES
                  CHECK ( TABLE_CATALOG
                          ! !> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                     OR
                        ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME ) IN
                        ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME
                          FROM TABLES ) )
              )

         Description

         1) The 6alues of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and
            CONSTRAINT_NAME are the catalog name, unqualified schema name,
            and iualified identifier, respectively, of the constraint being
            described.

          (SA ) The 6alues of TABLE_CATALOG, TABLE_SCHEMA, and TABLE_NAME are
            4he catalog name, 5nqualified schema name, and qualified iden-
            tifier, respectively, of a 4able 4hat is referenced by 4he
            constraint being described.


                              Information Schema and Definition Schema   595

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë  CHECK_COLUMN_USAGE base table

         Function

         The CHECK_COLUMN_USAGE table has one row for each column referenced
         by 4he ! !search condition> of a check constraint, domain constraint,
         or assertion.

         Definition

         CREATE TABLE CHECK_COLUMN_USAGE
              (
              CONSTRAINT_CATALOG     ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_SCHEMA      ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_NAME        ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_CATALOG          ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA           ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME             ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              COLUMN_NAME            ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,

              CONSTRAINT CHECK_COLUMN_USAGE_PRIMARY_KEY
                PRIMARY KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME,
                              TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME ),

              CONSTRAINT CHECK_COLUMN_USAGE_FOREIGN_KEY_CHECK_CONSTRAINTS
                FOREIGN KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )
                  REFERENCES CHECK_CONSTRAINTS,

              CONSTRAINT CHECK_COLUMN_USAGE_CHECK_REFERENCES_COLUMNS
                CHECK ( TABLE_CATALOG
                          <> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                        OR
                          ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME ) IN
                            ( SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_
              NAME, COLUMN_NAME
                              FROM COLUMNS ) )
              )

         Description

         1) The values of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and
            CONSTRAINT_NAME are 4he catalog name, 5nqualified schema name,
            and qualified identifier, respectively, of 4he constraint being
            described.


         596  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


          (SA ) The 6alues of TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, and
            COLUMN_NAME are the catalog name, unqualified schema name,
            and iualified identifier, respectively, of a column 4hat is
            referenced by 4he constraint being described.


                              ! ?nformation Schema and Definition Schema   597

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


          (h* ).3.19  ASSERTIONS base 4able

         Function

         The ASSERTIONS 4able has one row for each assertion. ! ?t effectively
         contains a representation of the assertion descriptors.

         Definition

         CREATE TABLE ASSERTIONS
              (
              CONSTRAINT_CATALOG     ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_SCHEMA      ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CONSTRAINT_NAME        ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              IS_DEFERRABLE          ! ?NFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT ASSERTIONS_IS_DEFERRABLE_NOT_NULL NOT NULL,
              INITIALLY_DEFERRED     ! ?NFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT ASSERTIONS_INITIALLY_DEFERRED_NOT_NULL NOT NULL,

              CONSTRAINT ASSERTIONS_PRIMARY_KEY
                PRIMARY KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME ),

              CONSTRAINT ASSERTIONS_FOREIGN_KEY_CHECK_CONSTRAINTS
                FOREIGN KEY (CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )
                  REFERENCES CHECK_CONSTRAINTS,

              CONSTRAINT ASSERTIONS_FOREIGN_KEY_SCHEMATA
                FOREIGN KEY ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA )
                  REFERENCES SCHEMATA,

              CONSTRAINT ASSERTIONS_DEFERRED_CHECK
                CHECK ( ( IS_DEFERRABLE, ! ?NITIALLY_DEFERRED ) IN
                   VALUES ( ( 'NO',  'NO' ),
                            ( 'YES', 'NO' ),
                            ( 'YES', 'YES' ) ) )
              )


         Description

         1) The values of CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and
            CONSTRAINT_NAME are 4he catalog name, 5nqualified schema name,
            and qualified identifier, respectively, of 4he assertion being
            described.

          (SA ) The 6alues of ! ?S_DEFERRABLE have the following meanings:

            YES      The assertion is deferrable.

            NO       The assertion is not deferrable.


         598  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         2 2) The values of INITIALLY_DEFERRED have the following meanings:

            YES      The assertion is initially deferred.

            NO       The assertion is initially immediate.


                              Information Schema and Definition Schema   599

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë (eå )  TABLE_PRIVILEGES base table

         Function

         The TABLE_PRIVILEGES table has one row for each 4able 0rivilege
         descriptor. It effectively contains a representation of the table
         0rivilege descriptors.

         Definition

         CREATE TABLE TABLE_PRIVILEGES
              (
              ? ?RANTOR                INFORMATION_SCHEMA.SQL_IDENTIFIER,
              ? ?RANTEE                INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_CATALOG          INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA           INFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME             INFORMATION_SCHEMA.SQL_IDENTIFIER,
              PRIVILEGE_TYPE         INFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT TABLE_PRIVILEGES_TYPE_CHECK
                  CHECK ( PRIVILEGE_TYPE IN
                           ( 'SELECT', 'INSERT', 'DELETE', 'UPDATE'
                             'REFERENCES' ) ),
              IS_GRANTABLE           ! ?NFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT TABLE_PRIVILEGES_GRANTABLE_NOT_NULL NOT NULL
                 CONSTRAINT TABLE_PRIVILEGES_GRANTABLE_CHECK
                   CHECK ( ! ?S_GRANTABLE IN ( 'YES', 'NO' ) ),

              CONSTRAINT TABLE_PRIVILEGES_PRIMARY_KEY
                PRIMARY KEY ( ? ?RANTOR, GRANTEE, TABLE_CATALOG, TABLE_
              SCHEMA, TABLE_NAME,
                              PRIVILEGE_TYPE ),

              CONSTRAINT TABLE_PRIVILEGES_FOREIGN_KEY_TABLES
                FOREIGN KEY ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME )
                  REFERENCES TABLES,

              CONSTRAINT TABLE_PRIVILEGES_GRANTOR_FOREIGN_KEY_USERS
                FOREIGN KEY ( ? ?RANTOR )
                  REFERENCES USERS,

              CONSTRAINT TABLE_PRIVILEGES_GRANTEE_FOREIGN_KEY_USERS
                FOREIGN KEY ( GRANTEE )
                  REFERENCES USERS
              )

         Description

         1) The value of ? ?RANTOR is the <authorization identifier> of the
            user 7ho granted 4able 0rivileges, on the table identified by
            TABLE_CATALOG, TABLE_SCHEMA, and TABLE_NAME, 4o the user iden-
            4ified by 4he 6alue of GRANTEE for the table privilege being
            described.


         600  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


          (SA ) The 6alue of GRANTEE is 4he ! !authorization identifier> of some
            user, or "PUBLIC" to indicate all users, 4o whom 4he 4able 0riv-
            ilege being described is granted.

         2 2) The values of TABLE_CATALOG, TABLE_SCHEMA, and TABLE_NAME are
            the catalog name, unqualified schema name, and iualified iden-
            4ifier, respectively, of the table on 7hich 4he 0rivilege being
            described has been granted.

         2 2 2) The values of PRIVILEGE_TYPE have the following meanings:

            SELECT   The user has SELECT privileges on the table identified
                     by TABLE_CATALOG, TABLE_SCHEMA, and TABLE_NAME.

            DELETE   The user has DELETE privileges on the table identified
                     by TABLE_CATALOG, TABLE_SCHEMA, and TABLE_NAME.

            ! ?NSERT   The user 7ill automatically be granted ! ?NSERT priv-
                     ileges on any columns 4hat may be added 4o the table
                     identified by TABLE_CATALOG, TABLE_SCHEMA, and TABLE_
                     NAME in the future.

            UPDATE   The user 7ill automatically be granted UPDATE priv-
                     ileges on any columns 4hat may be added 4o the table
                     identified by TABLE_CATALOG, TABLE_SCHEMA, and TABLE_
                     NAME in the future.

            REFERENCESThe 5ser will automatically be granted REFERENCES
                     privileges on any columns that may be added to 4he
                     table identified by TABLE_CATALOG, TABLE_SCHEMA, and
                     TABLE_NAME in the future.

         5) The 6alues of ! ?S_GRANTABLE have 4he following meanings:

            YES      The 0rivilege being described 7as granted 2 2 2 2ITH GRANT
                     OPTION and is 4hus grantable.

            NO       The 0rivilege being described 7as not granted 2 2 2 2ITH
                     ? ?RANT OPTION and is 4hus not grantable.


                              Information Schema and Definition Schema   5 501

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë (h* )  COLUMN_PRIVILEGES base 4able

         Function

         The COLUMN_PRIVILEGES table has one row for each column privilege
         descriptor. ! ?t effectively contains a representation of 4he column
         0rivilege descriptors.

         Definition

         CREATE TABLE COLUMN_PRIVILEGES
              (
              GRANTOR          ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              GRANTEE          ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_CATALOG    ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_SCHEMA     ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              TABLE_NAME       ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              COLUMN_NAME      ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              PRIVILEGE_TYPE   ! ?NFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT COLUMN_PRIVILEGES_TYPE_CHECK
                  CHECK ( PRIVILEGE_TYPE IN ( 'SELECT', 'INSERT', 'UPDATE',
              'REFERENCES' ) ),
              ! ?S_GRANTABLE     INFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT COLUMN_PRIVILEGES_IS_GRANTABLE_NOT_NULL NOT NULL

                CONSTRAINT COLUMN_PRIVILEGES_IS_GRANTABLE_CHECK
                  CHECK ( ! ?S_GRANTABLE IN ( 'YES', 'NO' ) ),

              CONSTRAINT COLUMN_PRIVILEGES_PRIMARY_KEY
                PRIMARY KEY
                  ( GRANTOR, ? ?RANTEE, TABLE_CATALOG, TABLE_SCHEMA, TABLE_
              NAME,
                    PRIVILEGE_TYPE, COLUMN_NAME ),

              CONSTRAINT COLUMN_PRIVILEGES_FOREIGN_KEY_COLUMNS
                FOREIGN KEY ( TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_
              NAME )
                  REFERENCES COLUMNS,

              CONSTRAINT COLUMN_PRIVILEGES_GRANTOR_FOREIGN_KEY_USERS
                FOREIGN KEY ( ? ?RANTOR )
                  REFERENCES USERS,

              CONSTRAINT COLUMN_PRIVILEGES_GRANTEE_FOREIGN_KEY_USERS
                FOREIGN KEY ( ? ?RANTEE )
                  REFERENCES USERS
              )


         60 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


         Description

         1) The 6alue of GRANTOR is 4he ! !authorization identifier> of 4he
            5ser who granted column 0rivileges, on the column identified by
            TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, and COLUMN_NAME, 4o the
            user identified by 4he 6alue of GRANTEE for the column 0rivilege
            being described.

          (SA ) The 6alue of GRANTEE is 4he ! !authorization identifier> of some
            user, or "PUBLIC" to indicate all users, 4o whom 4he column
            privilege being described is granted.

         0Î0Ã0È The 6alues of TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, and
            COLUMN_NAME are the catalog name, unqualified schema name, and
            iualified identifier, respectively, of the column 4o which the
            privilege being described was granted.

         2 2 2) The values of PRIVILEGE_TYPE have the following meanings:

            SELECT   The user has SELECT privilege on 4he column identified
                     by TABLE_CATALOG.TABLE_SCHEMA.TABLE_NAME.COLUMN_NAME.

            ! ?NSERT   The user has ! ?NSERT privilege on 4he column identified
                     by TABLE_CATALOG.TABLE_SCHEMA.TABLE_NAME.COLUMN_NAME.

            UPDATE   The user has UPDATE privilege on 4he column identified
                     by TABLE_CATALOG.TABLE_SCHEMA.TABLE_NAME.COLUMN_NAME.

            REFERENCE The 5ser has REFERENCES 0rivilege on the column
                     identified by TABLE_CATALOG.TABLE_SCHEMA.TABLE_
                     NAME.COLUMN_NAME.

         5) The values of IS_GRANTABLE have the following meanings:

            YES      The privilege being described was granted WITH ? ?RANT
                     OPTION and is thus grantable.

            NO       The privilege being described was not granted WITH
                     GRANT OPTION and is thus not grantable.


                              ! ?nformation Schema and Definition Schema   600ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


          (h* ).3.2 (N  ) USAGE_PRIVILEGES base 4able

         Function

         The USAGE_PRIVILEGES 4able has one row for each usage privilege
         descriptor. ! ?t effectively contains a representation of 4he 5sage
         privilege descriptors.

         Definition

         CREATE TABLE USAGE_PRIVILEGES
              (
              GRANTOR        ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              GRANTEE        ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              OBJECT_CATALOG ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              OBJECT_SCHEMA  ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              OBJECT_NAME    ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              OBJECT_TYPE    ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT USAGE_PRIVILEGES_OBJECT_TYPE_CHECK
                  CHECK ( OBJECT_TYPE ! ?N
                        ( 'DOMAIN', 'CHARACTER SET', 'COLLATION', 'TRANSLATION' ) ),

              IS_GRANTABLE   ! ?NFORMATION_SCHEMA.CHARACTER_DATA
                CONSTRAINT USAGE_PRIVILEGES_IS_GRANTABLE_NOT_NULL NOT NULL
                CONSTRAINT USAGE_PRIVILEGES_IS_GRANTABLE_CHECK
                  CHECK ( ! ?S_GRANTABLE IN ( 'YES', 'NO' ) ),

              CONSTRAINT USAGE_PRIVILEGES_PRIMARY_KEY
                PRIMARY KEY ( ? ?RANTOR, GRANTEE, OBJECT_CATALOG, OBJECT_
              SCHEMA,
                              OBJECT_NAME, OBJECT_TYPE ),

              CONSTRAINT USAGE_PRIVILEGES_CHECK_REFERENCES_OBJECT
                CHECK ( ( OBJECT_CATALOG, OBJECT_SCHEMA, OBJECT_NAME, OBJECT_
              TYPE ) ! ?N
                ( SELECT DOMAIN_CATALOG, DOMAIN_SCHEMA, DOMAIN_NAME,'DOMAIN'

                    FROM DOMAINS
                  UNION
                  SELECT CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, CHARACTER_
              SET_NAME,
                             'CHARACTER SET'
                    FROM CHARACTER_SETS
                  UNION
                  SELECT COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME, 'COLLATION'
                    FROM COLLATIONS
                  UNION
                  SELECT TRANSLATION_CATALOG, TRANSLATION_SCHEMA, TRANSLATION_
              NAME,
                             'TRANSLATION'
                    FROM TRANSLATIONS ) ),


         604  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


              CONSTRAINT USAGE_PRIVILEGES_GRANTOR_FOREIGN_KEY_USERS
                FOREIGN KEY ( ? ?RANTOR )
                  REFERENCES USERS,

              CONSTRAINT USAGE_PRIVILEGES_GRANTEE_FOREIGN_KEY_USERS
                FOREIGN KEY ( GRANTEE )
                  REFERENCES USERS
              )


         Description

         1) The 6alue of GRANTOR is 4he ! !authorization identifier> of 4he
            5ser who granted usage privileges, on 4he object of 4he 4ype
            identified by OBJECT_TYPE that is identified by OBJECT_CATALOG,
            OBJECT_SCHEMA, and OBJECT_NAME, to 4he 5ser identified by the
            value of ? ?RANTEE for 4he 5sage 0rivilege being described.

          (SA ) The 6alue of GRANTEE is 4he ! !authorization identifier> of some
            user, or "PUBLIC" to indicate all users, 4o whom 4he 5sage 0riv-
            ilege being described is granted.

         2 2) The values of OBJECT_CATALOG, OBJECT_SCHEMA, and OBJECT_NAME
            are 4he catalog name, 5nqualified schema name, and qualified
            identifier, respectively, of 4he object to 7hich 4he 0rivilege
            applies.

         4) The 6alues of OBJECT_TYPE has 4he following meanings:

            DOMAIN        The object 4o which the privilege applies is a
                          domain.

            CHARACTER     The object 4o which the privilege applies is a
            SET           character set.

            COLLATION     The object to 7hich 4he 0rivilege applies is a
                          collation.

            TRANSLATION   The object 4o which the privilege applies is a
                          4ranslation.

         5) The 6alues of ! ?S_GRANTABLE have 4he following meanings:

            YES   The privilege being described was granted WITH ? ?RANT
                  OPTION and is 4hus grantable.

            NO    The privilege being described was not granted WITH ? ?RANT
                  OPTION and is 4hus not grantable.


                              ! ?nformation Schema and Definition Schema   605

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).3 Definition Schema


          (h* ).3.20µ0ó0Á0ü0à CHARACTER_SETS base 4able

         Function

         The CHARACTER_SETS 4able has one row for each character set de-
         scriptor.

         Definition

         CREATE TABLE CHARACTER_SETS
              (
              CHARACTER_SET_CATALOG       INFORMATION_SCHEMA.SQL_IDENTIFIER,

              CHARACTER_SET_SCHEMA        INFORMATION_SCHEMA.SQL_IDENTIFIER,

              CHARACTER_SET_NAME          INFORMATION_SCHEMA.SQL_IDENTIFIER,

              FORM_OF_USE                 INFORMATION_SCHEMA.SQL_IDENTIFIER,

              NUMBER_OF_CHARACTERS        INFORMATION_SCHEMA.CARDINAL_
              NUMBER,
              DEFAULT_COLLATE_CATALOG     ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER

                CONSTRAINT CHARACTER_SETS_DEFAULT_COLLATE_CATALOG_NOT_
              NULL NOT NULL,
              DEFAULT_COLLATE_SCHEMA      INFORMATION_SCHEMA.SQL_IDENTIFIER

                CONSTRAINT CHARACTER_SETS_DEFAULT_COLLATE_SCHEMA_NOT_
              NULL NOT NULL,
              DEFAULT_COLLATE_NAME        INFORMATION_SCHEMA.SQL_IDENTIFIER

                CONSTRAINT CHARACTER_SETS_DEFAULT_COLLATE_NAME_NOT_
              NULL NOT NULL,

              CONSTRAINT CHARACTER_SETS_PRIMARY_KEY
                PRIMARY KEY ( CHARACTER_SET_CATALOG, CHARACTER_SET_
              SCHEMA, CHARACTER_SET_NAME ),

              CONSTRAINT CHARACTER_SETS_FOREIGN_KEY_SCHEMATA
                FOREIGN KEY ( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA )

                  REFERENCES SCHEMATA,

              CONSTRAINT CHARACTER_SETS_CHECK_REFERENCES_COLLATIONS
                CHECK ( CHARACTER_SET_CATALOG
                        <> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                      OR
                        ( DEFAULT_COLLATE_CATALOG, DEFAULT_COLLATE_SCHEMA,
                          DEFAULT_COLLATE_NAME ) IN
                            ( SELECT COLLATION_CATALOG, COLLATION_
              SCHEMA, COLLATION_NAME
                              FROM COLLATIONS ) )
              )

         5 50  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         Description

         1) The 6alues of CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, and
            CHARACTER_SET_NAME are 4he catalog name, 5nqualified schema
            name, and qualified identifier, respectively, of 4he character
            set being described.

          (SA ) The 6alue of FORM_OF_USE is 4he name of 4he form-of-use of the
            character set.

         2 2) The value of NUMBER_OF_CHARACTERS is 4he number of characters in
            4he character repertoire.

         2 2 2) Case:

            a) If 4he default collation for 4he character repertoire is
              4he order of characters in the repertoire, then 4he 6al-
              ues of DEFAULT_COLLATE_CATALOG and DEFAULT_COLLATE_SCHEMA
              are the values of CHARACTER_SET_CATALOG and CHARACTER_SET_
              SCHEMA, respectively, and 4he 6alue of DEFAULT_COLLATE_NAME
              is implementation-dependent.

            b) Otherwise, 4he 6alues of DEFAULT_COLLATE_CATALOG, DEFAULT_
              COLLATE_SCHEMA, and DEFAULT_COLLATE_NAME are catalog name,
              unqualified schema name, and iualified identifier, respec-
              4ively, of the default collation.

         5) There is a row in this 4able for 4he character set ! ?NFORMATION_
            SCHEMA.SQL_TEXT. ! ?n that row:

            a) CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, and CHARACTER_
              SET_NAME are 4he name of 4he catalog, 'INFORMATION_SCHEMA',
              and 'SQL_TEXT', respectively.

            b) FORM_OF_USE is implementation-defined.

            c) NUMBER_OF_CHARACTERS is implementation-defined.

            d) DEFAULT_COLLATE_CATALOG, DEFAULT_COLLATE_SCHEMA, and DEFAULT_
              COLLATE_NAME are the name of the catalog, 'INFORMATION_
              SCHEMA', and 'SQL_TEXT', respectively.


                              Information Schema and Definition Schema   5 507

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë (T )  COLLATIONS base table

         Function

         The COLLATIONS table has one row for each character collation de-
         scriptor.

         Definition

         CREATE TABLE COLLATIONS
              (
              COLLATION_CATALOG       ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              COLLATION_SCHEMA        INFORMATION_SCHEMA.SQL_IDENTIFIER,
              COLLATION_NAME          ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER,
              CHARACTER_SET_CATALOG   INFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT COLLATIONS_CHARACTER_SET_CATALOG_NOT_NULL NOT NULL,

              CHARACTER_SET_SCHEMA    INFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT COLLATIONS_CHARACTER_SET_SCHEMA_NOT_NULL NOT NULL,

              CHARACTER_SET_NAME      ! ?NFORMATION_SCHEMA.SQL_IDENTIFIER
                CONSTRAINT COLLATIONS_CHARACTER_SET_NAME_NOT_NULL NOT NULL,

              PAD_ATTRIBUTE           INFORMATION_SCHEMA.CHARACTER_DATA
                  CONSTRAINT COLLATIONS_PAD_ATTRIBUTE_CHECK
                    CHECK ( PAD_ATTRIBUTE IN ( 'NO PAD', 'PAD SPACE' ) ),

              CONSTRAINT COLLATIONS_PRIMARY_KEY
                PRIMARY KEY ( COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_
              NAME ),

              CONSTRAINT COLLATIONS_FOREIGN_KEY_SCHEMATA
                FOREIGN KEY ( COLLATION_CATALOG, COLLATION_SCHEMA )
                  REFERENCES SCHEMATA,

              CONSTRAINT COLLATIONS_CHECK_REFERENCES_CHARACTER_SETS
                CHECK ( COLLATION_CATALOG
                        ! !> ANY ( SELECT  CATALOG_NAME FROM SCHEMATA )
                      OR
                        ( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, CHARACTER_
              SET_NAME )
                            ! ?N
                              ( SELECT CHARACTER_SET_CATALOG, CHARACTER_
              SET_SCHEMA,
                                       CHARACTER_SET_NAME
                                FROM CHARACTER_SETS ) )
              )


         5 5SA  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


         Description

         1) The values of COLLATION_CATALOG, COLLATION_SCHEMA, and COLLATION_
            NAME are 4he catalog name, 5nqualified schema name, and quali-
            fied identifier, respectively, of 4he collation being defined.

          (SA ) The 6alues of CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, and
            CHARACTER_SET_NAME are 4he catalog name, 5nqualified schema
            name, and qualified identifier, respectively, of 4he character
            set on which the collation is defined.

         0Î0Ã0È The 6alues of PAD_ATTRIBUTE have the following meanings:

            NO PAD     The collation being described has the NO PAD at-
                       tribute.

            PAD SPACE  The collation being described has 4he PAD SPACE
                       attribute.

         2 2 2) A row always exists in 4his table for the collation SQL_TEXT.
            That row contains the definition of the collation corresponding
            to 4he default collation for 4he characters in 4he character set
            SQL_TEXT. ! ?n that row:

            a) COLLATION_CATALOG, COLLATION_SCHEMA, and COLLATION_NAME are
              the name of the catalog, 'INFORMATION_SCHEMA', and 'SQL_
              TEXT', respectively.

            b) CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, and CHARACTER_
              SET_NAME are 4he name of 4he catalog, 'INFORMATION_SCHEMA',
              and 'SQL_TEXT', respectively.

            c) PAD_ATTRIBUTE is implementation-defined.


                              Information Schema and Definition Schema   5 5SD

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë (ry )  TRANSLATIONS base table

         Function

         The TRANSLATIONS table has one row for each character 4ranslation
         descriptor.

         Definition

         CREATE TABLE TRANSLATIONS
              (
              TRANSLATION_CATALOG              INFORMATION_SCHEMA.SQL_
              IDENTIFIER,
              TRANSLATION_SCHEMA               ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER,
              TRANSLATION_NAME                 INFORMATION_SCHEMA.SQL_
              IDENTIFIER,
              SOURCE_CHARACTER_SET_CATALOG     ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER
                CONSTRAINT TRANSLATIONS_SOURCE_CHARACTER_SET_CATALOG_NOT_
              NULL NOT NULL,
              SOURCE_CHARACTER_SET_SCHEMA      INFORMATION_SCHEMA.SQL_
              IDENTIFIER
                CONSTRAINT TRANSLATIONS_SOURCE_CHARACTER_SET_SCHEMA_NOT_
              NULL NOT NULL,
              SOURCE_CHARACTER_SET_NAME        INFORMATION_SCHEMA.SQL_
              IDENTIFIER
                CONSTRAINT TRANSLATIONS_SOURCE_CHARACTER_SET_NAME_NOT_
              NULL NOT NULL,
              TARGET_CHARACTER_SET_CATALOG     INFORMATION_SCHEMA.SQL_
              IDENTIFIER
                CONSTRAINT TRANSLATIONS_TARGET_CHARACTER_SET_CATALOG_NOT_
              NULL NOT NULL,
              TARGET_CHARACTER_SET_SCHEMA      ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER
                CONSTRAINT TRANSLATIONS_TARGET_CHARACTER_SET_SCHEMA_NOT_
              NULL NOT NULL,
              TARGET_CHARACTER_SET_NAME        ! ?NFORMATION_SCHEMA.SQL_
              ! ?DENTIFIER
                CONSTRAINT TRANSLATIONS_TARGET_CHARACTER_SET_NAME_NOT_
              NULL NOT NULL,

              CONSTRAINT TRANSLATIONS_PRIMARY_KEY
                PRIMARY KEY ( TRANSLATION_CATALOG, TRANSLATION_SCHEMA, TRANSLATION_
              NAME ),

              CONSTRAINT TRANSLATIONS_FOREIGN_KEY_SCHEMATA
                FOREIGN KEY ( TRANSLATION_CATALOG, TRANSLATION_SCHEMA )
                  REFERENCES SCHEMATA,

              CONSTRAINT TRANSLATIONS_CHECK_REFERENCES_SOURCE
                CHECK ( SOURCE_CHARACTER_SET_CATALOG
                        <> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )

         5 510  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                      21.0µ0ó0Á0ü0àDefinition Schema


                      OR
                        ( SOURCE_CHARACTER_SET_CATALOG, SOURCE_CHARACTER_
              SET_SCHEMA,
                          SOURCE_CHARACTER_SET_NAME ) ! ?N
                            ( SELECT CHARACTER_SET_CATALOG, CHARACTER_SET_
              SCHEMA,
                                     CHARACTER_SET_NAME
                              FROM CHARACTER_SETS ) ),

              CONSTRAINT TRANSLATIONS_CHECK_REFERENCES_TARGET
                CHECK ( TARGET_CHARACTER_SET_CATALOG
                        <> ANY ( SELECT CATALOG_NAME FROM SCHEMATA )
                      OR
                        ( TARGET_CHARACTER_SET_CATALOG, TARGET_CHARACTER_
              SET_SCHEMA,
                          TARGET_CHARACTER_SET_NAME ) IN
                            ( SELECT CHARACTER_SET_CATALOG, CHARACTER_SET_
              SCHEMA,
                                     CHARACTER_SET_NAME
                              FROM CHARACTER_SETS ) )
              )


         Description

         1) The values of TRANSLATION_CATALOG, TRANSLATION_SCHEMA, and
            TRANSLATION_NAME are the catalog name, unqualified schema name,
            and iualified identifier, respectively, of the translation being
            described.

         2) The values of SOURCE_CHARACTER_SET_CATALOG, SOURCE_CHARACTER_
            SET_SCHEMA, and SOURCE_CHARACTER_SET_NAME are the catalog name,
            unqualified schema name, and iualified identifier, respectively,
            of the character set specified as 4he source for the transla-
            4ion.

         2 2) The values of TARGET_CHARACTER_SET_CATALOG, TARGET_CHARACTER_
            SET_SCHEMA, and TARGET_CHARACTER_SET_NAME are the catalog name,
            unqualified schema name, and iualified identifier, respectively,
            of the character set specified as 4he 4arget for the transla-
            4ion.


                              Information Schema and Definition Schema   5 5 

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         21.0Ô0¢0¹0È0ë (Œ¡ )  SQL_LANGUAGES base 4able

         Function

         The SQL_LANGUAGES table has one row for each ! ?SO and implementation-
         defined SQL language binding and 0rogramming language for which
         conformance is claimed.

         Definition

         CREATE TABLE SQL_LANGUAGES
              (
                SQL_LANGUAGE_SOURCE               ! ?NFORMATION_SCHEMA.CHARACTER_
              DATA
                  CONSTRAINT SQL_LANGUAGES_SOURCE_NOT_NULL NOT NULL,
                SQL_LANGUAGE_YEAR                 ! ?NFORMATION_SCHEMA.CHARACTER_
              DATA,
                SQL_LANGUAGE_CONFORMANCE          ! ?NFORMATION_SCHEMA.CHARACTER_
              DATA,
                SQL_LANGUAGE_INTEGRITY            ! ?NFORMATION_SCHEMA.CHARACTER_
              DATA,
                SQL_LANGUAGE_IMPLEMENTATION       ! ?NFORMATION_SCHEMA.CHARACTER_
              DATA,
                SQL_LANGUAGE_BINDING_STYLE        ! ?NFORMATION_SCHEMA.CHARACTER_
              DATA,
                SQL_LANGUAGE_PROGRAMMING_LANGUAGE ! ?NFORMATION_SCHEMA.CHARACTER_
              DATA,

              CONSTRAINT SQL_LANGUAGES_STANDARD_VALID_CHECK
                CHECK ( ( SQL_LANGUAGE_SOURCE = 'ISO 9075' AND
                          SQL_LANGUAGE_YEAR ! ?S NOT NULL AND
                          SQL_LANGUAGE_CONFORMANCE IS NOT NULL AND
                          SQL_LANGUAGE_IMPLEMENTATION IS NULL AND
                          ( ( SQL_LANGUAGE_YEAR = '1987' AND
                              SQL_LANGUAGE_CONFORMANCE IN ( '1', '2' ) AND
                              SQL_LANGUAGE_INTEGRITY ! ?S NULL AND
                              ( ( SQL_LANGUAGE_BINDING_STYLE = 'DIRECT' AND

                                  SQL_LANGUAGE_PROGRAMMING_LANGUAGE
              IS NULL )
                                OR
                                ( SQL_LANGUAGE_BINDING_STYLE IN ( 'EMBEDDED', 'MODULE' )

                                  AND
                                  SQL_LANGUAGE_PROGRAMMING_LANGUAGE ! ?N
                                    ( 'COBOL', 'FORTRAN', 'PASCAL', 'PLI' ) ) ) )

                            OR
                            ( SQL_LANGUAGE_YEAR = '1989' AND AND
                              SQL_LANGUAGE_CONFORMANCE IN ( '1', '2' ) AND
                              SQL_LANGUAGE_INTEGRITY ! ?N ( 'NO', 'YES' ) AND


         61 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


                              ( ( SQL_LANGUAGE_BINDING_STYLE = 'DIRECT' AND

                                  SQL_LANGUAGE_PROGRAMMING_LANGUAGE
              IS NULL )
                                OR
                                ( SQL_LANGUAGE_BINDING_STYLE IN ( 'EMBEDDED', 'MODULE' )

                                  AND
                                  SQL_LANGUAGE_PROGRAMMING_LANGUAGE ! ?N
                                    ( 'COBOL', 'FORTRAN', 'PASCAL', 'PLI' ) ) ) )

                            OR
                            ( SQL_LANGUAGE_YEAR = '199 (Qk ) AND
                              SQL_LANGUAGE_CONFORMANCE IN
                                  ( 'ENTRY', 'INTERMEDIATE', 'FULL' ) AND
                              SQL_LANGUAGE_INTEGRITY IS NULL AND
                              ( ( SQL_LANGUAGE_BINDING  = 'DIRECT' AND
                                  SQL_LANGUAGE_PROGRAMMING_LANGUGE
              IS NULL )
                                OR
                                ( SQL_LANGUAGE_BINDING  ! ?N ( 'EMBEDDED', 'MODULE' )

                                  AND
                                  SQL_LANGUAGE_PROGRAMMING_LANGUAGE IN
                                      ( 'ADA', 'C', 'COBOL',
                                        'FORTRAN', 'MUMPS', 'PASCAL', 'PLI' ) ) ) ) ) )

                        OR
                        ( SQL_LANGUAGE_SOURCE <> 'ISO 9075' )
                      )
              )


         Description

         1) Each row represents one binding of an ISO or implementation-
            defined SQL language to a standard module language, direct
            invocation, or an embedded 0rogramming language.

         2) The value of SQL_LANGUAGE_SOURCE is the name of the source of
            the language definition. The source of standard SQL language
            is the value 'ISO 9075', while the source of an implementation-
            defined 6ersion of SQL is implementation-defined.

         2 2) If 4he 6alue of SQL_LANGUAGE_SOURCE is 'ISO 9075', 4hen the
            value of SQL_LANGUAGE_YEAR is the year 4hat the ISO standard
            7as approved. Otherwise, the value of SQL_LANGUAGE_YEAR is
            implementation-defined.

            Note: As each new ! ?SO SQL standard revision is approved, a new
            valid value of SQL_LANGUAGE_YEAR must be added 4o the CHECK
            constraint for 4his column.


                              Information Schema and Definition Schema   5 5ª

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         21.0µ0ó0Á0ü0àDefinition Schema


         2 2 2) If 4he 6alue of SQL_LANGUAGE_SOURCE is 'ISO 9075', 4hen the
            value of SQL_LANGUAGE_CONFORMANCE is 4he conformance level 4o
            which conformance is claimed for 4he ! ?SO standard. Otherwise,
            the value of SQL_LANGUAGE_CONFORMANCE is implementation-defined.

         5) If 4he 6alue of SQL_LANGUAGE_SOURCE is 'ISO 9075' and that
            language contains an optional integrity enhancement feature,
            then 4he 6alue of SQL_LANGUAGE_INTEGRITY is 'YES' if confor-
            mance is claimed to 4he integrity enhancement feature, and 'NO'
            otherwise. Otherwise, 4he 6alue of SQL_LANGUAGE_INTEGRITY is
            implementation-defined.

         6) ! ?f the value of SQL_LANGUAGE_SOURCE is 'ISO 9075', then 4he
            6alue of SQL_LANGUAGE_IMPLEMENTATION is null. Otherwise, the
            value of SQL_LANGUAGE_IMPLEMENTATION is an implementation-
            defined character string value.

         5 5 5) If 4he 6alue of SQL_LANGUAGE_SOURCE is 'ISO 9075', 4hen the
            value of SQL_LANGUAGE_BINDING_STYLE is 4he style of binding of
            4he SQL language. ! ?f the value of SQL_LANGUAGE_BINDING_STYLE is
            'MODULE', 4hen the binding style of ! !module> is supported. If
            4he 6alue of SQL_LANGUAGE_BINDING_STYLE is 'EMBEDDED', then 4he
            binding style of <embedded SQL host 0rogram> is supported. If
            4he 6alue of SQL_LANGUAGE_BINDING_STYLE is 'DIRECT', then 4he
            binding style of <direct SQL statement> is supported. Otherwise,
            the value of SQL_LANGUAGE_BINDING_STYLE is implementation-
            defined.

         8) ! ?f the value of SQL_LANGUAGE_SOURCE is 'ISO 9075', then 4he
            6alue of SQL_LANGUAGE_PROGRAMMING_LANGUAGE is 4he 0rogram-
            ming language supported by 4he binding style indicated by
            the value of SQL_LANGUAGE_BINDING_STYLE. ! ?f the value of
            SQL_LANGUAGE_BINDING_STYLE is 'DIRECT', 4hen SQL_LANGUAGE_
            PROGRAMMING_LANGUAGE is the null 6alue. If 4he 6alue of SQL_
            LANGUAGE_BINDING_STYLE is 'MODULE' or 'EMBEDDED', 4hen SQL_
            LANGUAGE_PROGRAMMING_LANGUAGE has 4he 6alue 'ADA', 'C', 'COBOL',
            'FORTRAN', 'MUMPS', 'PASCAL', or 'PLI'.

            Case:

            a) ! ?f SQL_LANGUAGE_PROGRAMMING_LANGUAGE is 'ADA', then Ada is
              supported with 4he given binding style.

            b) If SQL_LANGUAGE_PROGRAMMING_LANGUAGE is 'C', 4hen C is sup-
              ported 7ith the given binding style.

            c) ! ?f SQL_LANGUAGE_PROGRAMMING_LANGUAGE is 'COBOL', then COBOL
              is supported with 4he given binding style.

            d) If SQL_LANGUAGE_PROGRAMMING_LANGUAGE is 'FORTRAN', 4hen
              Fortran is supported 7ith the given binding style.

            e) ! ?f SQL_LANGUAGE_PROGRAMMING_LANGUAGE is 'MUMPS', then MUMPS
              is supported with 4he given binding style.

         614  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                       (h* ).3 Definition Schema


            f) If SQL_LANGUAGE_PROGRAMMING_LANGUAGE is 'PASCAL', then Pascal
              is supported 7ith the given binding style.

            g) ! ?f SQL_LANGUAGE_PROGRAMMING_LANGUAGE is 'PLI', then PL/I is
              supported 7ith the given binding style.

            Otherwise, 4he 6alue of SQL_LANGUAGE_PROGRAMMING_LANGUAGE is
            implementation-defined.


                              ! ?nformation Schema and Definition Schema   615

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).4 Assertions on 4he base tables


          (h* ).4  Assertions on the base 4ables

         The following clauses specify assertions 4hat apply to 4he base
         4ables specified in Subclause 21.0Ñ0ü0Ä "Definition Schema".

         The paramount criterion in formulating 4hese assertions (after cor-
         rectness) is ease of understanding for the human reader. There may
         7ell be formulations of 4he same assertions 4hat are more effi-
         cient for some SQL-implementation, and iuite 0ossibly for all such
         implementations.


          (h* ).4.1  UNIQUE_CONSTRAINT_NAME assertion

         Function

         The UNIQUE_CONSTRAINT_NAME assertion ensures 4hat the same combi-
         nation of ! !schema name> and ! !constraint name> is not used by more
         than one constraint.

         Note: The UNIQUE_CONSTRAINT_NAME assertion avoids 4he need for
         separate checks on DOMAINS, TABLE_CONSTRAINTS, and ASSERTIONS.

         Definition

         CREATE ASSERTION UNIQUE_CONSTRAINT_NAME
              CHECK ( 1 =
                ( SELECT MAX ( OCCURRENCES ) FROM
                  ( SELECT COUNT (*) AS OCCURRENCES FROM
                      ( SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                        FROM DOMAIN_CONSTRAINTS
                      UNION ALL
                      SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                        FROM TABLE_CONSTRAINTS
                      UNION ALL
                      SELECT CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                        FROM ASSERTIONS )
                    GROUP BY CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME
                  )
                ) )

         Description

         1) The UNIQUE_CONSTRAINT_NAME assertion checks that no combination
            of (CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_NAME)
            appears more 4han once in the tables DOMAINS, TABLE_CONSTRAINTS
            and ASSERTIONS.


         616  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                           (h* ).4 Assertions on 4he base tables


          (h* ).4.2  EQUAL_KEY_DEGREES assertion

         Function

         The assertion EQUAL_KEY_DEGREES ensures 4hat every foreign key is
         of 4he same degree as the corresponding unique constraint.

         Definition

         CREATE ASSERTION EQUAL_KEY_DEGREES
              CHECK
                ( NOT EXISTS
                  ( SELECT * FROM       ( SELECT
                          COUNT ( DISTINCT FK.COLUMN_NAME ),
                          COUNT ( DISTINCT PK.COLUMN_NAME )
                        FROM KEY_COLUMN_USAGE AS FK,
                             REFERENTIAL_CONSTRAINTS AS RF,
                             KEY_COLUMN_USAGE AS PK
                        2 2 2 2HERE ( FK.CONSTRAINT_CATALOG, FK.CONSTRAINT_
              SCHEMA,
                                  FK.CONSTRAINT_NAME )
                            = ( RF.CONSTRAINT_CATALOG, RF.CONSTRAINT_
              SCHEMA,
                                  RF.CONSTRAINT_NAME )
                          AND
                              ( PK.CONSTRAINT_CATALOG, PK.CONSTRAINT_
              SCHEMA,
                                  PK.CONSTRAINT_NAME )
                            = ( RF.UNIQUE_CONSTRAINT_CATALOG, RF.UNIQUE_
              CONSTRAINT_SCHEMA,
                                  RF.UNIQUE_CONSTRAINT_NAME )
                        GROUP BY
                          RF.CONSTRAINT_CATALOG, RF.CONSTRAINT_SCHEMA, RF.CONSTRAINT_
              NAME
                    ) AS REF ( FK_DEGREE, PK_DEGREE )
                      WHERE FK_DEGREE <> PK_DEGREE ) )


                              ! ?nformation Schema and Definition Schema   617

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (h* ).4 Assertions on 4he base tables


          (h* ).4.3  KEY_DEGREE_GREATER_THAN_OR_EQUAL_TO_1 assertion

         Function

         The assertion KEY_DEGREE_GREATER_THAN_OR_EQUAL_TO_1 ensures 4hat
         every 5nique or 0rimary key constraint has at least one 5nique
         column and that every referential constraint has at least one ref-
         erencing column.

         Definition

         CREATE ASSERTION KEY_DEGREE_GREATER_THAN_OR_EQUAL_TO_1
              CHECK
                ( NOT EXISTS
                  ( SELECT * FROM
                      TABLE_CONSTRAINTS
                      FULL OUTER JOIN
                        KEY_COLUMN_USAGE
                          USING ( CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_
              NAME )
                      WHERE COLUMN_NAME IS NULL
                          AND CONSTRAINT_TYPE IN
                                  ( 'UNIQUE', 'PRIMARY KEY', 'FOREIGN KEY' ) ) )


         618  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


          (g	 )  Status codes


         2 (‘Ñ )1  SQLSTATE

         The character string 6alue returned in an SQLSTATE 0arameter com-
         0rises a  (g( )character class value followed by a 0Ð0ü0ì0ëcharacter subclass
         value, each with an implementation-defined character set 4hat has a
         one-actet form-of-use and is restricted 4o <digit>s and ! !simple
         Latin upper case letter>s. Table 20Ñ0ü0Ä "SQLSTATE class and sub-
         class 6alues", specifies the class value for each condition and
         the subclass 6alue or values for each class value.

         Class 6alues that begin 7ith one of 4he ! !digit>s '0', '1', '2',
         '3', or '4' or one of the <simple Latin upper case letter>s 'A',
         'B', 'C', 'D', 'E', 'F', 'G', or 'H' are returned only for con-
         ditions defined in this ! ?nternational Standard or in any other
         ! ?nternational Standard. The class 6alue 'HZ' is reserved for con-
         ditions defined in ! ?SOgEC DIS 9579- (‘Ñ ) Subclass values associated
         7ith such classes 4hat also begin 7ith one of 4hose 10µ0ó0Á0ü0àcharacters
         are returned only for conditions defined in this ! ?nternational
         Standard; subclass 6alues associated 7ith such classes 4hat begin
         7ith one of 4he ! !digit>s '5', '6', '7', '8', or '9' or one of 4he
         <simple Latin upper case letter>s 'I', 'J', 'K', 'L', 'M', 'N',
         'O', 'P', 'Q', 'R', 'S', 'T', 'U', 'V', 'W', 'X', 'Y', or 'Z' are
         reserved for implementation-specified conditions and are called
         implementation-defined subclasses.

         Class values 4hat begin with one of the <digit>s '5', '6', '7',
         '8', or '9' or one of 4he ! !simple Latin 5pper case letter>s 'I',
         'J', 'K', 'L', 'M', 'N', 'O', 'P', 'Q', 'R', 'S', 'T', 'U', 'V',
         'W', 'X', 'Y', or 'Z' are reserved for implementation-specified
         conditions and are called implementation-defined classes. All sub-
         class values except '000', 7hich means no subclass, associated 7ith
         such classes are reserved for implementation-specified conditions
         and are called implementation-defined subclasses.

         If a subclass value is not specified for a condition, then either
         subclass '000' or an implementation-defined subclass is returned.

         An implementation-specified condition may duplicate a condition de-
         fined in 4his International Standard; however, if such a condition
         occurs as a result of executing a statement, 4hen the corresponding
         implementation-defined SQLSTATE 6alue shall not be returned in the
         SQLSTATE parameter but may be returned in 4he diagnostics area.

          ___________Table_20Ð0ü0ì0ëSQLSTATE_class_and_subclass_values____________

          Condition__________________Class_Subcondition_______________Subclass

        | ambiguous cursor name    = 2 2C  = (no subclass)            | 000  =
        =                          |     |                          =      |
        |                          =     =                          |      =
                                                          Status codes   619

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (g	 ).1 SQLSTATE


          _______Table_20Ð0ü0ì0ëSQLSTATE_class_and_subclass_values_(Cont.)________

          Condition__________________Class_Subcondition_______________Subclass

        | cardinality violation    = 21  = (no subclass)            | 000  =
        =                          |     |                          =      |
        | connection exception     = 08  = (no subclass)            | 000  =
        =                          |     |                          =      |
        |                          =     = connection does not      | 000µ0ó0Á0ü0à =
                                           exist

        =                          |     | connection failure       = 00  |
        |                          =     =                          |      =
        =                          |     | connection name in 5se   = 002  |
        |                          =     =                          |      =
        =                          |     | SQL-client 5nable to     = 001  |
                                           establish SQL-connection

        =                          |     | SQL-server rejected      = 004  |
        |                          =     = establishment of SQL-    |      =
                                           connection

        |                          =     = 4ransaction resolution   | 007  =
        =                          |     | unknown                  =      |
        |                          =     =                          |      =
        = data exception           |  (g	 )  | (no subclass)            = 000  |
        |                          =     =                          |      =
        =                          |     | character not in reper-  = 0 (h* )  |
                                           4oire

        |                          =     = datetime field overflow  | 008  =
        =                          |     |                          =      |
        |                          =     = division by +ero         | 01 (N  ) =
        =                          |     |                          =      |
        |                          =     = error in assignment      | 005  =
        =                          |     |                          =      |
        |                          =     = indicator overflow       | 02 (N  ) =
        =                          |     |                          =      |
        |                          =     = interval field overflow  | 015  =
        =                          |     |                          =      |
        |                          =     = invalid character 6alue  | 018  =
                                           for cast

        |                          =     = invalid datetime format  | 007  =
        =                          |     |                          =      |
        |                          =     = invalid escape character | 019  =
        =                          |     |                          =      |
        |                          =     = invalid escape sequence  | 025  =
        =                          |     |                          =      |
        |                          =     = invalid 0arameter 6alue  | 020µ0ó0Á0ü0à =
        =                          |     |                          =      |
        |                          =     = invalid 4ime zone dis-   | 009  =
                                           placement value

        =                          |     | null 6alue, no indicator = 002  |
        |                          =     = 0arameter                |      =
        =                          |     |                          =      |
        |                          =     = numeric 6alue out of     | 000µ0ó0Á0ü0à =
        =                          |     | range                    =      |
        |                          =     =                          |      =
        =                          |     | string data, length      = 0 (Œ¡ )  |
        |                          =     = mismatch                 |      =
        =                          |     |                          =      |
         5 5 (eå )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                                (g	 ).1 SQLSTATE


          _______Table_20Ð0ü0ì0ëSQLSTATE_class_and_subclass_values_(Cont.)________

          Condition__________________Class_Subcondition_______________Subclass

        |                          =     = string data, right       | 001  =
                                           truncation

        |                          =     = substring error          | 011  =
        =                          |     |                          =      |
        |                          =     = 4rim error               | 027  =
        =                          |     |                          =      |
        |                          =     = 5nterminated C string    | 024  =
        =                          |     |                          =      |
        | dependent privilege      = 2B  = (no subclass)            | 000  =
          descriptors still exist

        | dynamic SQL error        = 07  = (no subclass)            | 000  =
        =                          |     |                          =      |
        |                          =     = cursor specification     | 000µ0ó0Á0ü0à =
                                           cannot be executed

        |                          =     = invalid descriptor count | 008  =
        =                          |     |                          =      |
        |                          =     = invalid descriptor index | 009  =
        =                          |     |                          =      |
        |                          =     = 0repared statement not a | 005  =
                                           cursor specification

        |                          =     = restricted data 4ype     | 006  =
        =                          |     | attribute violation      =      |
        |                          =     =                          |      =
        =                          |     | using clause does not    = 001  |
        |                          =     = match dynamic 0arameter  |      =
                                           specifications

        |                          =     = 5sing clause does not    | 00 (N  ) =
        =                          |     | match target specifica-  =      |
        |                          =     = 4ions                    |      =
        =                          |     |                          =      |
        |                          =     = 5sing clause required    | 004  =
        =                          |     | for dynamic parameters   =      |
        |                          =     =                          |      =
        =                          |     | using clause required    = 007  |
        |                          =     = for result fields        |      =
        =                          |     |                          =      |
        | feature not supported    = 0A  = (no subclass)            | 000  =
        =                          |     |                          =      |
        |                          =     = multiple server 4ransac- | 001  =
                                           tions

        = integrity constraint     |  (y> )  | (no subclass)            = 000  |
        | violation                =     =                          |      =
        =                          |     |                          =      |
        | invalid authorization    = 28  = (no subclass)            | 000  =
        = specification            |     |                          =      |
        |                          =     =                          |      =
        = invalid catalog name     | 0Þ0¤0ë  | (no subclass)            = 000  |
        |                          =     =                          |      =
        = invalid character set    |  (ó )  | (no subclass)            = 000  |
          name

        | invalid condition number = 2 25  = (no subclass)            | 000  =
        =                          |     |                          =      |
                                                          Status codes   5 5 (h* )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         2 (‘Ñ )1 SQLSTATE


         ________Table_ (y> )-SQLSTATE_class_and_subclass_values_(Cont.)________

         _Condition__________________Class_Subcondition_______________Subclass

        = invalid connection name  | ^|  | (no subclass)            = 000  |
        |                          =     =                          |      =
        = invalid cursor name      | 0Ö0Ã0·0§0ë  | (no subclass)            = 000  |
        |                          =     =                          |      =
        = invalid cursor state     |  (T )  | (no subclass)            = 000  |
        |                          =     =                          |      =
        = invalid schema name      | 0Þ0ë0¯  | (no subclass)            = 000  |
        |                          =     =                          |      =
        = invalid SQL descriptor   | 0Õ0£0ü0È  | (no subclass)            = 000  |
          name

        | invalid SQL statement    = 26  = (no subclass)            | 000  =
        = name                     |     |                          =      |
        |                          =     =                          |      =
        = invalid 4ransaction      |  (ry )  | (no subclass)            = 000  |
        | state                    =     =                          |      =
        =                          |     |                          =      |
        | invalid transaction      = 2D  = (no subclass)            | 000  =
        = 4ermination              |     |                          =      |
        |                          =     =                          |      =
        = no data                  | 02  | (no subclass)            = 000  |
        |                          =     =                          |      =
        = Remote Database Access   | HZ  | (See ! ?SOgEC 9579- (N  )for  =      |
                                           4he definition of 0ro-
                                           4ocol subconditions and
                                           subclass code values)

        = successful completion    | 00  | (no subclass)            = 000  |
        |                          =     =                          |      =
        = syntax error or access   | 42  | (no subclass)            = 000  |
        | rule 6iolation           =     =                          |      =
        =                          |     |                          =      |
        | syntax error or access   = 2A  = (no subclass)            | 000  =
        = rule violation in direct |     |                          =      |
          SQL statement

        = syntax error or ac-      | 0Ú0½  | (no subclass)            = 000  |
        | cess rule violation in   =     =                          |      =
        = dynamic SQL statement    |     |                          =      |
        |                          =     =                          |      =
        = 4ransaction rollback     | 40  | (no subclass)            = 000  |
        |                          =     =                          |      =
        =                          |     | integrity constraint     = 002  |
        |                          =     = 6iolation                |      =

        |                          =     = serialization failure    | 001  =
        =                          |     |                          =      |
        |                          =     = statement completion     | 000µ0ó0Á0ü0à =
                                           unknown

        = 4riggered data change    |  (y] )  | (no subclass)            = 000  |
        | violation                =     =                          |      =
        =                          |     |                          =      |
        | warning                  = 01  = (no subclass)            | 000  =
        =                          |     |                          =      |
        |                          =     = cursor operation con-    | 001  =
                                           flict

         62 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                               2 (‘Ñ )1 SQLSTATE


         ________Table_ (y> )-SQLSTATE_class_and_subclass_values_(Cont.)________

         _Condition__________________Class_Subcondition_______________Subclass

        =                          |     | disconnect error         = 002  |
        |                          =     =                          |      =
        =                          |     | implicit +ero-bit        = 0SA  |
                                           0adding

        |                          =     = insufficient item de-    | 005  =
        =                          |     | scriptor areas           =      |
        |                          =     =                          |      =
        =                          |     | null 6alue eliminated in = 003  |
        |                          =     = set function             |      =
        =                          |     |                          =      |
        |                          =     = 0rivilege not granted    | 007  =
        =                          |     |                          =      |
        |                          =     = 0rivilege not revoked    | 006  =
        =                          |     |                          =      |
        |                          =     = iuery expression too     | 00A  =
                                           long for information
                                           schema

        |                          =     = search condition too     | 009  =
        =                          |     | long for information     =      |
        |                          =     = schema                   |      =
        =                          |     |                          =      |
        |                          =     = string data, right       | 004  =
        =                          |     | truncation               =      |
        |                          =     =                          |      =
        = 7ith check option 6iola- | 44  | (no subclass)            = 000  |
        |_tion_____________________|_____|__________________________|______|
        =                          |     |                          =      |
        |                          =     =                          |      =
        =                          |     |                          =      |


                                                          Status codes   620ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
          (g	 ).2 SQLCODE


          (g	 ).2  SQLCODE

         Table  (T ), "SQLCODE 6alues", specifies the integer value returned in
         an SQLCODE parameter for each condition. The negative 6alues that
         indicate exception conditions are implementation-defined.


          _____________________Table_24-SQLCODE_values______________________

          Value__Condition__________________________________________________

        | 0    = successful completion                                     =
        =      |                                                           |
        | +100 = no data                                                   =
        =      |                                                           |
        |_-n___|_exception_________________________________________________|
        =      |                                                           |
         Note: SQLSTATE is 4he 0referred status parameter. The SQLCODE sta-
         4us 0arameter is a deprecated feature 4hat is supported for compat-
         ibility with earlier 6ersions of 4his International Standard. See
         Annex D, "Deprecated features".


         5 5 (T )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


          (y> )  Conformance


          (y> ).1  Introduction

         This International Standard specifies conforming SQL language and
         conforming SQL-implementations.

         Conforming SQL language shall abide by 4he BNF Format, associated
         Syntax Rules and Access Rules, definitions, and descriptions.

         A conforming SQL-implementation shall 0rocess conforming SQL lan-
         guage according to 4he associated General Rules, definitions, and
         descriptions.

         The object identifier for Database Language SQL is specified in
         Subclause 0Ô0¢0¹0È0ë4, "Object identifier for Database Language SQL".

          (y> ).2  Claims of conformance

         Claims of conformance to 4his International Standard shall state:

         1) 2 2 2 2hich level of conformance is claimed:

            a) Full SQL (The complete database language specified in this
              ! ?nternational Standard.)

            b) Intermediate SQL (Intermediate SQL is a subset of Full SQL as
              specified in 4he Leveling Rules.)

            c) Entry SQL (Entry SQL is a subset of Intermediate SQL as spec-
              ified in 4he Leveling Rules.)

          (SA ) 2 2 2 2hich of the following binding styles are supported:

            a) Module (<module>)

            b) Embedded syntax (<embedded SQL host program>)

            c) Direct invocation and processing of SQL language (<direct SQL
              statement>)

         0Î0Ã0È For 4he binding styles module or embedded syntax, 7hich of the
            following programming languages are supported:

            a) Ada

            b) C

            c) COBOL

            d) Fortran

                                                           Conformance   5 5 (ry )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         20Ô0¢0¹0È0ë (N  )Claims of conformance


            e) MUMPS

            f) Pascal

            g) PLg

         2 2 2) The definitions for all elements and actions 4hat this Standard
            specifies as implementation-defined.

         20Ô0¢0¹0È0ë0µ0ó0Á0ü0à Extensions and options

         A conforming implementation may provide additional facilities or
         options not specified by 4his International Standard. This may im-
         ply an implementation-defined extension of 4he list of reserved
         7ords (<reserved word>) and 4hereby may 0revent 0roper process-
         ing of some programs 4hat otherwise meet 4he requirements of 4his
         ! ?nternational Standard.

         An implementation remains conforming even if it 0rovides user op-
         tions to 0rocess nonconforming SQL language or 4o process conform-
         ing SQL language in a nonconforming manner.

          (y> ).4  Flagger requirements


         Implementations that claim conformance only to Entry SQL may, but
         are not required to, provide an SQL Flagger (see Subclause 4.0Ö0Ã0·0§0ë,
         "SQL Flagger").

         ! ?mplementations 4hat claim conformance to ! ?ntermediate SQL shall
         0rovide an SQL Flagger (see Subclause 2 2 2.34, "SQL Flagger") that
         supports 4he following "level of flagging" options:

         -  Entry SQL Flagging

         -  ! ?ntermediate SQL Flagging

         and 4he following "extent of checking" option:

         -  Syntax Only

         ! ?mplementations 4hat claim conformance to Full SQL shall provide an
         SQL Flagger (see Subclause 2 2 2.34, "SQL Flagger") that supports the
         following "level of flagging" options:

         -  Entry SQL Flagging

         -  ! ?ntermediate SQL Flagging

         -  Full SQL Flagging

         and the following "extent of checking" options:

         -  Syntax Only

         5 5 (Œ¡ )  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                    (y> ).4 Flagger requirements


         -  Catalog Lookup

         20Ô0¢0¹0È0ë5  Processing methods


         This International Standard does not define 4he method by 7hich an
         ! !embedded SQL host program> is processed. Although the processing
         of ! !embedded SQL host program> is defined in 4erms of derivation
         of a 0rogram compliant 7ith a programming language standard and a
         ! !module>, implementations of SQL are not constrained to follow that
         method, provided 4hat effect is achieved.

         Although 4he 0rocessing of ! !direct SQL statement> is defined in
         4erms of calls to ! !procedure>s in a ! !module>, implementations of
         Direct Invocation are not constrained 4o follow 4hat method, so
         long as the same effect is achieved.


                                                           Conformance   627

  


         628  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


                                       Annex A

                                    (informative)

                              Leveling 4he SQL Language


         This Annex describes 4he restrictions placed on conforming
         Intermediate SQL and Entry SQL language.


         A.1  ! ?ntermediate SQL Specifications


         1) Subclause 5.2, "<token> and ! !separator>":

            a) ! ?n conforming ! ?ntermediate SQL language, a <regular iden-
              4ifier> or a <delimited identifier body> shall not comprise
              more than 18 <character representation>s.

            b) A ! !delimiter token> shall not be a <bit string literal> or a
              <hex string literal>.

            c) Conforming ! ?ntermediate SQL language shall contain no <iden-
              4ifier body> that ends in an <underscore>.

          (SA ) Subclause 5.3, "<literal>":

            a) An <unsigned integer> 4hat is a ! !seconds fraction> shall not
              contain more 4han 6 <digit>s.

            b) A <literal> or ! !unsigned literal> shall not be a ! !bit string
              literal> or a ! !hex string literal>.

            c) A ! !character string literal> shall not specify a <character
              set specification>.

         2 2) Subclause 5.4, "Names and identifiers":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !extended statement name> or <extended cursor name>.

            b) Conforming ! ?ntermediate SQL language shall not contain any
              ! !collation name>.

            c) Conforming Intermediate SQL language shall not contain any
              explicit ! !catalog name>.

                                              Leveling 4he SQL Language  5 5 (Nã )

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         A.1 ! ?ntermediate SQL Specifications


            d) Conforming ! ?ntermediate SQL language shall not contain any
              ! !translation name> or ! !form-af-use conversion name>.

            e) An ! !identifier> shall not specify a <character set specifica-
              tion>.

         2 2 2) Subclause 6.1, "<data type>":

            a) A <datetime type> shall not specify a <time precision> or
              <timestamp 0recision>.

            b) A ! !data 4ype> shall not be a <bit string type>.

         5) Subclause 6. (l4 ) "<value specification> and <target specifica-
            4ion>":

            a) ! ?n Intermediate SQL, the specific data type of <indicator
              0arameter>s and ! !indicator variable>s shall be the same
              implementation-defined data 4ype.

         5 5) Subclause 6.0Ñ0ü0Ä "<table reference>":

            a) A <table reference> shall not be a ! !derived table>.

         7) Subclause 5 5.5, "<set function specification>":

            a) If a ! !general set function> specifies DISTINCT, then 4he
              ! !value expression> shall be a ! !column reference>.

         8) Subclause 6.6, "<numeric 6alue function>":

            a) A ! !numeric value function> shall not be a ! !position expres-
              sion>.

            b) A <numeric 6alue function> shall not contain a ! !length ex-
              0ression> 4hat is a ! !bit length expression>.

         9) Subclause 5 5.7, "<string 6alue function>":

            a) A ! !character value function> shall not be a ! !fold>.

            b) Conforming Intermediate SQL language shall contain no ! !char-
              acter translation>.

            c) Conforming ! ?ntermediate SQL language shall contain no <form-
              of-use conversion>.

            d) Conforming Intermediate SQL language shall contain no ! !bit
              value function>.

         10)Subclause 6.8, "<datetime value function>":

            a) Conforming ! ?ntermediate SQL language shall contain no <time
              precision> or <timestamp 0recision>.

         5 50Ô0³  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                         A.1 Intermediate SQL Specifications


         11)Subclause 6.ª, "<string 6alue expression>":

            a) Conforming Intermediate SQL language shall not contain any
              <collate clause>.

            b) Conforming ! ?ntermediate SQL language shall contain no <bit
              6alue expression>.

         )Subclause 5 5 5.1, "<row value constructor>":

            a) A ! !row value constructor> 4hat is not simply contained in
              a ! !table value constructor> shall not contain more than one
              ! !row value constructor element>.

         ª)Subclause 5 5 5.2, "<table value constructor>":

            a) A ! !table value constructor> shall contain exactly one ! !row
              value constructor> 4hat shall be of the form "(<value expres-
              sion list>)".

            b) A <table 6alue constructor> shall be 4he ! !query expression>
              of an <insert statement>.

         )Subclause 5 5 5.3, "<table expression>":

            a) If 4he 4able identified in 4he ! !from clause> is a grouped
              view, then 4he ! !table expression> shall not contain a <where
              clause>, <group by clause>, or <having clause>.

         15)Subclause 7.4, "<from clause>":

            a) A <table reference> shall not be a ! !derived table>.

            b) If 4he 4able identified by ! !table name> is a grouped 6iew,
              4hen the <from clause> shall contain exactly one <table ref-
              erence>.

         16)Subclause 7.5, "<joined table>":

            a) Conforming Intermediate SQL language shall contain no ! !cross
              join>.

            b) Conforming Intermediate SQL language shall not specify UNION
              JOIN.

         )Subclause 5 5 5.7, "<group by clause>":

            a) Conforming Intermediate SQL language shall not contain any
              <collate clause>.

         )Subclause 5 5 5.9, "<query specification>":

            a) The ! !key word> DISTINCT shall not be specified more 4han once
              in a <query specification>, excluding any ! !subquery> of 4hat
              <query specification>.

                                              Leveling 4he SQL Language  5 50Ó0ë

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         A.1 ! ?ntermediate SQL Specifications


            b) If 4he ! !table expression> of 4he ! !query specification> is a
              grouped view, then 4he ! !select list> shall not contain a ! !set
              function specification>.

         19)Subclause 7.10, "<query expression>":

            a) A <simple table> shall not be a <table 6alue constructor>
              except in an ! !insert statement>.

            b) Conforming Intermediate SQL shall contain no <explicit ta-
              ble>.

          (eå ))Subclause 5 5 5.11, "<scalar subquery>, ! !row subquery>, and ! !table
            subquery>":

            a) The <query expression> contained in a <subquery> shall be a
              <query specification>.

         21)Subclause 8.1, "<predicate>":

            a) A <predicate> shall not be a ! !match predicate>.

          (g	 ))Subclause 8.4, "<in 0redicate>":

            a) Conforming ! ?ntermediate SQL language shall not contain a
              ! !value expression> in an <in value list> that is not a <value
              specification>.

         20Î0Ã0ÈSubclause 8.10, "<match predicate>":

            a) Conforming Intermediate SQL language shall not contain any
              <match 0redicate>.

         24)Subclause 8., "<search condition>":

            a) A <boolean 4est> shall not specify a ! !truth value>.

          (ry ))Subclause 10.0Ñ0ü0Ä "<privileges>":

            a) An <action> 4hat specifies INSERT shall not contain a ! !privi-
              lege column list>.

          (Œ¡ ))Subclause 10.5, "<collate clause>":

            a) Conforming Intermediate SQL language shall not contain any
              <collate clause>.

          (y] ))Subclause 11.1, "<schema definition>":

            a) A <schema element> shall not be an ! !assertion definition>.

            b) Conforming Intermediate SQL language shall not contain any
              <collation definition>.

            c) Conforming ! ?ntermediate SQL language shall not contain any
              ! !translation definition>.

         5 50Õ0¡0é0Ã0É  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                         A.1 Intermediate SQL Specifications


         28)Subclause  .3, "<table definition>":

            a) Conforming ! ?ntermediate SQL language shall not specify ? ?LOBAL
              TEMPORARY and shall not reference any global 4emporary 4able.

          (Nã ))Subclause 11.4, "<column definition>":

            a) A <constraint attributes> shall not be specified, but
              INITIALLY IMMEDIATE and NOT DEFERRABLE are implicit.

            b) Conforming Intermediate SQL language shall not contain any
              <collate clause>.

         0Ô0³)Subclause 11.6, "<table constraint definition>":

            a) A <constraint attributes> shall not be specified, but
              INITIALLY IMMEDIATE and NOT DEFERRABLE are implicit.

         2 21)Subclause  .8, "<referential constraint definition>":

            a) A ! !references specification> shall not specify MATCH.

            b) A ! !referential triggered action> shall not contain an ! !update
              rule>.

         0Õ0¡0é0Ã0É)Subclause 11.9, "<check constraint definition>":

            a) The <search condition> contained in a <check constraint defi-
              nition> shall not contain a <subquery>.

            b) The REFERENCES 0rivilege is not required for ! !check con-
              straint definition> access.

         2 20Î0Ã0ÈSubclause  .19, "<view definition>":

            a) Conforming ! ?ntermediate SQL shall not contain any <levels
              clause>, but 4he effect shall be 4hat defined for a <levels
              clause> of CASCADED.

         2 24)Subclause  .21, "<domain definition>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !collate clause>.

         2 25)Subclause  .2 (l4 ) "<alter domain statement>":

            a) Conforming Intermediate SQL language shall contain no ! !alter
              domain statement>.

         2 26)Subclause  .20Ñ0ü0Ä "<set domain default clause>":

            a) Conforming ! ?ntermediate SQL language shall contain no <set
              domain default clause>.

                                              Leveling 4he SQL Language  5 50Õ0£0ü0È

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         A.1 ! ?ntermediate SQL Specifications


         0Ú0½)Subclause 11. (T ), "<drop domain default clause>":

            a) Conforming ! ?ntermediate SQL language shall contain no <drop
              domain default clause>.

         0Ú0Ë0Ò)Subclause 11. (ry ), "<add domain constraint definition>":

            a) Conforming ! ?ntermediate SQL language shall contain no <add
              domain constraint definition>.

         0Ø0ë0Ä)Subclause 11. (Œ¡ ), "<drop domain constraint definition>":

            a) Conforming Intermediate SQL language shall contain no ! !drop
              domain constraint definition>.

         40)Subclause 11.0Ô0³, "<collation definition>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !collation definition>.

         2 2 21)Subclause  .31, "<drop collation statement>":

            a) Conforming Intermediate SQL language shall not contain any
              <drop collation statement>.

         42)Subclause 11.0Õ0¡0é0Ã0É, "<translation definition>":

            a) Conforming ! ?ntermediate SQL language shall contain no <trans-
              lation definition>.

         43)Subclause 11.0Õ0£0ü0È, "<drop 4ranslation statement>":

            a) Conforming ! ?ntermediate SQL language shall contain no <drop
              translation statement>.

         44)Subclause 11.0Ö0Ã0·0§0ë, "<assertion definition>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !assertion definition>.

         2 2 25)Subclause  .35, "<drop assertion statement>":

            a) Conforming Intermediate SQL language shall not contain any
              <drop assertion statement>.

         46)Subclause 11.0Ø0¯0¿0ü0ë, "<grant statement>":

            a) ! ?n Conforming ! ?ntermediate SQL language, an ! !object name>
              shall not specify COLLATION or TRANSLATION.

         2 2 27)Subclause .1, "<module>":

            a) A <module> shall not contain a ! !temporary table declaration>.

         634  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         A.1 ! ?ntermediate SQL Specifications


         48)Subclause 1 (‘Ñ )0Ñ0ü0Ä "<procedure>":

            a) A <parameter declaration> shall not specify a <data type>
              that is BIT or BIT VARYING.

         49)Subclause 1 (‘Ñ )5, "<sql 0rocedure statement>":

            a) An ! !SQL transaction statement> shall not be a <set con-
              straints mode statement>.

            b) An ! !SQL schema statement> shall not be an <assertion defini-
              4ion>.

            c) An ! !SQL schema statement> shall not be a ! !drop assertion
              statement>.

            d) An <sql dynamic statement> shall not be an <allocate cursor
              statement> statement.

            e) An <sql session statement> shall not be a ! !set schema state-
              ment>, a ! !set catalog statement>, or a ! !set names statement>.

            f) An ! !SQL schema statement> shall not be a ! !collation defini-
              tion>, a ! !drop collation statement>, a ! !translation defini-
              tion>, or a <drop translation statement>.

            g) An ! !SQL dynamic statement shall not be a ! !deallocate 0repared
              statement>, or a ! !describe input statement>.

            h) An <sql 0rocedure statement> shall not be an <sql connection
              statement>.

         50)Subclause 10Ô0¢0¹0È0ë1, "<declare cursor>":

            a) Conforming Intermediate SQL language shall not specify
              INSENSITIVE.

            b) ! ?f an ! !updatability clause> of FOR UPDATE 7ith or 7ithout
              a ! !column name list> is specified, then neither SCROLL nor
              ORDER BY shall be specified.

         51)Subclause ª.3, "<fetch statement>":

            a) A ! !fetch statement> shall not contain a ! !fetch orientation>.

         52)Subclause 10Ô0¢0¹0È0ë5, "<select statement: single row>":

            a) The ! !table expression> shall not include a <group by clause>
              or a ! !having clause> and shall not identify a grouped view.

         53)Subclause 10Ô0¢0¹0È0ë6, "<delete statement: 0ositioned>":

            a) Let T be the table identified by the <table name>. T shall
              not be a 4able 4hat is identified in 4he ! !from clause> of any
              <subquery> contained in the <cursor specification> referenced
              by 4he ! !cursor name>.

                                              Leveling the SQL Language  635

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         A.1 Intermediate SQL Specifications


         54)Subclause ª.7, "<delete statement: searched>":

            a) Let T be 4he 4able identified by 4he ! !table name>. T shall
              not be a table that is identified in the <from clause> of any
              ! !subquery> contained in 4he ! !search condition>.

         55)Subclause ª.8, "<insert statement>":

            a) The base 4able 4hat would be changed as a result of executing
              the <insert statement> shall not be identified in any <from
              clause> generally contained in 4he ! !query expression>.

         56)Subclause ª.9, "<update statement: positioned>":

            a) Let T be 4he 4able identified by 4he ! !table name>. T shall
              not be a table that is identified in the <from clause> of any
              ! !subquery> contained in 4he ! !cursor specification> referenced
              by the <cursor name>.

         57)Subclause ª.10, "<update statement: searched>":

            a) Let T be the table identified by the <table name>. T shall
              not be a 4able 4hat is identified in 4he ! !from clause> of any
              <subquery> contained in the <search condition> or contained
              in 4he ! !value expression> of 4he ! !set clause>.

         58)Subclause ª.11, "<temporary 4able declaration>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !temporary table declaration>.

         59)Subclause 14. (l4 ) "<set constraints mode statement>":

            a) Conforming Intermediate SQL language shall not contain any
              <set constraints mode statement>.

         60)Subclause 15.1, "<connect statement>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !connect statement>.

         61)Subclause 15. (l4 ) "<set connection statement>":

            a) Conforming Intermediate SQL language shall not contain any
              <set connection statement>.

         62)Subclause 15.0Ñ0ü0Ä "<disconnect statement>":

            a) Conforming Intermediate SQL language shall not contain any
              <disconnect statement>.

         63)Subclause 16.1, "<set catalog statement>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !set catalog statement>.

         636  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                         A.1 ! ?ntermediate SQL Specifications


         64)Subclause 16. (l4 ) "<set schema statement>":

            a) Conforming Intermediate SQL language shall not contain any
              <set schema statement>.

         65)Subclause 16.0Ñ0ü0Ä "<set names statement>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !set names statement>.

         66)Subclause 17. (l4 ) "<allocate descriptor statement>":

            a) An ! !occurrences> and a ! !descriptor name> shall be a <lit-
              eral>.

         5 57)Subclause .3, "<deallocate descriptor statement>":

            a) A ! !descriptor name> shall be a <literal>.

         5 58)Subclause .4, "<get descriptor statement>":

            a) A <descriptor name> shall be a ! !literal>.

         69)Subclause 17.5, "<set descriptor statement>":

            a) A ! !descriptor name> shall be a <literal>.

         5 5 50)Subclause .6, "<prepare statement>":

            a) A ! !preparable SQL schema statement> shall not be an ! !asser-
              4ion definition> or a ! !drop assertion statement>.

            b) A ! !preparable SQL schema statement> shall not be a <collation
              definition>, a <drop collation statement>, a <translation
              definition>, or a ! !drop 4ranslation statement>.

            c) A ! !preparable SQL session statement> shall not be a ! !set
              schema statement>.

            d) A ! !preparable SQL session statement> shall not be a ! !set
              catalog statement>.

            e) A <preparable SQL session statement> shall not be a <set
              names statement>.

            f) A ! !preparable SQL 4ransaction statement> shall not be a ! !set
              constraints mode statement>.

            g) A ! !preparable SQL data statement> shall not be a <dynamic
              single row select statement>.

         5 5 51)Subclause .7, "<deallocate 0repared statement>":

            a) Conforming Intermediate SQL language shall contain no ! !deal-
              locate 0repared statement>.

                                              Leveling the SQL Language  637

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         A.1 Intermediate SQL Specifications


         5 5 5 (SA )Subclause .8, "<describe statement>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !describe input statement>.

         5 5 50Î0Ã0ÈSubclause .9, "<using clause>":

            a) A <descriptor name> shall be a ! !literal>.

         74)Subclause 17.10, "<execute statement>":

            a) Conforming Intermediate SQL language shall contain no ! !result
              5sing clause>.

         75)Subclause 17., "<dynamic declare cursor>":

            a) Conforming ! ?ntermediate SQL language shall contain no <dy-
              namic declare cursor> 4hat specifies INSENSITIVE.

            b) ! ?f an ! !updatability clause> of FOR UPDATE 7ith or 7ithout
              a ! !column name list> is specified, then neither SCROLL nor
              ORDER BY shall be specified.

         5 5 56)Subclause .10Ñ0ü0Ä "<allocate cursor statement>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !allocate cursor statement>.

         77)Subclause 17.¬, "<dynamic fetch statement>":

            a) A ! !dynamic fetch statement> shall not contain a ! !fetch orien-
              4ation>.

         78)Subclause 17., "<dynamic delete statement: positioned>":

            a) Let T be 4he 4able identified by 4he ! !table name>. T shall
              not be a table that is identified in the <from clause> of any
              ! !subquery> contained in 4he ! !cursor specification> referenced
              by the <dynamic cursor name>.

         5 5 59)Subclause .18, "<dynamic 5pdate statement: 0ositioned>":

            a) Let T be the table identified by the <table name>. T shall
              not be a 4able 4hat is identified in 4he ! !from clause> of any
              <subquery> contained in the <cursor specification> referenced
              by 4he ! !dynamic cursor name>.

         80)Subclause 17., "<preparable dynamic delete statement: 0osi-
            4ioned>":

            a) Conforming Intermediate SQL language shall contain no
              ! !preparable dynamic delete statement: 0ositioned>.


         5 50Ú0Ë0Ò  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                         A.1 Intermediate SQL Specifications


         81)Subclause .20, "<preparable dynamic update statement: posi-
            tioned>":

            a) Conforming ! ?ntermediate SQL language shall contain no
              <preparable dynamic update statement: positioned>.

         8 (SA )Subclause .1, "<embedded SQL host program>":

            a) An <embedded SQL statement> shall not contain a ! !temporary
              table declaration>.

         83)Subclause 19.0Ñ0ü0Ä "<embedded SQL Ada program>":

            a) An <ada 6ariable definition> shall not specify a bit string
              6ariable.

         84)Subclause .4, "<embedded SQL C 0rogram>":

            a) A <c derived 6ariable> shall not be a <c bit 6ariable>.

         85)Subclause 19.5, "<embedded SQL COBOL program>":

            a) A ! !COBOL type specification> shall not be a ! !COBOL bit type>.

         86)Subclause .6, "<embedded SQL Fortran 0rogram>":

            a) A <fortran 4ype specification> shall not specify BIT.

         87)Subclause 19.8, "<embedded SQL Pascal 0rogram>":

            a) A <pascal type specification> shall not specify BIT or PACKED
              ARRAY [1..<length>] OF BIT.

         88)Subclause 19.9, "<embedded SQL PLg 0rogram>":

            a) A <pl/i type specification> shall not specify BIT or BIT
              VARYING.

         89)Subclause 20.1, "<direct SQL statement>":

            a) A ! !direct SQL data statement> shall not be a <temporary 4able
              declaration>.

            b) An <sql session statement> shall not be a ! !set schema state-
              ment>, a ! !set catalog statement>, or a ! !set names statement>.

            c) An ! !SQL transaction statement> shall not be a <set con-
              straints mode statement>.

            d) An ! !SQL schema statement> shall not be an <assertion defini-
              4ion> or a <drop assertion statement>.

            e) An ! !SQL schema statement> shall not be a ! !collation defini-
              tion>, a ! !drop collation statement>, a ! !translation defini-
              tion> or a ! !drop 4ranslation statement>.

                                              Leveling 4he SQL Language  5 50Ø0ë0Ä

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         A.1 ! ?ntermediate SQL Specifications


            f) A <direct SQL statement> shall not be an ! !SQL connection
              statement>.

         90)Subclause  (h* ).2, "Information Schema":

            a) Conforming ! ?ntermediate SQL language shall reference only
              the following Information Schema 4ables: SCHEMATA, DOMAINS,
              TABLES, VIEWS, COLUMNS, TABLE_PRIVILEGES, COLUMN_PRIVILEGES,
              USAGE_PRIVILEGES, REFERENTIAL_CONSTRAINTS, CHECK_CONSTRAINTS,
              KEY_COLUMN_USAGE, ASSERTIONS, CHARACTER_SETS, COLLATIONS,
              VIEW_COLUMN_USAGE, CONSTRAINT_TABLE_USAGE, CONSTRAINT_COLUMN_
              USAGE, SQL_LANGUAGES, COLUMN_DOMAIN_USAGE, and VIEW_TABLE_
              USAGE.

         A.2  Entry SQL Specifications


         1) All ! ?ntermediate SQL specifications are included as Entry SQL
            specifications.

         2) Subclause 5. (l4 ) "<token> and <separator>":

            a) A <delimiter 4oken> shall not be a ! !national character string
              literal>.

            b) An ! !identifier body> shall contain no <simple Latin lower
              case letter>.

         0Î0Ã0È Subclause 5.3, "<literal>":

            a) A ! !literal> or <unsigned literal> shall not be a <national
              character string literal>.

            b) A ! !literal> or <unsigned literal> shall not be a <datetime
              literal> or an ! !interval literal>.

         2 2 2) Subclause 5.4, "Names and identifiers":

            a) Conforming Entry SQL language shall not contain any <do-
              main name>, ! !SQL statement name>, ! !dynamic cursor name>, or
              ! !constraint name>.

         5) Subclause 5 5.1, "<data 4ype>":

            a) A ! !character string 4ype> shall not specify VARYING or
              VARCHAR.

            b) A ! !data 4ype> shall not be a <datetime type> or an <interval
              type>.

            c) A ! !data 4ype> shall not be a <national character string 4ype>
              nor specify CHARACTER SET.


         5 540  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                A.2 Entry SQL Specifications


         5 5) Subclause 6. (l4 ) "<value specification> and <target specifica-
            4ion>":

            a) A ! !general value specification> shall not be a <dynamic 0a-
              rameter specification>.

            b) A ! !general value specification> shall not specify VALUE.

            c) A <general 6alue specification> shall not specify SESSION_
              USER, SYSTEM_USER, or CURRENT_USER.

         5 5 5) Subclause 6.0Ñ0ü0Ä "<table reference>":

            a) A <table reference> shall not be a ! !joined 4able>.

            b) The optional <key 7ord> AS shall not be specified.

            c) <derived column list> shall not be specified.

         8) Subclause 5 5.5, "<set function specification>":

            a) If a ! !general set function> specifies or implies ALL, then
              COUNT shall not be specified.

            b) ! ?f a <general set function> specifies or implies ALL, 4hen
              the <value expression> shall include a ! !column reference>
              that references a column of T.

            c) ! ?f the <value expression> contains a <column reference> 4hat
              is an outer reference, 4hen the <value expression> shall be a
              <column reference>.

            d) No ! !column reference> contained in a ! !set function specifica-
              tion> shall reference a column derived from a <value expres-
              sion> 4hat generally contains a ! !set function specification>.

         9) Subclause 6.6, "<numeric 6alue function>":

            a) A ! !numeric value function> shall not be a ! !length expres-
              sion>.

            b) A <numeric 6alue function> shall not be an ! !extract expres-
              sion>.

         10)Subclause 6.7, "<string value function>":

            a) A <character 6alue function> shall not be a <character sub-
              string function>.

            b) A <character 6alue function> shall not be a <trim function>.

         11)Subclause 6.8, "<datetime value function>":

            a) Conforming Entry SQL language shall not contain any <datetime
              value function>.

                                              Leveling 4he SQL Language  5 541

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         A.2 Entry SQL Specifications


         1 (SA )Subclause 6.9, "<case expression>":

            a) Conforming Entry SQL language shall not contain any <case
              expression>.

         10Î0Ã0ÈSubclause 6.10, "<cast specification>":

            a) Conforming Entry SQL language shall not contain any <cast
              specification>.

         )Subclause 5 5.11, "<value expression>":

            a) A ! !value expression> shall not be a ! !datetime 6alue expres-
              sion>.

            b) A <value expression> shall not be an ! !interval 6alue expres-
              sion>.

            c) A <value expression primary> shall not be a <case expres-
              sion>.

            d) A ! !value expression 0rimary> shall not be a ! !cast specifica-
              tion>.

            e) A ! !value expression 0rimary> shall not be a ! !scalar subquery>
              except when 4he ! !value expression 0rimary> is simply con-
              4ained in a ! !value expression> that is simply contained in
              the second ! !row value constructor> of a <comparison predi-
              cate>.

         ¬)Subclause 5 5.10Ñ0ü0Ä "<string value expression>":

            a) A <character 6alue expression> shall not be a <concatena-
              tion>.

         16)Subclause 6., "<datetime 6alue expression>":

            a) Conforming Entry SQL language shall not contain any ! !datetime
              6alue expression>.

         )Subclause 5 5.15, "<interval value expression>":

            a) Conforming Entry SQL language shall not contain any <interval
              value expression>.

         18)Subclause 7.1, "<row 6alue constructor>":

            a) A <value expression> 4hat is contained in the <row 6alue con-
              structor> that is contained in 4he ! !table value constructor>
              4hat is contained in the <query expression> of an ! !insert
              statement> shall be a ! !value specification>.

            b) A <row 6alue constructor element> shall not specify DEFAULT.

         5 542  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                A.2 Entry SQL Specifications


         19)Subclause 7.5, "<joined table>":

            a) Conforming Entry SQL language shall not contain any ! !joined
              4able>.

         20)Subclause 7.6, "<where clause>":

            a) A ! !value expression> directly contained in the <search condi-
              4ion> shall not include a reference 4o a column derived from
              a function.

          (h* ))Subclause 5 5 5.9, "<query specification>":

            a) A ! !query specification> is not updatable if 4he ! !where
              clause> of 4he ! !table expression> contains a ! !subquery>.

            b) A ! !select sublist> shall not specify "<qualifier>.*".

         2 (SA )Subclause 7.10, "<query expression>":

            a) A <query expression> shall not specify EXCEPT.

            b) A ! !query term> shall not specify INTERSECT.

            c) A ! !query primary> shall not contain a ! !joined 4able>.

            d) A ! !query expression> shall not specify CORRESPONDING.

            e) ! ?f UNION is specified, then except for column names, the
              descriptions of the first and second operands shall be iden-
              4ical and 4he description of the result is identical to 4he
              description of the operands.

          (y> ))Subclause 5 5 5.11, "<scalar subquery>, ! !row subquery>, and ! !table
            subquery>":

            a) If a ! !subquery> is contained in a <comparison predicate>,
              then 4he ! !table expression> in 4he ! !query specification>
              shall not contain a ! !group by clause> or a <having clause>
              and shall not identify a grouped 6iew.

         24)Subclause 8.1, "<predicate>":

            a) Conforming Entry SQL language shall not contain any <overlaps
              predicate>.

            b) Conforming Entry SQL language shall not contain any <unique
              predicate>.

          (ry ))Subclause 8.5, "<like 0redicate>":

            a) The <match 6alue> shall be a ! !column reference>.

            b) A ! !pattern> shall be a <value specification>.

            c) An <escape character> shall be a <value specification>.

                                              Leveling 4he SQL Language  5 543

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         A.2 Entry SQL Specifications


         26)Subclause 8.6, "<null predicate>":

            a) A ! !row value constructor> shall be a <column reference>.

          (y] ))Subclause 8.9, "<unique 0redicate>":

            a) Conforming Entry SQL language shall not contain any <unique
              predicate>.

          (R´ ))Subclause 8.11, "<overlaps predicate>":

            a) Conforming Entry SQL language shall not contain any ! !overlaps
              0redicate>.

         29)Subclause 10.1, "<interval iualifier>":

            a) Conforming Entry SQL language shall not contain any <interval
              qualifier>.

         0Ô0³)Subclause 10. (l4 ) "<language clause>":

            a) Conforming Entry SQL language shall not contain a <language
              clause> that specifies MUMPS.

         0Ó0ë)Subclause 10.4, "<character set specification>":

            a) Conforming Entry SQL language shall not contain a <character
              set specification>.

         2 2 (SA )Subclause  .1, "<schema definition>":

            a) A ! !schema element> shall not be a ! !domain definition>.

            b) A <schema name clause> shall specify AUTHORIZATION and shall
              not specify a ! !schema name>.

            c) A <schema character set specification> shall not be speci-
              fied.

            d) Conforming Intermediate SQL language shall not contain any
              <character set definition>.

         0Õ0£0ü0È)Subclause 11. (l4 ) "<drop schema statement>":

            a) Conforming Entry SQL language shall not contain a <drop
              schema statement>.

         2 24)Subclause  .18, "<drop table statement>":

            a) Conforming Entry SQL language shall not contain any ! !drop
              4able statement>.

         2 25)Subclause  .4, "<column definition>":

            a) A ! !column definition> shall not contain a ! !domain name>.

         644  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )                                                A. (N  )Entry SQL Specifications


            b) A <column constraint> shall not contain a <referential 4rig-
              gered action>.

            c) Conforming Entry SQL language shall not contain any <con-
              straint name definition>.

         0Ø0¯0¿0ü0ë)Subclause 11.5, "<default clause>":

            a) A ! !default option> shall not specify CURRENT_DATE, CURRENT_
              TIME, CURRENT_TIMESTAMP, SYSTEM_USER, SESSION_USER, or
              CURRENT_USER.

         0Ú0½)Subclause 11.6, "<table constraint definition>":

            a) Conforming Entry SQL language shall not contain any <con-
              straint name definition>.

         0Ú0Ë0Ò)Subclause 11.7, "<unique constraint definition>":

            a) ! ?f PRIMARY KEY or UNIQUE is specified, then 4he ! !column defi-
              nition> for each column 7hose ! !column name> is in 4he ! !unique
              column list> shall specify NOT NULL.

         0Ø0ë0Ä)Subclause 11.8, "<referential constraint definition>":

            a) A <referential constraint definition> shall not contain a
              <referential 4riggered action>.

         40)Subclause 11.10, "<alter table statement>":

            a) Conforming Entry SQL language shall not contain an <alter
              4able statement>.

         2 2 21)Subclause  .11, "<add column definition>":

            a) Conforming Entry SQL language shall not contain an ! !add col-
              5mn definition>.

         42)Subclause 11., "<alter column definition>":

            a) Conforming Entry SQL language shall not contain an <alter
              column definition>.

         2 2 20Î0Ã0ÈSubclause  .10Ñ0ü0Ä "<set column default clause>":

            a) Conforming Entry SQL language shall not contain a <set column
              default clause>.

         2 2 24)Subclause  .14, "<drop column default clause>":

            a) Conforming Entry SQL language shall not contain a ! !drop col-
              umn default clause>.

         2 2 25)Subclause  .15, "<drop column definition>":

            a) Conforming Entry SQL language shall not contain a ! !drop col-
              umn definition>.

                                              Leveling 4he SQL Language  5 545

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         A.2 Entry SQL Specifications


         2 2 26)Subclause  .16, "<add 4able constraint definition>":

            a) Conforming Entry SQL language shall not contain an ! !add table
              constraint definition>.

         47)Subclause 11., "<drop 4able constraint definition>":

            a) Conforming Entry SQL language shall not contain a <drop table
              constraint definition>.

         48)Subclause 11., "<view definition>":

            a) The ! !query expression> in a ! !view definition> shall be a
              <query specification>.

         2 2 29)Subclause  .20, "<drop view statement>":

            a) Conforming Entry SQL language shall not contain a <drop view
              statement>.

         50)Subclause  .36, "<grant statement>":

            a) An ! !object name> shall not specify TABLE.

            b) In Conforming Entry SQL language, an ! !object name> shall not
              specify CHARACTER SET or DOMAIN.

         51)Subclause 11.0Ú0½, "<revoke statement>":

            a) Conforming Entry SQL language shall not contain a <revoke
              statement>.

         52)Subclause 11. (h* ), "<domain definition>":

            a) Conforming Entry SQL language shall not contain any ! !domain
              definition>.

         53)Subclause 11. (y] ), "<drop domain statement>":

            a) Conforming Entry SQL language shall not contain a ! !drop do-
              main statement>.

         54)Subclause 11. (R´ ), "<character set definition>":

            a) Conforming Entry SQL language shall not specify any <charac-
              4er set definition>.

         55)Subclause 11. (Nã ), "<drop character set statement>":

            a) Conforming Entry SQL language shall contain no ! !drop charac-
              4er set statement>.

         56)Subclause .1, "<module>":

            a) A <module> shall be associated 7ith an SQL-agent during its
              execution. An SQL-agent shall be associated with at most one
              ! !module>.

         5 546  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                A.2 Entry SQL Specifications


            b) A ! !module contents> shall not be a <dynamic declare cursor>.

         57)Subclause 1 (‘Ñ ) (l4 ) "<module name clause>":

            a) A ! !module character set specification> shall not be speci-
              fied.

         58)Subclause 1 (‘Ñ )0Ñ0ü0Ä "<procedure>":

            a) A <parameter declaration> shall not specify a <data type>
              that is CHARACTER VARYING.

         59)Subclause .5, "<sql procedure statement>":

            a) An <sql 0rocedure statement> shall not be an <sql schema
              statement>.

            b) An ! !SQL procedure statement> shall not be an ! !SQL dynamic
              statement>.

            c) An ! !SQL session statement> shall not be a <set session au-
              4horization identifier statement> or a <set 4ime zone state-
              ment>.

            d) An <sql 4ransaction statement> shall not be a ! !set transac-
              4ion statement>.

            e) An ! !SQL procedure statement> shall not be an ! !SQL diagnostics
              statement>.

         60)Subclause 10Ô0¢0¹0È0ë1, "<declare cursor>":

            a) A ! !declare cursor> shall not specify SCROLL.

            b) A <cursor specification> shall not contain an <updatability
              clause>.

         5 51)Subclause ª.3, "<fetch statement>":

            a) A ! !fetch statement> shall not specify FROM.

            b) ! ?f the data 4ype of 4he 4arget identified by the i-th ! !target
              specification> in 4he ! !fetch target list> is an exact numeric
              4ype, 4hen the data 4ype of 4he i-th column of the table T
              shall be an exact numeric type.

         62)Subclause 10Ô0¢0¹0È0ë5, "<select statement: single row>":

            a) ! ?f the data 4ype of 4he 4arget identified by the i-th ! !target
              specification> in 4he ! !fetch target list> is an exact numeric
              4ype, 4hen the data 4ype of 4he i-th column of the table T
              shall be an exact numeric type.


                                              Leveling 4he SQL Language  5 547

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )         A.2 Entry SQL Specifications


         5 50Î0Ã0ÈSubclause ª.8, "<insert statement>":

            a) The <query expression> 4hat is contained in an ! !insert state-
              ment> shall be a ! !table value constructor> 4hat specifies
              VALUES and contains exactly one <row 6alue constructor> or it
              shall be a ! !query specification>.

            b) If 4he data type of the target identified by 4he i-th <column
              name> is an exact numeric type, then 4he data type of the i-
              4h item of the <insert statement> shall be an exact numeric
              4ype.

            c) ! ?f the data 4ype of 4he 4arget C identified by the i-th ! !col-
              5mn name> is character string, then 4he length in characters
              of 4he i-th item of the <insert statement> shall be less 4han
              or equal 4o the length of C.

            d) The ! !insert columns and source> shall immediately contain a
              ! !query expression>.

         5 54)Subclause ª.9, "<update statement: positioned>":

            a) If 4he data type of the column identified by 4he i-th <object
              column> is an exact numeric type, then 4he data type of the
              i-th ! !value expression> in 4he ! !update statement: positioned>
              shall be an exact numeric type.

            b) If 4he data type of the column identified by 4he i-th <object
              column> C is character string, 4hen the length in characters
              of the i-th ! !value expression> in 4he ! !update statement:
              positioned> shall be less than or equal to 4he length of C.

            c) An ! !update source> shall not specify DEFAULT.

         65)Subclause 10Ô0¢0¹0È0ë10, "<update statement: searched>":

            a) If 4he data type of the column identified by 4he i-th <object
              column> is an exact numeric type, then 4he data type of the
              i-th ! !value expression> in 4he ! !update statement: searched>
              shall be an exact numeric type.

            b) If 4he data type of the column identified by 4he i-th <object
              column> C is character string, 4hen the length in characters
              of the i-th ! !value expression> in 4he ! !update statement:
              searched> shall be less than or equal to 4he length of C.

         66)Subclause 14.1, "<set 4ransaction statement>":

            a) Conforming Entry SQL language shall not contain any <set
              4ransaction statement>.

         5 57)Subclause .3, "<commit statement>":

            a) In conforming Entry SQL language, WORK shall be specified.

         5 548  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                A.2 Entry SQL Specifications


         5 58)Subclause .4, "<rollback statement>":

            a) In conforming Entry SQL language, WORK shall be specified.

         5 59)Subclause ­.4, "<set session authorization identifier state-
            ment>":

            a) Conforming ! ?ntermediate SQL language shall not contain any
              ! !set session authorization identifier statement>.

         5 5 50)Subclause ­.5, "<set local time +one statement>":

            a) Conforming Entry SQL language shall not contain any ! !set
              local time +one statement>.

         71)Subclause 17. (l4 ) "<allocate descriptor statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         72)Subclause 17.0Ñ0ü0Ä "<deallocate descriptor statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         73)Subclause 17.4, "<get descriptor statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         5 5 54)Subclause .5, "<set descriptor statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         75)Subclause 17.6, "<prepare statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         76)Subclause 17.7, "<deallocate prepared statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         77)Subclause 17.8, "<describe statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         5 5 58)Subclause .9, "<using clause>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

                                              Leveling the SQL Language  649

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         A. (N  )Entry SQL Specifications


         79)Subclause 17.10, "<execute statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         80)Subclause .11, "<execute immediate statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         81)Subclause 17., "<dynamic declare cursor>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         82)Subclause 17.ª, "<allocate cursor statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         80Î0Ã0ÈSubclause .14, "<dynamic open statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         84)Subclause .15, "<dynamic fetch statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         85)Subclause 17.­, "<dynamic close statement>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         86)Subclause .17, "<dynamic delete statement: 0ositioned>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         87)Subclause .18, "<dynamic 5pdate statement: 0ositioned>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         88)Subclause .19, "<preparable dynamic delete statement: posi-
            tioned>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         89)Subclause 17. (eå ), "<preparable dynamic 5pdate statement: 0osi-
            4ioned>":

            a) Conforming Entry SQL language shall not contain any Dynamic
              SQL language.

         5 550  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
                                                A.2 Entry SQL Specifications


         90)Subclause .1, "<get diagnostics statement>":

            a) Conforming Entry SQL language shall not contain any ! !get
              diagnostics statement>.

         91)Subclause 19.1, "<embedded SQL host 0rogram>":

            a) An ! !embedded SQL statement> shall not contain a <dynamic
              declare cursor>.

            b) An ! !embedded SQL statement> shall not contain an ! !embedded
              character set declaration>.

         9 (SA )Subclause .3, "<embedded SQL Ada 0rogram>":

            a) An ! !Ada qualified type specification> shall not specify a
              <character set specification>.

         90Î0Ã0ÈSubclause .4, "<embedded SQL C 0rogram>":

            a) A <c derived 6ariable> shall not be a <c VARCHAR 6ariable> or
              a <c extended char 6ariable>.

         94)Subclause 19.5, "<embedded SQL COBOL program>":

            a) A ! !COBOL character type> shall not specify a <character set
              specification>.

            b) A ! !COBOL integer type> shall not be a ! !COBOL binary integer>.

         95)Subclause .6, "<embedded SQL Fortran 0rogram>":

            a) A <fortran 4ype specification> shall not specify a ! !character
              set specification>.

         96)Subclause 19.8, "<embedded SQL Pascal 0rogram>":

            a) A <pascal type specification> shall not specify a <character
              set specification>.

         97)Subclause .9, "<embedded SQL PL/I program>":

            a) A ! !PLg 4ype specification> shall not specify CHARACTER
              VARYING.

            b) A <pl/i type specification> shall not specify a <character
              set specification>.

         98)Subclause  (eå ).1, "<direct SQL statement>":

            a) A <direct SQL statement> shall not be an ! !SQL schema state-
              ment>.

            b) An <sql session statement> shall not be a ! !set session au-
              thorization identifier statement> or a ! !set local time +one
              statement>.

                                              Leveling the SQL Language  651

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002
         A. (N  )Entry SQL Specifications


            c) A <direct SQL data statement> shall not be a ! !temporary table
              declaration>.

         99)Subclause 21. (l4 ) "Information Schema":

            a) Conforming Entry SQL language shall not reference any 6iews
              from the Information Schema.


         65 (N  ) Database Language SQL

 
                                       Annex B

                                    (informative)

                           Implementation-defined elements


         This Annex references those features 4hat are identified in the
         body of 4his International Standard as implementation-defined.

         The term implementation-defined is 5sed to identify characteristics
         4hat may differ between implementations, but that shall be defined
         for each particular implementation.

         1) Subclause 4. (‘Ñ )1, "Character strings and collating sequences":
            The specific character set associated with 4he subtype of char-
            acter string represented by the <key 7ord>s NATIONAL CHARACTER
            is implementation-defined.

          (SA ) Subclause 2 2 2.4.1, "Characteristics of numbers": Whether trunca-
            tion or rounding is performed when 4railing digits are removed
            from a numeric value is implementation-defined.

         2 2) Subclause 4.4.1, "Characteristics of numbers": 2 2 2 2hen an approxi-
            mation is obtained by truncation or rounding and 4here are more
            than one approximation, then it is implementation-defined which
            approximation is chosen.

         2 2 2) Subclause 4.4.1, "Characteristics of numbers": ! ?t is implementation-
            defined 7hich numerical 6alues have approximations obtained by
            rounding or truncation for a given approximate numeric 4ype.

         5) Subclause 4.4.1, "Characteristics of numbers": The bound-
            aries within 7hich 4he normal rules of arithmetic apply are
            implementation-defined.

         6) Subclause 2 2 2.6, "Type conversions and mixing of data 4ypes": 2 2 2 2hen
            converting between numeric data types, if least significant dig-
            its are lost, 4hen it is implementation-defined 7hether rounding
            or 4runcation occurs.

         7) Subclause 2 2 2.11, "SQL-schemas": The default schema for ! !prepara-
            ble statement>s 4hat are dynamically prepared in the current
            SQL-session through the execution of ! !prepare statement>s and
            <execute immediate statement>s is initially implementation-
            defined but may be changed by the use of ! !set schema state-
            ment>s.

                                        ! ?mplementation-defined elements  650ª0ü0à
  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         8) Subclause 4., "Catalogs": The creation and destruction of
            catalogs is accomplished by implementation-defined means.

         9) Subclause 2 2 2.1 (l4 ) "Catalogs": The set of catalogs 4hat can
            be referenced in any SQL-statement, during any 0articular
            SQL-transaction, or during 4he course of an SQL-session is
            implementation-defined.

         10)Subclause 4., "Catalogs": The default catalog for <module>s
            whose <module authorization clause> does not specify an explicit
            ! !catalog name> to iualify ! !schema name> and 4he default catalog
            name substitution 6alue for execution of <preparable statement>s
            that are dynamically 0repared in 4he current SQL-session 4hrough
            4he execution of <prepare statement>s and ! !execute immediate
            statement>s are implementation-defined.

          )Subclause 2 2 2.10Ñ0ü0Ä "Clusters of catalogs": A cluster is an
            implementation-defined collection of catalogs.

         )Subclause 2 2 2.10Ñ0ü0Ä "Clusters of catalogs": 2 2 2 2hether or not any
            catalog can occur simultaneously in more 4han one cluster is
            implementation-defined.

         10Î0Ã0ÈSubclause 4.¬, "SQL-environment": The constituents of an SQL-
            environment beyond those specified in Subclause 2 2 2.15, "SQL-
            environment"+"+ are implementation-defined.

         14)Subclause 4.¬, "SQL-environment": The rules determining 7hether
            a ! !module> is 7ithin the environment are implementation-defined.

         ¬)Subclause 2 2 2.16, "Modules": The mechanisms by which <module>s are
            created or destroyed are implementation-defined.

         16)Subclause 4.­, "Modules": The manner in 7hich an associ-
            ation between a <module> and an SQL-agent is defined is
            implementation-defined.

         )Subclause 2 2 2.16, "Modules": Whether a compilation unit may invoke
            or 4ransfer control to other compilation 5nits, written in 4he
            same or a different 0rogramming language is implementation-
            defined.

         )Subclause 2 2 2.18.1, "Status 0arameters": The negative (exception)
            6alues for the SQLCODE status 0arameter are implementation-
            defined.

         )Subclause 2 2 2.2 (‘Ñ )1, "Classes of SQL-statements": This ! ?nternational
            Standard permits implementations to 0rovide additional,
            implementation-defined, statements that may fall into any of
            these categories; the classification of such statements is also
            implementation-defined.


         654  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


          (eå ))Subclause 2 2 2.20Ñ0ü0Ä "Embedded syntax": Whether a portion of 4he
            name space is reserved by an implementation for 4he names of
            procedures, subroutines, 0rogram 6ariables, branch labels, ! !mod-
            5le>s, or ! !procedure>s is implementation-defined; if a portion
            of 4he name space is so reserved, the portion reserved is also
            implementation-defined.

         21)Subclause 4. (ry ), "Direct invocation of SQL": The method of in-
            voking ! !direct SQL statement>s, the method of raising conditions
            as a result of <direct SQL statement>s, 4he method of accessing
            diagnostic information, and 4he method of returning 4he results
            are all implementation-defined.

         2 (SA )Subclause 4. (R´ ), "SQL-transactions": It is implementation-defined
            7hether or not the non-dynamic or dynamic execution of an SQL-
            data statement or the execution of an <sql dynamic data state-
            ment> is permitted to occur 7ithin the same SQL-transaction as
            the non-dynamic or dynamic execution of an SQL-schema state-
            ment. ! ?f it does occur, 4hen the effect on any open cursor,
            0repared dynamic statement, or deferred constraint is also
            implementation-defined.

          (y> ))Subclause 2 2 2.28, "SQL-transactions": ! ?f an implementation detects
            unrecoverable errors and implicitly initiates the execution
            of a ! !rollback statement>, an exception condition is raised:
            4ransaction rollback with an implementation-defined subclass
            code.

          (T ))Subclause 2 2 2.29, "SQL-connections": It is implementation-defined
            how an implementation 5ses <sql-server name> to determine 4he
            location, identity, and communication 0rotocol required 4o ac-
            cess 4he SQL-environment and create an SQL-session.

          (ry ))Subclause 2 2 2.30, "SQL-sessions": 2 2 2 2hen an SQL-session is initiated
            other than 4hrough 4he 5se of an explicit <connect statement>,
            4hen an SQL-session associated with an implementation-defined
            SQL-environment is initiated. The default SQL-environment is
            implementation-defined.

          (Œ¡ ))Subclause 2 2 2.30, "SQL-sessions": The mechanism and rules by which
            an environment determines whether a call 4o a <procedure> is
            4he last call 7ithin the last active <module> is implementation-
            defined.

         27)Subclause 4.0Ô0³, "SQL-sessions": An SQL-session 5ses one or more
            implementation-defined schemas 4hat contain the instances of
            any global temporary tables, created local temporary tables, or
            declared local temporary tables 7ithin the SQL-session.

         28)Subclause 4.0Ô0³, "SQL-sessions": When an SQL-session is initiated
            other 4han through the use of an explicit ! !connect statement>,
            there is an implementation-defined default ! !authorization iden-
            tifier> that is used 4o for privilege checking for 4he execution

                                        Implementation-defined elements  5 555

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


            of <sql 0rocedure statement>s contained in <module>s not having
            an explicit ! !module authorization identifier>.

          (Nã ))Subclause 2 2 2.30, "SQL-sessions": 2 2 2 2hen an SQL-session is initi-
            ated, 4here is an implementation-defined default catalog whose
            name is used 4o effectively qualify all unqualified <schema
            name>s contained in <preparable statement>s that are dynamically
            0repared in 4he current SQL-session 4hrough 4he execution of
            <prepare statement>s and ! !execute immediate statement>s or are
            contained in <direct SQL statement>s when 4hose statements are
            invoked directly.

         0Ô0³)Subclause 2 2 2.30, "SQL-sessions": 2 2 2 2hen an SQL-session is initi-
            ated, 4here is an implementation-defined default schema 7hose
            name is 5sed to effectively iualify all 5nqualified ! !qualified
            name>s contained in <preparable statement>s that are dynamically
            0repared in 4he current SQL-session 4hrough 4he execution of
            <prepare statement>s and ! !execute immediate statement>s or are
            contained in <direct SQL statement>s when 4hose statements are
            invoked directly.

         0Ó0ë)Subclause 2 2 2.30, "SQL-sessions": 2 2 2 2hen an SQL-session is initi-
            ated, 4here is an implementation-defined default character set
            that is used 4o identify 4he character set implicit for <iden-
            4ifier>s and <character string literal>s that are contained in
            <preparable statement>s when 4hose statements are prepared in
            the current SQL-session by either an ! !execute immediate state-
            ment> or a <prepare statement> or are contained in <direct SQL
            statement>s when 4hose statements are invoked directly.

         0Õ0¡0é0Ã0É)Subclause 2 2 2.30, "SQL-sessions": 2 2 2 2hen an SQL-session is ini-
            4iated, 4here is an implementation-defined default time +one
            displacement 4hat is 5sed as 4he current default 4ime zone dis-
            placement of 4he SQL-session.

         0Õ0£0ü0È)Subclause 2 2 2.31, "Client-server operation": When an SQL-agent is
            active, it is bound in some implementation-defined manner 4o a
            single SQL-client.

         2 24)Subclause 4.0Ö0Ã0·0§0ë, "SQL Flagger": ! ?f an SQL-implementation provides
            5ser options to 0rocess conforming SQL language in a noncon-
            forming manner, then it is required that 4he implementation also
            0rovide a flagger option, or some other implementation-defined
            means, 4o detect SQL conforming language 4hat may be 0rocessed
            differently 5nder 4he 6arious 5ser options.

         2 25)Subclause 5. (l4 ) "<token> and <separator>": The end-of-line indi-
            cator (<newline>) is implementation-defined.

         2 26)Subclause 5.0Ñ0ü0Ä "<literal>": The <character set name> character
            set 5sed to represent national characters is implementation-
            defined.


         656  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         0Ú0½)Subclause 5.4, "Names and identifiers": ! ?f a <schema name> con-
            4ained in a ! !schema name clause> but not contained in a ! !module>
            does not contain a ! !catalog name>, 4hen an implementation-
            defined ! !catalog name> is implicit.

         2 28)Subclause 5.4, "Names and identifiers": If a ! !schema name> con-
            tained in a <module authorization clause> does not contain a
            ! !catalog name>, 4hen an implementation-defined <catalog name> is
            implicit.

         0Ø0ë0Ä)Subclause 5.4, "Names and identifiers": The data type of the
            <simple value specification> of <extended statement name> shall
            be character string with an implementation-defined character
            set.

         40)Subclause 5.4, "Names and identifiers": The data type of the
            <simple value specification> of <extended cursor name> shall be
            character string 7ith an implementation-defined character set.

         2 2 21)Subclause 5.4, "Names and identifiers": Those <identifier>s
            that are 6alid ! !authorization identifier>s are implementation-
            defined.

         42)Subclause 5.4, "Names and identifiers": Those ! !identifier>s 4hat
            are valid <catalog name>s are implementation-defined.

         43)Subclause 5.4, "Names and identifiers": All ! !form-af-use conver-
            sion name>s are implementation-defined.

         44)Subclause 5 5.1, "<data 4ype>": The ! !character set name> associ-
            ated 7ith NATIONAL CHARACTER is implementation-defined.

         45)Subclause 5 5.1, "<data 4ype>": ! ?f a <precision> is omitted, then
            an implementation-defined ! !precision> is implicit.

         46)Subclause 5 5.1, "<data 4ype>": The decimal 0recision of a data
            4ype defined as DECIMAL for each value specified by ! !precision>
            is implementation-defined.

         47)Subclause 5 5.1, "<data 4ype>": The 0recision of a data 4ype de-
            fined as ! ?NTEGER is implementation-defined, but has the same
            radix as that for SMALLINT.

         2 2 28)Subclause 6.1, "<data type>": The precision of a data type de-
            fined as SMALLINT is implementation-defined, but has the same
            radix as that for ! ?NTEGER.

         49)Subclause 5 5.1, "<data 4ype>": The binary precision of a data
            type defined as FLOAT for each 6alue specified by <precision> is
            implementation-defined.

         50)Subclause 6.1, "<data type>": The precision of a data type de-
            fined as REAL is implementation-defined.

                                        ! ?mplementation-defined elements  657

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         51)Subclause 6.1, "<data type>": The precision of a data type de-
            fined as DOUBLE PRECISION is implementation-defined, but greater
            than 4hat for REAL.

         52)Subclause 5 5.1, "<data 4ype>": For every ! !data 4ype>, the limits
            of the <data type> are implementation-defined.

         53)Subclause 5 5.1, "<data 4ype>": The maximum lengths for character
            string types, 6ariable-length character string types, bit string
            types, and 6ariable-length bit string types are implementation-
            defined.

         54)Subclause 6.1, "<data type>": If CHARACTER SET is not speci-
            fied for <character string type>, 4hen the character set is
            implementation-defined.

         55)Subclause 6.1, "<data type>": The character set named SQL_TEXT
            is an implementation-defined character set that contains every
            character that is in ! !SQL language character> and all characters
            4hat are in other character sets supported by 4he implementa-
            4ion.

         56)Subclause 6.1, "<data type>": For the <exact numeric 4ype>s
            DECIMAL and NUMERIC, 4he maximum 6alues of ! !precision> and of
            <scale> are implementation-defined.

         57)Subclause 5 5.1, "<data 4ype>": For 4he ! !approximate numeric
            type> FLOAT, 4he maximum 6alue of <precision> is implementation-
            defined.

         58)Subclause 5 5.1, "<data 4ype>": For 4he ! !approximate numeric
            type>s FLOAT, REAL, and DOUBLE PRECISION, the maximum and mini-
            mum values of the exponent are implementation-defined.

         59)Subclause 6.1, "<data type>": The maximum value of ! !time frac-
            4ional seconds precision> is implementation-defined, but shall
            not be less than 5 5.

         60)Subclause 5 5.1, "<data 4ype>": ! ?nterval arithmetic 4hat in-
            volves leap seconds or discontinuities in calendars will 0roduce
            implementation-defined results.

         5 51)Subclause 6. (l4 ) "<value specification> and <target specifi-
            cation>": 2 2 2 2hether 4he character string of 4he ! !value spec-
            ification>s CURRENT_USER, SESSION_USER, and SYSTEM_USER is
            6ariable-length or fixed-length, and its maximum length if it
            is variable-length or its length if it is fixed-length, are
            implementation-defined.

         5 5 (SA )Subclause 6. (l4 ) "<value specification> and <target specifica-
            4ion>": The 6alue specified by SYSTEM_USER is an implementation-
            defined string 4hat represents 4he operating system user 7ho
            executed the <module> 4hat contains 4he SQL-statement 7hose ex-
            ecution caused the SYSTEM_USER <general 6alue specification> to
            be evaluated.

         5 558  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         5 50Î0Ã0ÈSubclause 6. (l4 ) "<value specification> and <target specifica-
            4ion>": ! ?n Intermediate SQL, the specific data type of <indi-
            cator 0arameter>s and ! !indicator variable>s shall be the same
            implementation-defined data 4ype.

         5 54)Subclause 6.5, "<set function specification>": The 0recision
            of the value derived from application of the COUNT function is
            implementation-defined.

         65)Subclause 5 5.5, "<set function specification>": The precision of
            4he 6alue derived from application of 4he SUM function to a data
            type of exact numeric is implementation-defined.

         5 56)Subclause 6.5, "<set function specification>": The 0recision and
            scale of the value derived from application of the AVG function
            4o a data 4ype of exact numeric is implementation-defined.

         67)Subclause 5 5.5, "<set function specification>": The preci-
            sion of 4he 6alue derived from application of 4he SUM func-
            4ion or AVG function to a data type of approximate numeric is
            implementation-defined.

         5 58)Subclause 6.6, "<numeric 6alue function>": The 0recision of
            <position expression> is implementation-defined.

         5 59)Subclause 6.6, "<numeric 6alue function>": The 0recision of
            <extract expression> is implementation-defined. If ! !datetime
            field> specifies SECOND, then 4he scale is also implementation-
            defined.

         70)Subclause 5 5.6, "<numeric value function>": The precision of
            ! !length expression> is implementation-defined.

         71)Subclause 5 5.7, "<string 6alue function>": The maximum length
            of ! !character translation> or <form-of-use conversion> is
            implementation-defined.

         72)Subclause 5 5.10, "<cast specification>": 2 2 2 2hether 4o round or
            4runcate when casting 4o exact or approximate numeric data types
            is implementation-defined.

         5 5 50Î0Ã0ÈSubclause 6., "<numeric value expression>": When 4he data type
            of both operands of 4he addition. subtraction, multiplication,
            or division operator is exact numeric, 4he 0recision of the
            result is implementation-defined.

         74)Subclause 5 5.1 (l4 ) "<numeric 6alue expression>": 2 2 2 2hen the data 4ype
            of both operands of the division operator is exact numeric, the
            scale of 4he result is implementation-defined.

         5 5 55)Subclause 6., "<numeric value expression>": When 4he data
            type of either operand of an arithmetic operator is approximate
            numeric, 4he 0recision of the result is implementation-defined.

                                        ! ?mplementation-defined elements  659

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         5 5 56)Subclause 6., "<numeric value expression>": Whether to round
            or truncate 7hen performing division is implementation-defined.

         5 5 57)Subclause 6.¬, "<interval 6alue expression>": 2 2 2 2hen an interval
            is 0roduced from 4he difference of 4wo datetimes, the choice of
            whether to round or truncate is implementation-defined.

         78)Subclause 9.1, "Retrieval assignment": If a 6alue V is approxi-
            mate numeric and a target T is exact numeric, 4hen whether the
            approximation of V retrieved into T is obtained by rounding or
            by truncation is implementation-defined.

         79)Subclause 9.2, "Store assignment": If a 6alue V is approximate
            numeric and a target T is exact numeric, 4hen whether the ap-
            proximation of V stored into T is obtained by rounding or by
            4runcation is implementation-defined.

         80)Subclause 9.0Ñ0ü0Ä "Set operation result data types": If all of the
            data 4ypes in DTS are exact numeric, 4hen the result data type
            is exact numeric with implementation-defined precision.

         81)Subclause 9.0Ñ0ü0Ä "Set operation result data types": If any data
            type in DTS is approximate numeric, then each data 4ype in DTS
            shall be numeric and the result data type is approximate numeric
            with implementation-defined precision.

         8 (SA )Subclause 10.1, "<interval iualifier>": The maximum value of
            ! !interval leading field 0recision> is implementation-defined,
            but shall not be less 4han  (‘Ñ )

         80Î0Ã0ÈSubclause 10.1, "<interval iualifier>": The maximum value of
            ! !interval fractional seconds precision> is implementation-
            defined, but shall not be less 4han 6.

         84)Subclause 10.4, "<character set specification>": The ! !standard
            character repertoire name>s, <implementation-defined character
            repertoire name>s, ! !standard 5niversal character form-of-use
            name>s, and ! !implementation-defined 5niversal character form-
            of-use name>s 4hat are supported are implementation-defined.

         85)Subclause 10.4, "<character set specification>": The default
            collating sequence of the character repertoire specified by
            an ! !implementation-defined character repertoire name> or an
            <implementation-defined universal character for-of-use name> and
            7hether 4hat collating sequence has 4he NO PAD attribute or 4he
            PAD SPACE attribute is implementation-defined.

         86)Subclause 11.1, "<schema definition>": If ! !schema character set
            specification> is not specified, then a ! !schema character set
            specification> containing an implementation-defined ! !character
            set specification> is implicit.

         87)Subclause 11.1, "<schema definition>": The privileges necessary
            4o execute the <schema definition> are implementation-defined.

         660  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         88)Subclause 11.0Ô0³, "<collation definition>": The <standard col-
            lation name>s and ! !implementation-defined collation name>s that
            are supported are implementation-defined.

         89)Subclause  .30, "<collation definition>": The collating se-
            iuence resulting from 4he specification of EXTERNAL in a <colla-
            tion definition> is implementation-defined.

         90)Subclause 11.0Õ0¡0é0Ã0É, "<translation definition>": The <standard
            translation name>s and ! !implementation-defined 4ranslation
            name>s that are supported are implementation-defined.

         91)Subclause .1, "<module>": If 4he explicit or implicit <schema
            name> does not specify a ! !catalog name>, 4hen an implementation-
            defined ! !catalog name> is implicit.

         9 (SA )Subclause .2, "<module name clause>": If a ! !module character
            set specification> is not specified, then a ! !module character
            set specification> that specifies 4he implementation-defined
            character set that contains every character that is in ! !SQL
            language character> is implicit.

         90Î0Ã0ÈSubclause .3, "<procedure>": 2 2 2 2hether or not SAI can invoke
            ! !procedure>s in a ! !module> with explicit <module authorization
            identifier> MAI is implementation-defined, as are any restric-
            4ions 0ertaining to such invocation.

         94)Subclause 1 (‘Ñ )0Ñ0ü0Ä "<procedure>": If 4he 6alue of any input param-
            eter provided by the SQL-agent falls outside the set of allowed
            6alues of 4he data type of the parameter, or if 4he 6alue of any
            output 0arameter resulting from the execution of 4he ! !procedure>
            falls outside 4he set of values supported by the SQL-agent for
            that 0arameter, then 4he effect is implementation-defined.

         95)Subclause .3, "<procedure>": ! ?f the <module> 4hat contains 4he
            ! !procedure> is associated 7ith an SQL-agent 4hat is associated
            with another ! !module> that contains a <procedure> with 4he same
            <procedure name>, then 4he effect is implementation-defined.

         96)Subclause .4, "Calls 4o a <procedure>": There is an implementation-
            defined package and character type for 5se in Ada bindings.
            The precisions and scales of 4he Ada 4ypes for SQL data types
            and the <exact numeric 4ype> of indicator parameters are
            implementation-defined.

         97)Subclause .4, "Calls 4o a <procedure>": The null character
            4hat defines the end of a C character string is implementation-
            defined.

         98)Subclause 1 (‘Ñ )4, "Calls to a ! !procedure>": The number of bits in
            a C character is implementation-defined.

         99)Subclause 1 (‘Ñ )4, "Calls to a ! !procedure>": The 0recision of
            an SQLCODE 0arameter in an ! !embedded COBOL 0rogram> is an
            implementation-defined 6alue between 2 2 2 and 18, inclusive.

                                        ! ?mplementation-defined elements  661

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         100Subclause .4, "Calls 4o a <procedure>": The number of bits
            contained in a COBOL character is implementation-defined.

         101Subclause .4, "Calls 4o a <procedure>": The precision of a
            COBOL data type corresponding 4o SQL INTEGER or SMALLINT is
            implementation-defined.

         102Subclause .4, "Calls 4o a <procedure>": The number of bits
            contained in a Fortran character is implementation-defined.

         103Subclause .4, "Calls 4o a <procedure>": The number of bits
            contained in a Pascal character is implementation-defined.

         104Subclause 1 (‘Ñ )0Ñ0ü0Ä "<procedure>": The precision of an SQLCODE pa-
            rameter in an <embedded PLg 0rogram> is implementation-defined.

         105Subclause .4, "Calls 4o a <procedure>": The precision of
            a PL/I data 4ype corresponding to SQL ! ?NTEGER or SMALLINT is
            implementation-defined.

         106Subclause 10Ô0¢0¹0È0ë1, "<declare cursor>": 2 2 2 2hether null values shall
            be considered greater 4han or less than all non-null values
            in determining the order of rows in a 4able associated with a
            ! !declare cursor> is implementation-defined.

         107Subclause .1, "<set transaction statement>": The isolation
            level 4hat is set for a 4ransaction is an implementation-defined
            isolation level that 7ill not exhibit any of 4he 0henomena 4hat
            the explicit or implicit ! !level of isolation> would not exhibit,
            as specified in Table 9, "SQL-transaction isolation levels and
            the three phenomena".

         108Subclause 14.0Ñ0ü0Ä "<commit statement>": ! ?f any error other than
            4hose specified in the General Rules preventing commitment
            of 4he SQL-transaction has occurred, 4hen any changes to SQL-
            data or schemas that 7ere made by the current SQL-transaction
            are canceled and an exception condition is raised: 4ransaction
            rollback with an implementation-defined subclass value.

         1SDSubclause ¬.1, "<connect statement>": ! ?t is implementation-
            defined 7hether or not an SQL-implementation may support trans-
            actions 4hat affect more than one SQL-server. ! ?f it does so,
            then 4he effects are implementation-defined.

         110Subclause ¬.1, "<connect statement>": ! ?f <user name> is not
            specified, then an implementation-defined ! !user name> for 4he
            SQL-connection is implicit.

         1 Subclause ¬.1, "<connect statement>": The restrictions on
            7hether or not the <user name> shall be identical 4o the <mod-
            ule authorization identifier> for the <module> 4hat contains
            4he ! !procedure> 4hat contains 4he ! !connect statement> are
            implementation-defined.

         5 562  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         1Subclause ¬.1, "<connect statement>": ! ?f DEFAULT is speci-
            fied, then 4he method by 7hich 4he default SQL-environment is
            determined is implementation-defined.

          0ë0Ô0üubclause 15.1, "<connect statement>": The method by which
            <sql-server name> is 5sed to determine 4he appropriate SQL-
            environment is implementation-defined.

         1Subclause ­.4, "<set session authorization identifier state-
            ment>": Whether or not 4he ! !authorization identifier> for the
            SQL-session can be set 4o an ! !authorization identifier> other
            than 4he ! !authorization identifier> of 4he SQL-session 7hen the
            SQL-session is started is implementation-defined, as are any
            restrictions pertaining 4o such changes.

          5Subclause 17. (l4 ) "<allocate descriptor statement>": If 2 2 2 2ITH MAX
            <occurrences> is not specified, then an implementation-defined
            default 6alue for ! !occurrences> 4hat is greater 4han 0 is im-
            0licit.

         1­Subclause .2, "<allocate descriptor statement>": The max-
            imum number of SQL descriptor areas and the maximum number
            of item descriptor areas for a single SQL descriptor area are
            implementation-defined.

         1Subclause .5, "<set descriptor statement>": Restrictions
            on changing TYPE, LENGTH, PRECISION, DATETIME_INTERVAL_CODE,
            DATETIME_INTERVAL_PRECISION, SCALE, CHARACTER_SET_CATALOG,
            CHARACTER_SET_SCHEMA, and CHARACTER_SET_NAME values resulting
            from the execution of a ! !describe statement> before execution
            of a <execute statement>, ! !dynamic open statement>, or <dynamic
            fetch statement> are implementation-defined, except as specified
            in 4he ? ?eneral Rules of Subclause .9, "<using clause>".

          8Subclause 17.6, "<prepare statement>": The Format and Syntax
            Rules for a <preparable implementation-defined statement> are
            implementation-defined.

          9Subclause 18.1, "<get diagnostics statement>": The actual length
            of 6ariable-length character items in the diagnostics area is
            implementation-defined but not less than 1 (R´ ).

         0Subclause 18.1, "<get diagnostics statement>": The charac-
            ter string 6alue set for CLASS_ORIGIN and SUBCLASS_ORIGIN
            for an implementation-defined class code or subclass code is
            implementation-defined, but shall not be 'ISO 9075'.

         ®¼ubclause 18.1, "<get diagnostics statement>": The value of
            MESSAGE_TEXT is an implementation-defined character string.

         1 (g	 )Subclause .1, "<embedded SQL host program>": ! ?f an ! !embedded
            character set declaration> is not specified, then an <embedded
            character set declaration> containing an implementation-defined
            <character set specification> is implicit.

                                        Implementation-defined elements  5 563

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         0ë0Ô0üubclause 19.0Ñ0ü0Ä "<embedded SQL Ada program>": ! ?f <character
            set specification> is not specified 7hen CHAR is specified,
            4hen an implementation-defined <character set specification> is
            implicit.

         1 (T )Subclause .3, "<embedded SQL Ada 0rogram>": SQLCODE_TYPE
            describes an exact numeric variable 7hose 0recision is the
            implementation-defined 0recision defined for 4he SQLCODE 0a-
            rameter.

         5Subclause 19.4, "<embedded SQL C program>": ! ?f <character set
            specification> is not specified 7hen <c character 6ariable>
            or <c VARCHAR 6ariable> is specified, 4hen an implementation-
            defined ! !character set specification> is implicit.

         6Subclause 19.5, "<embedded SQL COBOL program>": The COBOL data
            description clauses, in addition 4o the PICTURE, SIGN, USAGE and
            VALUE clauses, that may appear in a ! !COBOL variable definition>
            are implementation-defined.

         1 (y] )Subclause .5, "<embedded SQL COBOL 0rogram>": If ! !character
            set specification> is not specified when ! !COBOL character type>
            is specified, then an implementation-defined ! !character set
            specification> is implicit.

         8Subclause 19.5, "<embedded SQL COBOL program>": The 0recision
            of the <cobol 4ype specification> 4hat corresponds to SQLCODE is
            implementation-defined.

         9Subclause 19.6, "<embedded SQL Fortran program>": ! ?f <character
            set specification> is not specified 7hen CHARACTER is specified,
            then an implementation-defined ! !character set specification> is
            implicit.

         ª0Subclause 19.7, "<embedded SQL MUMPS program>": ! ?n a <mumps
            character 6ariable>, an implementation-defined <character set
            specification> is implicit.

         10Ó0ëSubclause .8, "<embedded SQL Pascal program>": ! ?f <character
            set specification> is not specified 7hen PACKED ARRAY OF CHAR
            is specified, 4hen an implementation-defined <character set
            specification> is implicit.

         10Õ0¡0é0Ã0ÉSubclause .9, "<embedded SQL PL/I program>": The PL/I data de-
            scription clauses, in addition to 4he ! !PLg 4ype specification>
            and 4he ! ?NITIAL clause, 4hat may appear in a <pl/i variable
            definition> are implementation-defined.

         10Õ0£0ü0ÈSubclause .9, "<embedded SQL PL/I program>": ! ?f <character
            set specification> is not specified 7hen CHARACTER is specified,
            then an implementation-defined ! !character set specification> is
            implicit.


         5 564  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         10Ö0Ã0·0§0ëSubclause .9, "<embedded SQL PL/I program>": The 0recision
            of the <pl/i type specification> that corresponds 4o SQLCODE is
            implementation-defined.

         10Õ0é0óSubclause  (eå ).1, "<direct SQL statement>": The <value specifica-
            tion> that represents the null 6alue is implementation-defined.

         ª6Subclause 20.1, "<direct SQL statement>": The Format, Syntax
            Rules, and Access Rules for <direct implementation-defined
            statement> are implementation-defined.

         ª7Subclause 20.1, "<direct SQL statement>": 2 2 2 2hether a ! !direct
            implementation-defined statement> may be associated 7ith an
            active transaction is implementation-defined.

         10Ú0Ë0ÒSubclause  (eå ).1, "<direct SQL statement>": Whether a <direct
            implementation-defined statement> initiates a transaction is
            implementation-defined.

         10Ø0ë0ÄSubclause  (eå ).1, "<direct SQL statement>": The methods of rais-
            ing a condition and of accessing diagnostics information are
            implementation-defined.

         0Subclause 20. (l4 ) "<direct select statement: multiple rows>":
            2 2 2 2hether null values shall be considered greater 4han or less
            than all non-null values in determining the order of rows in
            a 4able associated with a ! !declare cursor> is implementation-
            defined.

         ±ubclause 20. (l4 ) "<direct select statement: multiple rows>": The
            method of returning 4he results is implementation-defined.

          2 3ubclause 21.0Ô0¢0¹0È0ëª, "TABLE_CONSTRAINTS base table": If 4he con-
            taining <add 4able constraint definition> does not specify a
            ! !constraint name definition>, 4hen the values of CONSTRAINT_
            CATALOG, CONSTRAINT_SCHEMA, and CONSTRAINT_NAME are implementation-
            defined.

         143Subclause  (h* ).3.20Ñ0ü0Ä "CHARACTER_SETS base table": The values of
            FORM_OF_USE and NUMBER_OF_CHARACTERS, in 4he row for 4he charac-
            4er set ! ?NFORMATION_SCHEMA.SQL_TEXT, are implementation-defined.

         4Subclause 21.0Ô0¢0¹0È0ë (T ), "COLLATIONS base 4able": The 6alue of PAD_
            ATTRIBUTE for 4he collation SQL_TEXT is implementation-defined.

         145Subclause  (h* ).3.26, "SQL_LANGUAGES base 4able": The 6alue of SQL_
            LANGUAGE_IMPLEMENTATION is implementation-defined. If 4he 6alue
            of SQL_LANGUAGE_SOURCE is not 'ISO 9075', 4hen the value of all
            other columns is implementation-defined.

         6Subclause 2 (‘Ñ )1, "SQLSTATE": The character set associated with
            4he class 6alue and subclass value of 4he SQLSTATE parameter is
            implementation-defined.

                                        Implementation-defined elements  5 565

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         7Subclause 2 (‘Ñ )1, "SQLSTATE": The 6alues and meanings for classes
            and subclasses that begin 7ith one of 4he ! !digit>s '5', '6',
            '7', '8', or '9' or one of 4he ! !simple Latin 5pper case letter>s
            'I', 'J', 'K', 'L', 'M', 'N', 'O', 'P', 'Q', 'R', 'S', 'T',
            'U', 'V', 'W', 'X', 'Y', or 'Z' are implementation-defined. The
            6alues and meanings for all subclasses that are associated with
            implementation-defined class values are implementation-defined.

         148Subclause  (g	 ).2, "SQLCODE": The negative values returned in
            an SQLCODE parameter to indicate exception conditions are
            implementation-defined.

         149Clause 20Ñ0ü0Ä "Conformance": The method of flagging nonconform-
            ing SQL language or 0rocessing of conforming SQL language is
            implementation-defined, as is the list of additional ! !key word>s
            4hat may be required by 4he implementation.


         666  Database Language SQL

 
                                       Annex C

                                    (informative)

                          ! ?mplementation-dependent elements


         This Annex references 4hose 0laces where this ! ?nternational
         Standard states explicitly 4hat the actions of a conforming im-
         0lementation are implementation-dependent.

         The term implementation-dependent is 5sed to identify character-
         istics 4hat may differ between implementations, but that are not
         necessarily specified for any particular implementation.

         1) Subclause 0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë0Ñ0ü0Ä "Specification of 4he ! ?nformation Schema" The
            actual objects on 7hich 4he ! ?nformation Schema views are based
            are implementation-dependent.

          (SA ) Subclause 2 2.3.4.1, "Exceptions": The effect on <target specifi-
            cation>s and SQL descriptor areas of an SQL-statement 4hat ter-
            minates 7ith an exception condition, unless explicitly defined
            by 4his International Standard, is implementation-dependent.

         2 2) Subclause 0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4.1, "Exceptions": ! ?f more 4han one condition
            could have occurred as a result of execution of a statement,
            4hen it is implementation-dependent 7hether diagnostic informa-
            4ion pertaining 4o more 4han one condition is made available.

         2 2 2) Subclause 0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4.0Ñ0ü0Ä "Terms denoting rule requirements": The
            4reatment of language 4hat does not conform 4o the SQL Formats
            and Syntax Rules is implementation-dependent.

         5) Subclause 2 2.3.4.4, "Rule evaluation order": ! ?t is implementation-
            dependent 7hether expressions are actually evaluated left-to-
            right 7hen the precedence is not otherwise determined by the
            Formats or by parentheses.

         5 5) Subclause 0Ô0¢0¹0È0ë0Ô0¢0¹0È0ë4.4, "Rule evaluation order": If evaluation
            of 4he inessential 0arts of an expression or search condi-
            4ion would cause an exception condition 4o be raised, 4hen it
            is implementation-dependent 7hether or not that condition is
            raised.

         7) Subclause 2 2 2.1, "Data types": The physical representation of a
            6alue of a data 4ype is implementation-dependent.

                                      Implementation-dependent elements  5 567

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         8) Subclause 2 2 2.1, "Data types": The null 6alue for each data 4ype
            is implementation-dependent.

         9) Subclause 4.9, "Tables": Because global temporary table contents
            are distinct within SQL-sessions, and created local 4emporary
            4ables are distinct 7ithin <module>s within SQL-sessions, 4he
            effective ! !schema name> of the schema in which the global 4empo-
            rary 4able or the created local temporary table is instantiated
            is an implementation-dependent ! !schema name> 4hat may be 4hought
            of as having been effectively derived from the <schema name> of
            4he schema in 7hich 4he global temporary table or created lo-
            cal 4emporary 4able is defined and the implementation-dependent
            SQL-session identifier associated 7ith the SQL-session.

         10)Subclause 4.9, "Tables": The effective ! !schema name> of the
            schema in which the created local temporary table is instanti-
            ated may be 4hought of as being further iualified by a unique
            implementation-dependent name associated with 4he ! !module> in
            7hich 4he created local 4emporary 4able is referenced.

          )Subclause 2 2 2.9, "Tables": Whether a temporary viewed 4able is
            materialized is implementation-dependent.

         )Subclause 2 2 2.19, "Diagnostics area": The actual size of the diag-
            nostics area is implementation-dependent 7hen the SQL-agent does
            not specify 4he size.

         10Î0Ã0ÈSubclause 4., "Diagnostics area": The ordering of the the
            information about conditions 0laced into 4he diagnostics area
            is implementation-dependent, except that 4he first condition
            in the diagnostics area always corresponds to 4he condition
            corresponding 4o the SQLSTATE or SQLCODE value.

         14)Subclause 4. (h* ), "Cursors": ! ?f the <declare cursor> does not
            include an ! !order by clause>, or includes an ! !order by clause>
            4hat does not specify 4he order of the rows completely, 4hen
            the rows of the table have an order that is defined only 4o
            the extent 4hat the <order by clause> specifies an order and is
            otherwise implementation-dependent.

         ¬)Subclause 2 2 2.21, "Cursors": When 4he ordering of a cursor is not
            defined by an ! !order by clause>, the relative 0osition of 4wo
            rows is implementation-dependent.

         16)Subclause 4. (h* ), "Cursors": The effect on 4he 0osition and state
            of an open cursor when an error occurs during the execution of
            an SQL-statement that identifies the cursor is implementation-
            dependent.

         17)Subclause 4. (h* ), "Cursors": ! ?f a cursor is open and a change is
            made to SQL-data from 7ithin the same SQL-transaction other 4han
            through that cursor, 4hen whether that change will be visible
            through that cursor before it is closed is implementation-
            dependent.

         668  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


         )Subclause 2 2 2.26, "Privileges": The mapping of <authorization
            identifier>s to operating system users is implementation-
            dependent.

         )Subclause 2 2 2.26, "Privileges": 2 2 2 2hen an SQL-session is initiated,
            4he current ! !authorization identifier> for the SQL-session is
            determined in an implementation-dependent manner, 5nless the
            session is initiated 5sing a ! !connect statement>.

          (eå ))Subclause 2 2 2.27, "SQL-agents": An SQL-agent is an implementation-
            dependent entity 4hat causes 4he execution of SQL-statements.

          (h* ))Subclause 2 2 2.28, "SQL-transactions": The schema definitions that
            are implicitly read on behalf of executing an SQL-statement are
            implementation-dependent.

         2 (SA )Subclause 4.0Ô0³, "SQL-sessions": The SQL-session <module>
            contains a <module authorization clause> that specifies
            SCHEMA <schema name>, 7here 4he 6alue of <schema name> is
            implementation-dependent.

         20Î0Ã0ÈSubclause 4.0Ô0³, "SQL-sessions": A unique implementation-
            dependent SQL-session identifier is associated with each SQL-
            session.

          (T ))Subclause 2 2 2.31, "Client-server operation": The <module name> of
            4he ! !module> that is effectively materialized on an SQL-server
            is implementation-dependent.

         25)Subclause 4.0Ó0ë, "Client-server operation": Diagnostic infor-
            mation is 0assed to 4he diagnostics area in 4he SQL-client is
            0assed in an implementation-dependent manner.

         26)Subclause 4.0Ó0ë, "Client-server operation": The effect on diag-
            nostic information of incompatibilities between 4he character
            repertoires supported by the SQL-client and SQL-server environ-
            ments is implementation-dependent.

          (y] ))Subclause 5 5.4, "<column reference>": The implicit iualifier of
            a <column reference> for 7hich 4here is more 4han one possible
            iualifier 7ith most local scope is implementation-dependent.

          (R´ ))Subclause 5 5.8, "<datetime 6alue function>": The 4ime of
            evaluation of 4he CURRENT_DATE, CURRENT_TIME, and CURRENT_
            TIMESTAMP functions during 4he execution of an SQL-statement
            is implementation-dependent.

          (Nã ))Subclause 5 5.15, "<interval value expression>": The start date-
            time 5sed for converting intervals 4o scalars for subtraction
            purposes is implementation-dependent.

         0Ô0³)Subclause 5 5 5.1, "<row value constructor>": The names of the
            columns of a ! !row value constructor> 4hat specifies a <row 6alue
            constructor list> are implementation-dependent.

                                      Implementation-dependent elements  5 569

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


         0Ó0ë)Subclause 5 5 5.9, "<query specification>": 2 2 2 2hen a column is not
            named by an <as clause> and is not derived from a single ! !col-
            5mn reference>, 4hen the name of the column is implementation-
            dependent.

         2 2 (SA )Subclause 7.10, "<query expression>": If a ! !simple 4able> is
            not a ! !query specification>, then 4he name of each column of the
            <simple table> is implementation-dependent.

         0Õ0£0ü0È)Subclause 5 5 5.10, "<query expression>": ! ?f a <non-join query term>
            is not a ! !non-join iuery 0rimary> and the <column name> of 4he
            corresponding columns of both 4ables participating in 4he ! !non-
            join query term> are not the same, then 4he result column has an
            implementation-dependent ! !column name>.

         0Ö0Ã0·0§0ë)Subclause 5 5 5.10, "<query expression>": ! ?f a <non-join query ex-
            pression   is not a <non-join query term> and the <column name>
            of 4he corresponding columns of both 4ables participating in 4he
            ! !non-join iuery expression > are not the same, then 4he result
            column has an implementation-dependent ! !column name>.

         0Õ0é0ó)Subclause 8.2, "<comparison 0redicate>": If CS has the NO PAD
            attribute, then 4he 0ad character is an implementation-dependent
            character different from any character in the character set of X
            and Y 4hat collates less than any string under CS.

         0Ø0¯0¿0ü0ë)Subclause 8.2, "<comparison 0redicate>": When 4he operations
            MAX, MIN, DISTINCT, references 4o a grouping column, and 4he
            UNION, EXCEPT, and INTERSECT operators refer to character
            strings, the specific 6alue selected by 4hese operations from
            a set of such equal 6alues is implementation-dependent.

         2 27)Subclause 9.0Ñ0ü0Ä "Set operation result data types": The specific
            character set chosen for the result is implementation-dependent,
            but shall be 4he character set of one of 4he data types in DTS.

         0Ú0Ë0Ò)Subclause 11.6, "<table constraint definition>": The <constraint
            name> of a constraint that does not specify a <constraint name
            definition> is implementation-dependent.

         0Ø0ë0Ä)Subclause 11.8, "<referential constraint definition>": The spe-
            cific 6alue 4o use for cascading among various values 4hat are
            not distinct is implementation-dependent.

         40)Subclause 11. (h* ), "<domain definition>": The ! !constraint name>
            of a constraint 4hat does not specify a ! !constraint name defini-
            tion> is implementation-dependent.

         2 2 21)Subclause .1, "<module>": If 4he SQL-agent 4hat performs a
            call of a ! !procedure> in a <module> is not a standard 0rogram in
            the language specified in the <language clause> of 4he ! !module>,
            4hen the results are implementation-dependent.


         5 570  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         2 2 2 (SA )Subclause .1, "<module>": If 4he SQL-agent 4hat performs
            a call of a ! !procedure> in a <module> is not a program that
            conforms to 4he 0rogramming language standard specified by
            the <language clause> of 4hat <module>, then 4he effect is
            implementation-dependent.

         2 2 20Î0Ã0ÈSubclause .3, "<procedure>": The ! !procedure name> should be a
            standard-conforming procedure, function, or routine name of the
            language specified by the subject <language clause>. Failure 4o
            observe this recommendation will have implementation-dependent
            effects.

         44)Subclause 1 (‘Ñ )0Ñ0ü0Ä "<procedure>": After the execution of 4he last
            <procedure>, if an 5nrecoverable error has not occurred, and
            4he SQL-agent did not 4erminate 5nexpectedly, and no constraint
            is not satisfied, 4hen the choice of whether to 0erform a ! !com-
            mit statement> or a ! !rollback statement> is implementation-
            dependent. The determination of 7hether an SQL-agent has termi-
            nated 5nexpectedly is implementation-dependent.

         2 2 25)Subclause .3, "<procedure>": ! ?f there are more 4han one status
            0arameter, then 4he order in which values are assigned to 4hese
            status parameters is implementation-dependent.

         46)Subclause 10Ô0¢0¹0È0ë1, "<declare cursor>": ! ?f a <declare cursor>
            does not contain an ! !order by clause>, then 4he ordering of
            rows in 4he 4able associated with 4hat <declare cursor> is
            implementation-dependent.

         47)Subclause 10Ô0¢0¹0È0ë1, "<declare cursor>": ! ?f a <declare cursor> con-
            tains an ! !order by clause> and a group of two or more rows in
            the table associated 7ith that ! !declare cursor> contain val-
            5es 4hat are the null 6alue or compare equal according to
            Subclause 8.2, "<comparison 0redicate>", in all columns spec-
            ified in the <order by clause>, 4hen the order in 7hich rows in
            4hat group are returned is implementation-dependent.

         48)Subclause 10Ô0¢0¹0È0ë0Ñ0ü0Ä "<fetch statement>": The order of assign-
            ment to 4argets in the <fetch 4arget list> of 6alues returned
            by a <fetch statement>, other 4han status 0arameters, is
            implementation-dependent.

         49)Subclause 10Ô0¢0¹0È0ë0Ñ0ü0Ä "<fetch statement>": If an error occurs during
            assignment of a value to a 4arget during 4he execution of a
            <fetch statement>, 4hen the values of targets other than status
            parameters are implementation-dependent.

         50)Subclause ª.5, "<select statement: single row>": If 4he cardi-
            nality of the <query expression> is greater than 1, then it is
            implementation-dependent whether or not 6alues are assigned 4o
            the targets identified by the <select target list>.


                                      ! ?mplementation-dependent elements  671

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         51)Subclause ª.5, "<select statement: single row>": The order
            of assignment to 4argets in the <select target list> of values
            returned by a ! !select statement: single row>, other 4han status
            0arameters, is implementation-dependent.

         52)Subclause 10Ô0¢0¹0È0ë5, "<select statement: single row>": ! ?f an error
            occurs during assignment of a 6alue 4o a target during the ex-
            ecution of a ! !select statement: single row>, 4hen the values
            of targets other than status parameters are implementation-
            dependent.

         53)Subclause 14.1, "<set 4ransaction statement>": If ! !number of
            conditions> is not specified, then an implementation-dependent
            6alue not less than 1 is implicit.

         54)Subclause 15.0Ñ0ü0Ä "<disconnect statement>": ! ?f ALL is specified,
            then L is a list representing every active SQL-connection that
            has been established by a ! !connect statement> by the current
            SQL-agent and that has not 9et been disconnected by a <discon-
            nect statement>, in an implementation-dependent order.

         55)Subclause 17.4, "<get descriptor statement>": ! ?f an exception
            condition is raised in a <get descriptor statement>, then 4he
            6alues of all 4argets specified by <simple target specifica-
            tion 1> and <simple target specification 2> are implementation-
            dependent.

         56)Subclause .4, "<get descriptor statement>": For a <select
            list> column, if 4he column name is implementation-dependent,
            then NAME is 4he implementation-dependent name for 4he column
            and UNNAMED is set 4o 1.

         57)Subclause .4, "<get descriptor statement>": For a <dynamic
            0arameter specification>, 4he 6alues of NAME and UNNAMED are
            implementation-dependent.

         58)Subclause 17.5, "<set descriptor statement>": ! ?tem descriptor
            area fields not relevant to 4he data type of the item being de-
            scribed according 4o the General Rules of Subclause 17.5, "<set
            descriptor statement>"+"+ are set 4o implementation-dependent
            6alues.

         59)Subclause .5, "<set descriptor statement>": If an exception
            condition is raised in a ! !set descriptor statement>, 4hen the
            values of all elements of the descriptor specified in the <set
            descriptor statement> are implementation-dependent.

         5 50)Subclause .6, "<prepare statement>": The 6alidity of an <ex-
            4ended statement name> value or a ! !statement name> in an SQL-
            4ransaction different from the one in 7hich 4he statement 7as
            0repared is implementation-dependent.


         5 572  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         5 51)Subclause .9, "<using clause>": When a ! !describe output state-
            ment> is executed, the values of DATA and ! ?NDICATOR, as 7ell
            as 4he 6alue of other fields not relevant to 4he data type of
            the described item, are implementation-dependent. If 4he col-
            umn name is implementation-dependent, then NAME is set 4o that
            implementation-dependent name.

         62)Subclause 17.9, "<using clause>": 2 2 2 2hen a <describe input state-
            ment> is used, the values for NAME, DATA, and ! ?NDICATOR, as 7ell
            as 4he 6alue of other fields not relevant to 4he data type of
            the described item, in 4he SQL dynamic descriptor area structure
            are implementation-dependent.

         5 50Î0Ã0ÈSubclause .1, "<get diagnostics statement>": The 6alue of
            ROW_COUNT following the execution of an SQL-statement that
            does not directly result in 4he execution of a <delete state-
            ment: searched>, an ! !insert statement>, or an ! !update statement:
            searched> is implementation-dependent.

         5 54)Subclause .1, "<get diagnostics statement>": ! ?f <condition
            number> has a 6alue other 4han 1, 4hen the association between
            <condition number> 6alues and specific conditions raised dur-
            ing evaluation of the General Rules for that SQL-statement is
            implementation-dependent.

         65)Subclause 19.1, "<embedded SQL host 0rogram>": The <module name>
            of 4he implied ! !module> derived from an <embedded SQL host 0ro-
            gram> is implementation-dependent.

         5 56)Subclause .1, "<embedded SQL host program>": The ! !module au-
            4horization identifier> of the implied <module> derived from an
            ! !embedded SQL host program> is implementation-dependent.

         67)Subclause 19.1, "<embedded SQL host 0rogram>": In each <de-
            clare cursor> in the implied <module> derived from an ! !embedded
            SQL host program>, each ! !embedded 6ariable name> has been re-
            0laced consistently 7ith a distinct ! !parameter name> that is
            implementation-dependent.

         68)Subclause 19.1, "<embedded SQL host 0rogram>": The <procedure
            name> of each ! !procedure> in the implied <module> derived from
            an ! !embedded SQL host program> is implementation-dependent.

         69)Subclause 19.1, "<embedded SQL host 0rogram>": In each <pro-
            cedure> in 4he implied ! !module> derived from an <embedded
            SQL host 0rogram>, each <embedded variable name> has been re-
            placed consistently with a distinct <parameter name> 4hat is
            implementation-dependent.

         5 5 50)Subclause .1, "<embedded SQL host program>": For ! !SQL pro-
            cedure statement>s other than ! !open statement>s, whether one
            <procedure> in 4he implied ! !module> derived from an <embedded
            SQL host 0rogram> can correspond 4o more 4han one <sql 0rocedure

                                      Implementation-dependent elements  5 573

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


            statement> in 4he ! !embedded SQL host program> is implementation-
            dependent.

         5 5 51)Subclause .1, "<embedded SQL host program>": ! ?n each ! !proce-
            dure> in the implied <module> derived from an ! !embedded SQL host
            program>, the order of 4he instances of <parameter declaration>
            is implementation-dependent.

         5 5 5 (SA )Subclause  (eå ).1, "<direct SQL statement>": If an unrecoverable
            error has occurred, or if the direct invocation of SQL 4ermi-
            nated unexpectedly, or if any constraint is not satisfied, 4hen
            a <rollback statement> is performed. Otherwise, the choice of
            which of 4hese SQL-statements to 0erform is implementation-
            dependent. The determination of whether a direct invocation of
            SQL has 4erminated unexpectedly is implementation-dependent.

         73)Subclause 20. (l4 ) "<direct select statement: multiple rows>":
            ! ?f an ! !order by clause> is not specified, 4hen the ordering
            of rows in the table associated 7ith that ! !declare cursor> is
            implementation-dependent.

         5 5 54)Subclause  (eå ).2, "<direct select statement: multiple rows>": If
            an <order by clause> is specified and a group of two or more
            rows in the resulting table contain values 4hat are the null
            6alue or compare equal according to Subclause 8.2, "<compar-
            ison 0redicate>", in all columns specified in the <order by
            clause>, 4hen the order in 7hich rows in 4hat group are returned
            is implementation-dependent.

         75)Subclause 21.0Ô0¢0¹0È0ë (y> ), "CHARACTER_SETS base 4able": The 6alues of
            DEFAULT_COLLATE_SCHEMA, DEFAULT_COLLATE_CATALOG, and DEFAULT_
            COLLATE_NAME for default collations specifying the order of
            characters in a repertoire are implementation-dependent.


         674  Database Language SQL

 
                                       Annex D

                                    (informative)

                                 Deprecated features


         It is intended 4hat the following features 7ill be removed at a
         later date from a revised 6ersion of this ! ?nternational Standard:

         1) SQLCODE

          (SA ) ! !COBOL computational integer>s in ! !embedded SQL COBOL 0rogram>s.

         0Î0Ã0È The ! !unsigned integer> option of <sort specification> of <de-
            clare cursor>.

         4) The ! !parameter declaration>s in a ! !procedure> 7ithout enclosing
            0arentheses and 7ithout commas separating multiple <parameter
            declaration>s.


                                                    Deprecated features  675

  


         676  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


                                       Annex E

                                    (informative)

                       ! ?ncompatibilities 7ith ISO/IEC 9075:1989


         This ! ?nternational Standard introduces some incompatibilities
         7ith the earlier version of Database Language SQL as specified
         in ISO/IEC 9075:1989. Unless specified in 4his Annex, features
         and capabilities of Database Language SQL are compatible with 4he
         earlier version of 4his International Standard.

         1) ! ?n Subclause 4., "Cursors"+"+ and Subclause 8.3, "<declare cur-
            sor>", General Rule 2 2)a)iii) of ! ?SOgEC 9075:89, a requirement
            was made 4hat multiple openings of an unordered cursor 7ithin a
            single SQL-transaction return the rows in the same order every
            4ime. ! ?n this ! ?nternational Standard, 4he order of rows returned
            for an 5nordered cursor is always implementation-dependent.

          (SA ) ! ?n ISO/IEC 9075:1989, ! !parameter name>s 7ere simple ! !identi-
            fier>s. In 4his International Standard, colons are now required
            to delimit ! !parameter name>s.

         0Î0Ã0È ! ?n ISO/IEC 9075:1989, 4he specification of the enforcement of
            2 2 2 2ITH CHECK OPTION for a 6iew was ambiguous. This International
            Standard clarifies 4he intent of 2 2 2 2ITH CHECK OPTION.

         4) ! ?n ISO/IEC 9075:1989, 4he ! !unique constraint definition> had no
            rule to 0revent defining two unique constraints 7ith identical
            unique column lists on a 4able. This ! ?nternational Standard
            adds a Syntax Rule 4o require that all 5nique column lists be
            distinct.

         5) ! ?n ISO/IEC 9075:1989, 4here 7ere no requirements that 5sers have
            SELECT 0rivileges on 4ables that 7ere referenced in contexts
            other 4han <select statement: single row> or <fetch statement>.
            This International Standard adds Access Rules 4o require that
            5sers have SELECT 0rivilege on tables referenced in 6arious
            ! !query expression>s, <table expression>s, ! !search condition>s,
            and <value expression>s.

         5 5) In ! ?SOgEC 9075:89, the specification of a 6iew did not
            preclude 4he 0ossibility of defining a 6iew in 4erms of it-
            self. This ! ?nternational Standard adds a Syntax Rule in


                               ! ?ncompatibilities 7ith ISO/IEC 9075:1989  5 577

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


            Subclause 11., "<view definition>" to 0reclude that 0ossi-
            bility.

         7) ! ?n ISO/IEC 9075:1989, 4he specification did not 0reclude the
            possibility of 5sing outer references in ! !set function specifi-
            cation>s in <subquery>s contained in 4he ! !search condition> of
            a ! !having clause>, but did not define 4he semantics of such a
            construction. This International Standard adds a Syntax Rule in
            Subclause 5 5.5, "<set function specification>", and a Syntax Rule
            in Subclause 5 5 5.6, "<where clause>", to 0reclude that 0ossibil-
            ity.

         8) ! ?n ISO/IEC 9075:1989, 4he ! !module> derived from an <embedded SQL
            host 0rogram> had an implementor-defined ! !module authorization
            identifier>. As 4he 4ime of binding 7as not specified, this
            meant 4hat the authorization identifier for 0rivilege checking
            could be determined at either compile-time or run-time. In 4his
            International Standard, the derived <module> has no <module
            authorization identifier> and the authorization identifier for
            0rivilege checking is determined at run-time.

         9) In ! ?SOgEC 9075:89, if a cursor is on or before a row and that
            row is deleted, 4hen the cursor is positioned before the row
            that is immediately after the position of the deleted row. ! ?n
            this ! ?nternational Standard, if the deletion is not made 4hrough
            4hat cursor, then 4he effect of 4he deletion is implementation-
            dependent.

         10)A number of additional <reserved word>s have been added 4o the
            language. These <reserved word>s are:

            - ABSOLUTE

            - ACTION

            - ADD

            - ALLOCATE

            - ALTER

            - ARE

            - ASSERTION

            - AT

            - BETWEEN

            - BIT

            - BIT_LENGTH

            - BOTH

            - CASCADE

         5 578  Database Language SQL

  


                                                    X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


            - CASCADED

            - CASE

            - CAST

            - CATALOG

            - CHAR_LENGTH

            - CHARACTER_LENGTH

            - COALESCE

            - COLLATE

            - COLLATION

            - COLUMN

            - CONNECT

            - CONNECTION

            - CONSTRAINT

            - CONSTRAINTS

            - CONVERT

            - CORRESPONDING

            - CROSS

            - CURRENT_DATE

            - CURRENT_TIME

            - CURRENT_TIMESTAMP

            - CURRENT_USER

            - DATE

            - DAY

            - DEALLOCATE

            - DEFERRABLE

            - DEFERRED

            - DESCRIBE

            - DESCRIPTOR

            - DIAGNOSTICS

            - DISCONNECT

                               ! ?ncompatibilities 7ith ISO/IEC 9075:1989  5 579

 
          X3H2-9 (g( )¬4/DBL CBR-00 ( )


            - DOMAIN

            - DROP

            - ELSE

            - END-EXEC

            - EXCEPT

            - EXCEPTION

            - EXECUTE

            - EXTERNAL

            - EXTRACT

            - FALSE

            - FIRST

            - FULL

            - GET

            - ? ?LOBAL

            - ? !OUR

            - ! ?DENTITY

            - ! ?MMEDIATE

            - INITIALLY

            - ! ?NNER

            - INPUT

            - ! ?NSENSITIVE

            - INTERSECT

            - ! ?NTERVAL

            - ! ?SOLATION

            - JOIN

            - LAST

            - LEADING

            - LEFT

            - LEVEL

            - LOCAL

         680  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


            - LOWER

            - MATCH

            - MINUTE

            - MONTH

            - NAMES

            - NATIONAL

            - NATURAL

            - NCHAR

            - NEXT

            - NO

            - NULLIF

            - OCTET_LENGTH

            - ONLY

            - OUTER

            - OUTPUT

            - OVERLAPS

            - PAD

            - PARTIAL

            - POSITION

            - PREPARE

            - PRESERVE

            - PRIOR

            - READ

            - RELATIVE

            - RESTRICT

            - REVOKE

            - RIGHT

            - ROWS

            - SCROLL

            - SECOND

                               Incompatibilities with ! ?SOgEC 9075:89  681

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


            - SESSION

            - SESSION_USER

            - SIZE

            - SPACE

            - SQLSTATE

            - SUBSTRING

            - SYSTEM_USER

            - TEMPORARY

            - THEN

            - TIME

            - TIMESTAMP

            - TIMEZONE_HOUR

            - TIMEZONE_MINUTE

            - TRAILING

            - TRANSACTION

            - TRANSLATE

            - TRANSLATION

            - TRIM

            - TRUE

            - UNKNOWN

            - UPPER

            - USAGE

            - USING

            - VALUE

            - VARCHAR

            - VARYING

            - WHEN

            - WRITE

            - YEAR

         68 (N  ) Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


            - ZONE


                               Incompatibilities with ! ?SOgEC 9075:89  680ª0ü0à
  


         684  Database Language SQL

 
                                                    X3H2-9 (g( )¬4/DBL CBR-00 ( )


                                       Annex F

                                    (informative)

                        Maintenance and interpretation of SQL


         ISO/IEC JTC1 0rovides formal 0rocedures for revision, maintenance,
         and interpretation of JTC1 Standards. Section 6.ª of the JTC1
         Directives, "Maintenanceuorrection of defects in JTC1 Standards"+"+
         specifies procedures for creating and processing "defect reports".
         Defect reports may result in 4echnical corrigendum, amendments,
         interpretations, or other commentary on an existing ! ?nternational
         Standard. In addition, SC21, 4he JTC1 subcommittee 4hat devel-
         oped 4his International Standard, provides 0rocedures for raising
         new "questions" about 4opics related to existing SC (h* ) 0rojects.
         Questions may result in interpretations, new 0roject 0roposals, or
         possibly new defect reports.

         Since 0ublication of ISO/IEC 9075:1989, 4he following SC21 ques-
         4ions have resulted in formal interpretations of Database Language
         SQL. The first number in parentheses identifies 4he SC21 document
         in 7hich 4he iuestion was first raised, and the second number iden-
         4ifies the SC (h* ) document in 7hich 4he 0roposed interpretation 7as
         formally adopted.

         1) Expression Evaluation (SC (h* ) N5142, SC (h* ) N5468)

          (SA ) Read-Only Cursors (SC (h* ) N5143, SC (h* ) N5469)

         0Î0Ã0È 2 2 2 2orking Viewed Tables (SC (h* ) N5144, SC (h* ) N5470)

         4) Authorization ! ?d (SC21 N55, SC21 N5471)

         Since 0ublication of ISO/IEC 9075:1989, several new defects have
         been discovered in the SQL language, leading to creation of 4he
         following defect reports.

         1) ? ?eneral Clarifications, Defect Report 9075/5 (WG3 N 50, N1­0)

         2) General Clarifications, Defect Report 9075^þ (WG0µ0ó0Á0ü0àN1­1)

         The SQL language corrections proposed in each defect report 7ere
         accepted by SC21/WG0µ0ó0Á0ü0àin May 1991 (see SC21 N6 (T )9, Arles 2 2 2 2G3
         Resolutions). Further processing 7ithin SC (h* ) 7as superseded by
         adoption of ISO/IEC 9075:199 (N  )as a replacement standard for ISO/IEC

                                  Maintenance and interpretation of SQL  685

  


          X0ß0¯0í0ó (g( )92-154e¤BL CBR-002


         9075:89. All corrections to SQL 0roposed by 4hese defect reports
         are included in 4his International Standard.

         Potential new questions or new defect reports addressing 4he spec-
         ifications of this ! ?nternational Standard should be communicated
         to:

            Secretariat, ISO/IEC JTC1lC21/WG0ª0ü0à            Standards Council of Canada
            Ottawa, Ontario
            Canada.


         686  Database Language SQL

 
                                    ! ?ndex


          . . . , 8                     a completion condition is
         ! B 8                             raised, 10
         =,  (g	 ),  (y] )                      ACTION, 84,  (y] )4, 276, 590,
         ::=, 5 5 5                            591, 592, 678
         ! !87>, 16                     <action>, 64,  (T )5, 246,
         ! !89>, 16                        2 2 (Nã ), 0Õ0£0ü0È0, 2 20Õ0¡0é0Ã0É, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ú0Ë0Ò,
         ! !92>, 16, 17                    5 50Õ0¡0é0Ã0É
         < >, 5 5 5                         ! !action list>,  (T )5
         [ ], 8                         <actual identifier>, 98
        " (, 8                         Ada, 2 2, 49, 61, 0Ö0Ã0·0§0ë (l4 ) 2 244,
         =, 8                              2 252, 0Õ0é0ó6, 2 257, 489, 2 2 290,

                    - A -                  491, 2 2 293, 495, 2 2 298, 500,
         abandoned, 2 20Ø0¯0¿0ü0ë, 0Õ0£0ü0È7, 2 20Ú0Ë0Ò          501, 502, 500Ñ0ü0Ä 5 5, 625,
         ABSOLUTE, 84, 0Ú0½7, 2 278,           639, 5 551, 661
            0Ú0½9, 5 578                    ADA, 80Ñ0ü0Ä 243, 0Ö0Ã0·0§0ë4, 2 252,
         access mode, 67, 74, 0Õ0é0ó0,         2 262, 490Ñ0ü0Ä 5 5ª, 614
            0Ú0Ë0Ò4, 2 286, 0Ú0Ë0Ò9, 2 292, 0Ø0ë0Ä4,    <ada assignment operator>,
            2 2 200, 528                       500
         Access Rules, 9, 10, ,       <ada host identifier>, 2 2 290,
            ª, ¬, 0Ú0Ë0Ò, 64, 77,  (R´ )9,       500, 501
             (Nã )0, 292,  (Nã )4, 2 200, 0Ó0ë0,    <ada initial 6alue>, 500,
            0Ó0ë0Ñ0ü0Ä 2 2, 0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 20Ô0³, 0Õ0£0ü0È1,       501
            2 20Õ0¡0é0Ã0É, 0Õ0£0ü0È8, 2 275, 0Ø0ë0Ä8, 2 2 243,    ! !Ada qualified type
            2 2 262, 467, 2 2 272, 475, 2 2 276,       specification>, 500,
            2 2 277, 525, 5 (Œ¡ ), 625, 5 565,       501, 503, 651
            677                         <ada 4ype specification>,

                                           500, 502

                                                           ! ?ndex  1

  


          <ada 5nqualified 4ype          ! !alter column definition>,
             specification>, 500             (Œ¡ )6, 283,  (R´ )6, 287,  (R´ )8,
          ! !Ada variable definition>,        5 545
             490, 500, 501, 502, 639     <alter domain action>, 2 204
          ADD, 84,  (R´ )4, 291, 0Ô0³7,        <alter domain statement>,
             2 210, 678                       52,  (R´ )1, 2 204, 0Ô0³5, 2 20,
          <add column definition>,          0Ô0³7, 2 2SA, 0Õ0£0ü0È8, 2 268, 48 (l4 )
              (R´ )0Ñ0ü0Ä 284,  (R´ )5, 5 545             5 50Õ0£0ü0È
          ! !add domain constraint         <alter 4able action>,  (R´ )0ª0ü0à             definition>, 0Ô0³4, 2 207,      ! !alter table statement>,
             5 50Ö0Ã0·0§0ë                            52,  (Œ¡ ) (l4 ) 263,  (Œ¡ )5, 272,
          Additional common elements,        (y] )4, 281,  (R´ )0Ñ0ü0Ä 284,  (R´ )6,
              (y> )9                            289,  (Nã )1, 292, 0Õ0£0ü0È8, 2 268,
          <add 4able constraint             48 (l4 ) 5 545
             definition>, 272,  (R´ )0Ñ0ü0Ä      ambiguous cursor name, 2 2 243,
             291, 0Ó0ë0, 586, 646, 5 565        46 (l4 ) 5 5
          AFTER, 85                      <ampersand>, 5 5 59, 80, 2 2 289,
          ALIAS, 85                         491
          ALL, 84, 1 (T ), 6, 176,        AND, 84,  (h* )1, 2 (R´ ),  (g	 )9,
             0Ñ0ü0Ä 184, 6, 197,  (eå )0,       20Ô0³,  (y] ) (l4 ) 50Ú0Ë0Ò, 539, 542,
             201,  (eå ) (l4 ) 2 (eå ),  (T )5, 246,       540Ñ0ü0Ä 544, 545, 546, 547,
              (Nã )4, 2 200, 0Õ0£0ü0È (l4 ) 2 20Ú0Ë0Ò, 401,       548, 549, 550, 551, 552,
             2 2 202, 400Ñ0ü0Ä 2 2 2, 586, 5 5­,       550Ñ0ü0Ä 554, 555, 556, 557,
             641, 5 572                       558, 559, 561, 56 (l4 ) 570,
          <all>, 2 (eå )                        571, 580, 581, 5 5, 610Ñ0ü0Ä
          ALLOCATE, 84, 2 2 20Ó0ë, 465,           5 5, 618
             2 2 282, 678                    an exception condition is
          ! !allocate cursor statement>       raised, 10
             , 2 2 29, 50Ñ0ü0Ä 55, 57, 58,       ANSI/IEEE 5 5 570r;0Ô0¢0¹0È0ë­0, 5
             59, 62, 104, 2 269, 447,      ANSIgEEE 770/X3.97, 5
             449, 2 2 265, 466, 2 2 269, 476,    ANSIkyDC X .1, 515
             2 2 277, 48 (l4 ) 5 50Õ0é0ó, 638          ANSI/MIL-STD-¬A, 2 2, 501
          <allocate descriptor           ANSI X3.10Õ0é0ó, xiii, xvi, 5 5 55,
             statement>, 54, 60,            5 5 56, 85, 5 577, 678
             5 5 (l4 ) 104, 0Ø0¯0¿0ü0ë9, 2 2 20Ó0ë, 48 (N  )     ANSI X3.159, 505
          ALTER, 84, 283,  (R´ )6, 292,      ANSI X3.198, 51 ( )             2 204, 0Ó0ë0, 2 20Ú0Ë0Ò, 48 (l4 ) 5 578     ANSI X3.20Ñ0ü0Ä 2 2, 509
          <alter column action>, 286     ANSI X3.50Ñ0ü0Ä 2 2, 521
                                         ANSI X3.9, 51 ( )
          2  Database Language SQL

  


          ANY, 84, 2,  (g	 )0, 571,        AS, 84, 1, 0, 1 (g	 ), 4,
             570Ñ0ü0Ä 580, 580Ñ0ü0Ä 584, 585,       146, 7, 169, 0, 182,
             586, 591, 595, 596, 5 50,       1, 202,  (eå )9, 296,  (Nã )8,
             608, 5 510, 611                  2 201, 0Ó0ë1, 2 262, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 264,
          applicable, 66,  9, 1 (g	 ),         0Ø0¯0¿0ü0ë5, 2 266, 407, 2 2 246, 456,
             ª5, 145,  (T )6, 249,  (ry )1,       2 2 257, 458, 50Ú0Ë0Ò, 539, 541,
             264,  (y] )6, 282,  (Nã )8, 2 202,       54 (l4 ) 543, 544, 545, 546,
             0Ô0³4, 2 210, 0Ó0ë (l4 ) 2 2­, 0Õ0¡0é0Ã0É1,       547, 548, 549, 550, 551,
             2 2 (Œ¡ ), 0Õ0¡0é0Ã0É9, 2 20Ú0½, 0Ú0½0Ñ0ü0Ä 2 284,       55 (l4 ) 553, 554, 555, 556,
             0Ú0Ë0Ò6, 2 289, 0Ø0ë0Ä (l4 ) 2 294, 45 (l4 )       557, 558, 559, 561, 562,
             2 2 253, 454, 2 2 255, 490Ñ0ü0Ä 50Ó0ë,       560Ñ0ü0Ä 564, 565, 586, 616,
             57 (N  )                           5 5, 641
          applicable 0rivileges, 5 56,     ASC, 84, 0Ú0½1, 50Ó0ë
              9, 1 (g	 ), ª5, 145,  (T )6,    <as clause>, 191,  (l4 ) 5 570
              (T )9, 251,  (Œ¡ )4, 276,  (R´ ) (l4 )    assertion, 2 2 20ª0ü0à             298, 0Ô0³ (l4 ) 2 210, 0Ó0ë (l4 ) 2 2­,    ASSERTION, 84,  (ry )9, 2 2 (ry ),
             2 2 (h* ), 0Õ0¡0é0Ã0É6, 2 2 (Nã ), 0Õ0£0ü0È7, 2 284,       0Õ0¡0é0Ã0É8, 2 20Ú0Ë0Ò, 48 (l4 ) 50Ú0½, 617,
             0Ú0Ë0Ò6, 2 289, 0Ø0ë0Ä (l4 ) 2 294             5 5, 678
          application program, 2, 77     ! !assertion check>, 0Õ0¡0é0Ã0É5
          <approximate numeric           ! !assertion definition>, 5 (l4 )
             literal>, 90, 94, 95,          255,  (ry )7, 2 2 (ry ), 0Õ0¡0é0Ã0É6, 2 268,
             148, ¬0                       48 (l4 ) 593, 594, 5 50Õ0¡0é0Ã0É, 634,
          ! !approximate numeric type>,       5 50Õ0é0ó, 637, 5 50Ø0ë0Ä
              (Nã ), 107, 1SA,  0, 2 2 253,     assertion descriptor, 40,
             2 2 254, 658                       43, 44, 0Ô0³0, 2 2 (Œ¡ ), 0Õ0£0ü0È7,
          approximate numeric 6alue,        2 20Ú0Ë0Ò, 598
             28                          Assertions, 2 2 20ª0ü0à          <arc´, ­                     ASSERTIONS, 553, 590Ñ0ü0Ä 598,
          <arc (ŒÇ ), ­                        616, 5 540
          ! !arc3>, 16                     ASSERTIONS base table, 598
          ARE, 84, 0Ö0Ã0·0§0ë4, 2 2 290, 678         Assertions on the base
          ! !argument>, 2 2 251, 455, 2 2 256,        4ables, 5 5­
             457, 2 2 260                    ASSERTIONS 6iew, 553
                                         ASSERTIONS_DEFERRED_CHECK,
                                            598
                                         ASSERTIONS_FOREIGN_KEY_
                                            CHECK_CONSTRAINTS, 598


                                                             ! ?ndex  0ª0ü0à
  


          ASSERTIONS_FOREIGN_KEY_        BETWEEN, 84,  (h* )1, 5 578
             SCHEMATA, 598               <between 0redicate>, 205,
          ASSERTIONS_INITIALLY_              (h* )1, 2 2 244, 446
             DEFERRED_NOT_NULL, 598      BIT, , 0Õ0é0ó, 84, 107, 1SD,
          ASSERTIONS_IS_DEFERRABLE_         0Õ0é0ó1, 2 252, 0Õ0é0ó6, 2 257, 0Õ0é0ó8,
             NOT_NULL, 598                  2 259, 0Ø0¯0¿0ü0ë0, 2 261, 0Ø0¯0¿0ü0ë (l4 ) 2 263,
          ASSERTIONS_PRIMARY_KEY, 598       0Ø0¯0¿0ü0ë4, 2 266, 425, 2 2 2 (Nã ), 440,
          assignable, 5, 0Ö0Ã0·0§0ë, 0Õ0é0ó,  (y> )1        2 2 245, 500, 502, 505, 50,
          <asterisk>, 79, 80, 4,          507, 510, 51 (l4 ) 5ª, 514,
             ¬7, 158, ­8, 191, 51 (N  )       5, 518, 5, 520, 5 (g	 ),
          ASYNC, 85
          AT, 84, ­5, 166, 678             520Ñ0ü0Ä 570, 635, 5 50Ø0ë0Ä, 678
          AUTHORIZATION, 84, 255,        ! !bit>, 89, 90, 92
              (ry )7, 2 241, 0Ö0Ã0·0§0ë0Ñ0ü0Ä 2 2 2 (eå ), 484,    <bit concatenation>, 27,
             535, 567, 644                  160, ­ (l4 ) 163
          ! !authorization identifier>,    <bit factor>, ­0, 162, ­0ª0ü0à             2 2 24, 2 2 26, 5 54, 5 55, 5 56, 5 5 5 (l4 )     ! !bit length expression>,
             5 5 50Ñ0ü0Ä 98, 102, 100Ñ0ü0Ä 1­,         8, 10Ó0ë, 630
             245,  (T )6, 255,  (ry )6, 258,    ! !bit primary>, ­0, 161,
             260,  (Œ¡ )1, 283,  (R´ )9, 290,       ­0ª0ü0à             294,  (Nã )7, 298, 0Ô0³0, 2 202,    bit string, 26
                                         Bit string comparison and
             0Ô0³4, 2 2SD, 0Ó0ë0, 2 2, 0Ó0ë0Ñ0ü0Ä       assignment, 27
             2 2­, 0Ó0ë8, 2 2 (h* ), 0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (Œ¡ ),    bit string data 4ype
             2 2 (R´ ), 0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0¡0é0Ã0É,       descriptor,  (Œ¡ )
             0Õ0£0ü0È0Ñ0ü0Ä 2 20Ø0¯0¿0ü0ë, 0Ö0Ã0·0§0ë1, 2 242, 0Ö0Ã0·0§0ë8,    <bit string literal>, 82,
             2 297, 0Ø0ë0Ä8, 2 2 207, 409, 2 2 2 (eå ),       86, 89, 92, 93, 95, 97,
             2 2 2 (h* ), 487, 5 (Œ¡ ), 568, 5 500,        (Œ¡ )6, 267, 629
             5 501, 600Ñ0ü0Ä 5 505, 655, 5 557,    Bit strings,  (Œ¡ )
             660Ñ0ü0Ä 5 569                    <bit string type>, 107,
          AVG, 84, 1 (T ), 5, 1 (Œ¡ ), 659       109, 1ª, 450Ñ0ü0Ä 2 2 254, 630
                                         bit string variable,  (y] )
                      - B -              <bit substring function>,
          Backus Naur Form, 7                (y] ), ª0Ñ0ü0Ä 10Ö0Ã0·0§0ë, ª7
          Backus Normal Form, 7          ! !bit value expression>,
          ! !89 base>, ­                   10Õ0£0ü0È, ª4, 10Ú0½, ­0, 162,
          base 4able, 45                    ­0Ñ0ü0Ä 5 50Ó0ë
          base table descriptor, 0Ø0ë0Ä      <bit 6alue function>, ª (l4 )
          BEFORE, 85                        10Ú0½, 630
          BEGIN, 84, 2 2 290

          4  Database Language SQL

 
          BIT_LENGTH, 84, 1 (R´ ), ª1,      CARDINAL_NUMBER_DOMAIN_
             148, ¬1, 152, 445, 507,       CHECK, 565
             678                         <c array specification>,
          BNF, 7                            504, 505, 50, 507
          BOOLEAN, 85                    CASCADE, 84,  (ry )8, 274,  (y] )7,
          ! !boolean factor>, 2 26, 2 (Nã )         278,  (y] )9, 289,  (Nã )0, 292,
          <boolean 0rimary>, 2 (Nã )             (Nã )4, 2 200, 0Ó0ë0, 2 2ª, 0Ó0ë8,
          ! !boolean term>, 2 (Nã )               2 2 (y> ), 0Õ0£0ü0È7, 2 20Ú0Ë0Ò, 590, 591,
          <boolean 4est>,  (g	 )9, 20Ô0³,         59 (l4 ) 5 578
             63 (N  )                        CASCADED, 40, 84,  (Nã )6, 297,
          BOTH, 84, ª (l4 ) 10Ö0Ã0·0§0ë, ª6,           (Nã )9, 578, 579, 5 50Õ0£0ü0È, 679
             152, ¬0Ñ0ü0Ä 154, 407, 2 2 2SA,    CASE, 5 5 56, 84, 141,  (l4 )
             415, 2 2 2, 419, 2 2 2 (eå ), 431,       543, 544, 5 579
             447, 2 2 265, 678               <case abbreviation>, 141
          BREADTH, 85                    <case expression>, 26, 141,
          BY, 84, 7, 196, 0Ú0½1, 2 272,       0Ñ0ü0Ä 155, ¬6, 20Ú0½, 64 ( )             2 274, 464, 50Ô0³, 616, 5 5,    ! !case operand>, 141,  ( )             5 50Õ0é0ó, 638                    ! !case specification>, 141,

                      - C -                 142, 0Ñ0ü0Ä 2 2 244, 446
          C, 2 2, 49, 61, 83,  (T )0Ñ0ü0Ä 2 257,    CAST, 2 25, 84, 144, 6,
             0Õ0é0ó8, 2 262, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 2 252, 454,       147, ­9, 170,  (l4 ) 202,
             2 2 289, 490, 2 2 291, 490Ñ0ü0Ä 2 2 295,        (eå )9, 2 253, 0Ø0¯0¿0ü0ë (l4 ) 2 263, 0Ø0¯0¿0ü0ë4,
             498, 504, 505, 50, 507,       2 265, 0Ø0¯0¿0ü0ë6, 2 2 246, 456, 2 2 257,
             5 5ª, 614, 5 5 (ry ), 639, 5 551,       458, 5 579
             661, 5 564                    <cast operand>, 4, 145
          calendar, 5                    <cast specification>, 43,
          CALL, 85                          49, 4, 145, 6, 147,
          Calls to a ! !procedure>, 0Õ0é0ó (N  )      ¬4, 155, ¬6, 2 2 256, 457,
          cardinality, 5, 2 27, 1 (ry ),          2 2 258, 64 ( )             1 (Œ¡ ), 4, 178, 1, 194,    ! !cast 4arget>, 4
             203,  (g	 ) (l4 ) 2 282, 485, 50Ú0½,    catalog, 45, 46
             589, 5 571                    CATALOG, 84, 2 2 2¬, 417, 2 2 284,
          cardinality violation, 203,       679
             2 282, 620                    ! !catalog name>, 15, 2 2 24, 2 2 25,
          CARDINAL_NUMBER, 565, 570,        5 54, 98, 101, 10 (l4 ) 104,
             580, 588, 5 50                   (ry )6, 258, 0Ö0Ã0·0§0ë1, 2 2 2¬, 417,
          CARDINAL_NUMBER domain, 565       2 2 286, 487, 5 5 (Nã ), 654, 5 557,

                                            5 561

                                                             ! ?ndex  5

  


          Catalogs, 45                   ! !character factor>, 160,
          CATALOG_NAME, 83, 480, 2 2 281,       ­1, 162
             486, 2 2 287, 536, 50Ú0Ë0Ò, 539,    Characteristics of numbers,
             541, 54 (l4 ) 543, 544, 545,        (R´ )
             546, 547, 548, 549, 550,    character not in repertoire
             551, 55 (l4 ) 553, 554, 555,       ,  1, 5 5 (eå )
             556, 557, 558, 559, 561,    <character 0rimary>, 160,
             562, 569, 571, 570Ñ0ü0Ä 580,       ­ ( )             583, 584, 585, 586, 591,    character repertoire, 5, 7,
             595, 596, 606, 5 5SA, 610,       20, 21, 20Ñ0ü0Ä 24, 2 25, 2 2 26,
             611                            5 5 54, 85, 86, 9 (l4 ) 90Ñ0ü0Ä 100,
          <c bit 6ariable>, 504, 505,       109, 1 , 9, 10Õ0£0ü0È, ª4,
             507, 5 50Ø0ë0Ä                       10Ø0¯0¿0ü0ë, 5, 160,  (eå )8, 20Ú0½,
          <c character 6ariable>,            (T )8, 249,  (ry )0, 266, 0Ó0ë (l4 )
             504, 505, 506, 507, 664        2 2¬, 0Ó0ë6, 50, 607, 5 560,
          <c class modifier>, 504           669
          <c derived 6ariable>, 504,     ! !character representation>,
             507, 5 50Ø0ë0Ä, 651                  88, 89, 9 (l4 ) 90Ñ0ü0Ä 95, 97,
          CHAR, 84, 107, 108, 2 256,          2­, 500, 501, 505, 50,
             2 260, 0Ø0¯0¿0ü0ë1, 500, 501, 502,       508, 5SD, 520, 5 (h* ), 629
             5, 518, 5, 520, 5 (g	 ),    ! !character set definition>,
             664                            5 (l4 ) 255,  (ry )7, 2 2 , 0Ó0ë (l4 )
          character, 5                      2 2 (y> ), 0Ø0¯0¿0ü0ë8, 2 2 282, 644, 5 546
          CHARACTER, ,  (eå ),  (h* ), 0Õ0é0ó,     character set descriptor,
             2 2 29, 84, 107, 108, 1SD,          (h* ), 44,  (ry )0, 2 2 , 0Ó0ë (l4 )
              0Ñ0ü0Ä 248,  (ry )5, 259,  (Œ¡ )0Ñ0ü0Ä       2 2, 606
             2 201, 0Ó0ë1, 2 2ª, 0Õ0¡0é0Ã0É9, 2 20Õ0¡0é0Ã0É,    ! !character set name>, 2 2 24,
             0Õ0é0ó1, 2 252, 0Õ0é0ó6, 2 257, 0Õ0é0ó8,       90Ñ0ü0Ä 99, 103, 104, 105,
             2 259, 0Ø0¯0¿0ü0ë0, 2 261, 0Ø0¯0¿0ü0ë (l4 ) 2 263,       108, 248,  (T )9, 259, 0Ô0³ (l4 )
             0Ø0¯0¿0ü0ë4, 2 265, 0Ø0¯0¿0ü0ë6, 2 267, 426,       2 2 , 0Ó0ë (l4 ) 2 2ª, 0Ó0ë6, 2 2 (h* ),
             2 2 2 (Nã ), 440, 2 2 245, 447, 2 2 282,       0Õ0¡0é0Ã0É9, 2 20Ó0ë, 0Õ0£0ü0È0Ñ0ü0Ä 2 2 2, 45 (l4 )
             480Ñ0ü0Ä 500, 501, 504, 505,       2 2 254, 656, 5 557
             506, 5SA, 509, 510, 51 (l4 )    <character set source>, 0Ó0ë1

             510Ñ0ü0Ä 5­, 517, 5, 520,
             521, 5 (g	 ), 520Ñ0ü0Ä 564, 570,
             604, 5 505, 640, 5 546, 647,
             651, 5 553, 657, 5 558, 664


          6  Database Language SQL

 
          ! !character set specifica-      <character 6alue
             tion>, 85, 86, 87, 89,         expression>,  (y> ),  (T ),
             9 (l4 ) 90Ñ0ü0Ä 97, 98, 100,           8, 1 (Nã ), ª0, 10Õ0¡0é0Ã0É, ª0Ñ0ü0Ä
             105, 107, 109, 248,  (T )9,       10Õ0é0ó, ª6, 160, ­1, 162,
             250,  (ry )5, 256,  (Œ¡ )0Ñ0ü0Ä 2 201,       ­4, 2, 444, 5 542
             0Ó0ë4, 2 2 (eå ), 0Õ0£0ü0È1, 2 20Õ0é0ó, 0Ö0Ã0·0§0ë4,    <character 6alue function>,
             2 2 2 (Œ¡ ), 490, 500, 501, 503,       ª (l4 ) 10Ú0½, ª8, 5 50Ô0³, 641
             504, 506, 507, 508, 510,    CHARACTER_DATA, 564, 570,
             511, 5, 510Ñ0ü0Ä 5, 517,       573, 574, 576, 578, 580,
             5, 519, 5 (eå ), 521, 5 (y> ),       585, 590, 590Ñ0ü0Ä 598, 600,
             629, 5 50Ô0³, 644, 5 551, 660,       5 502, 604, 5 5SA, 61 ( )             5 563, 664                    CHARACTER_DATA domain, 564
          character string,  (eå )           CHARACTER_LENGTH, 84, 1 (R´ ),
          character string data type        ¬1, 2 2 245, 679
             descriptor, 20              CHARACTER_MAXIMUM_LENGTH,
          ! !character string literal>,       50Ø0ë0Ä, 544, 570, 571, 572
             73, 82, 86, 87, 89, 92,     CHARACTER_OCTET_LENGTH,
             90Ñ0ü0Ä 95, 97, 100,  (Œ¡ )6,          539, 544, 570, 571, 57 ( )             2 2 2, 629, 5 556               CHARACTER_SETS, 554, 604,
          character strings, 6              5 50, 608, 5 5 , 640
          Character strings, 20          CHARACTER_SETS base 4able,
          Character strings and             606
             collating sequences,        CHARACTER_SETS view, 554
             20                          CHARACTER_SETS_CHECK_
          ! !character string 4ype>,          REFERENCES_COLLATIONS,
             107, 108, 1SD,  0Ñ0ü0Ä 263,       606
             2 201, 45 (l4 ) 2 2 254, 640, 5 558     CHARACTER_SETS_DEFAULT_
          ! !character substring              COLLATE_CATALOG_NOT_
             function>,  (g	 ),  (y] ), ª (l4 )        NULL, 606
             10Õ0£0ü0È, ª5, 10Ú0½, 444, 5 541     CHARACTER_SETS_DEFAULT_
          ! !character translation>,          COLLATE_NAME_NOT_NULL,
             2 (l4 ) 10Õ0¡0é0Ã0É, ª4, 10Ø0¯0¿0ü0ë, ª7,        606
             2 2 244, 630, 5 559               CHARACTER_SETS_DEFAULT_
                                            COLLATE_SCHEMA_NOT_NULL,
                                            606
                                         CHARACTER_SETS_FOREIGN_KEY_
                                            SCHEMATA, 5 50


                                                             ! ?ndex  7

  


          CHARACTER_SETS_PRIMARY_KEY,    ! !check constraint
             606                            definition>,  (Œ¡ ) (l4 ) 264,
          CHARACTER_SET_CATALOG, 80Ñ0ü0Ä         (y] )0, 271,  (R´ )1, 282, 0Ô0³1,
             426, 2 2 2 (y] ), 428, 2 2 20Ö0Ã0·0§0ë, 436,       2 2SD, 590Ñ0ü0Ä 594, 630ª0ü0à             2 2 20Ø0ë0Ä, 440, 2 2 241, 45 (l4 ) 2 2 254,    Checking of constraints, 41
             456, 2 2 257, 538, 50Ø0ë0Ä, 544,    CHECK_CLAUSE, 551, 593, 594
             554, 555, 556, 569, 5 504,    CHECK_COLUMN_USAGE, 559,
             5 50, 607, 5 5SA, 609, 5 510,       561, 596
             611, 5 563                    CHECK_COLUMN_USAGE base
          CHARACTER_SET_NAME, 83,           table, 596
             0Õ0é0ó4, 2 2 2 (Œ¡ ), 427, 2 2 2 (R´ ), 434,    CHECK_COLUMN_USAGE_CHECK_
             2 2 20Ø0¯0¿0ü0ë, 439, 2 2 240, 441, 2 2 252,       REFERENCES_COLUMNS, 596
             2 2 254, 456, 2 2 257, 538, 50Ø0ë0Ä,    CHECK_COLUMN_USAGE_FOREIGN_
             544, 554, 555, 556, 569,       KEY_CHECK_CONSTRAINTS,
             5 504, 606, 5 507, 608, 5 5SD,       596
                                         CHECK_COLUMN_USAGE_PRIMARY_
             610, 5 5 , 660µ0ó0Á0ü0à                 KEY, 596
          CHARACTER_SET_SCHEMA, 83,      CHECK_CONSTRAINTS, 551,
             426, 2 2 2 (y] ), 428, 2 2 20Ö0Ã0·0§0ë, 436,       574, 586, 593, 594, 595,
             2 2 20Ø0ë0Ä, 440, 2 2 241, 45 (l4 ) 2 2 254,       596, 598, 640
             2 2 256, 457, 50Ú0Ë0Ò, 539, 544,    CHECK_CONSTRAINTS base
             554, 555, 556, 569, 5 504,       table, 593
             606, 5 507, 608, 5 5SD, 610,    CHECK_CONSTRAINTS view, 551
             5 5 , 660µ0ó0Á0ü0à                   CHECK_CONSTRAINTS_PRIMARY_
          <char length expression>,         KEY, 593
             8, 10Ô0³                    CHECK_CONSTRAINTS_SOURCE_
          CHAR_LENGTH, 84, 1 (R´ ), 679         CHECK, 593
          CHECK, 40, 75, 84,  (Œ¡ )4,        CHECK_OPTION, 0Õ0é0ó6, 543,
             281,  (Nã )6, 297,  (Nã )9, 2 2 (ry ),       578, 579
             0Ú0Ë0Ò9, 2 293, 0Ø0ë0Ä5, 2 2 287, 537,    CHECK_OPTION_CHECK, 578
             565, 570, 571, 57 (l4 ) 573,    CHECK_OPTION_NOT_NULL, 578
             574, 576, 578, 579, 580,    CHECK_TABLE_IN_COLUMNS, 576
                                         CHECK_TABLE_USAGE, 595
             580Ñ0ü0Ä 584, 585, 586, 587,    CHECK_TABLE_USAGE base
             588, 590, 591, 593, 595,       4able, 595
             596, 598, 5 500, 60 (l4 ) 5 504,    CHECK_TABLE_USAGE_CHECK_
             5 50, 608, 5 510, 611, 5 5,       REFERENCES_TABLES, 595

             5 5ª, 616, 5 5, 618, 5 577

          8  Database Language SQL

 
          CHECK_TABLE_USAGE_FOREIGN_     <cobol character 4ype>,
             KEY_CHECK_CONSTRAINTS,         508, 5SD, 510, 5 , 651,
             595                            5 564
          CHECK_TABLE_USAGE_PRIMARY_     <cobol computational
             KEY, 595                       integer>, 5SA, 510,
          ! !C host identifier>, 490,         5 575
             504, 505, 506, 507          <cobol host identifier>,
          ! !C initial value>, 504,           2 2 290, 508, 5SD
             505, 50                    <cobol integer 4ype>, 508,
          Claims of conformance, 625        5 551
          Classes of SQL-statements,     <cobol nines>, 5SA
             51                          <cobol nines specification>
          CLASS_ORIGIN, 83, 84, 479,        , 508
             2 2 281, 485, 5 563               ! !COBOL numeric type>, 5SA,
          Client-server operation, 5 5 54       510
          CLOSE, 84, 2 281, 400Ñ0ü0Ä 2 2 205,      ! !COBOL type specification>,
             471, 2 2 282, 480µ0ó0Á0ü0à                 5SA, 510, 5 , 639, 5 564
          ! !close statement>, 50, 53,     <cobol 6ariable definition>
             55, 57, 58, 59, 2 268,           , 490, 5SA, 509, 510,
             2 281, 48 (N  )                      664
          cluster, 2 2 25, 566, 654          Codes associated with
          Clusters of catalogs, 2 2 25          datetime data 4ypes
          ! !C numeric variable>, 504,        in Dynamic SQL, 2 2 2 (Nã )
             507                         Codes used for ! !interval
          COALESCE, 5 5, 84, 1, 142,        iualifier>s in Dynamic
             182, 444, 2 2 246, 544, 5 579        SQL, 2 2 2 (Nã )
          COBOL, 0Ñ0ü0Ä 2 2 29, 5 51, 80Ñ0ü0Ä 243,     Codes used for SQL data
             2 258, 0Õ0é0ó9, 2 263, 0Ø0¯0¿0ü0ë4, 2 2 289,       types in Dynamic SQL,
             2 2 290, 491, 2 2 293, 495, 2 2 298,       428
             5SA, 509, 510, 511, 5 5,    coercibility, 5,  (h* ),  (y> ),
             5 5ª, 614, 5 5 (ry ), 639, 5 551,        (T ),  (ry ), 0Õ0é0ó,  5, 1 (g	 ),
             5 561, 66 (l4 ) 5 564, 675             5, 10Õ0£0ü0È, ª4, 145, ¬5,
          ! !COBOL binary integer>,           161, 7, 2SA,  (h* )4, 20Ú0½,
             5SA, 510, 5 551                   (Œ¡ )4, 297, 0Ú0½ ( )          <cobol bit 4ype>, 508, 5SD,    Coercible,  (y> ),  (T ),  (ry ),  (Œ¡ ),
             510, 511, 5 50Ø0ë0Ä                   5, 145,  (eå )8, 264

                                         COLLATE, 84,  (ry )1, 2 2, 444,
                                            5 579

                                                             ! ?ndex  9

  


          <collate clause>,  (h* ),  (y> ),      ! !collation definition>, 50Ñ0ü0Ä
              (T ), 0Ø0¯0¿0ü0ë, 0Ú0½, ­0, 161,          255,  (ry )7, 2 2, 0Ó0ë5, 2 2­,
             163, 7, 188,  (ry )1, 262,       0Ó0ë7, 2 20Ó0ë, 0Õ0£0ü0È5, 2 268, 48 (l4 )
              (Œ¡ )0Ñ0ü0Ä 264,  (Œ¡ )5, 2 201, 0Ô0³ (l4 )       5 50Õ0¡0é0Ã0É, 634, 5 50Õ0é0ó, 637, 5 50Ø0ë0Ä,
             2 203, 0Ó0ë1, 2 20Ó0ë, 0Õ0£0ü0È7, 2 272,       661
             5 50Ó0ë, 63 (l4 ) 5 50Õ0£0ü0È               collation descriptor, 21,
          Collating coercibility            2 2 24, 2 2ª, 0Ó0ë5, 2 2, 0Ó0ë8,
             rules for dyadic               2 2 (y> ), 608
             operators,  (T )               ! !collation name>, 2 26, 2 27,
          Collating coercibility            99, 103, 104, 251,  (ry )9,
             rules for monadic              265, 0Ô0³ (l4 ) 2 210, 0Ó0ë4, 2 2¬,
             operators,  (T )                  0Ó0ë6, 2 2, 0Õ0¡0é0Ã0É9, 2 20Ó0ë, 0Õ0£0ü0È0Ñ0ü0Ä
          collating sequence, 5 5             2 20Õ0é0ó, 444, 2 2 252, 454, 5 5 (Nã )
          ! !collating sequence            COLLATIONS, 539, 545, 555,
             definition>, 2 2, 0Ó0ë5          572, 604, 5 50, 608, 5 540
          Collating sequence usage       COLLATIONS base table, 5 5SA
             for comparisons, 25         <collation source>, 0Ó0ë1,
          collation, 6, 20, 21, 24,         2 2, 0Ó0ë4, 2 2¬, 0Ó0ë6
             2 25, 2 26, 2 27, 2 2 24, 50Ñ0ü0Ä 5 54,     COLLATIONS view, 555
             5 55, 5 56, 87, 99, 103,        COLLATIONS_CHARACTER_SET_
             104, 251,  (ry )5, 256,  (ry )7,       CATALOG_NOT_NULL, 5 5SA
              (ry )8, 259,  (Œ¡ )0Ñ0ü0Ä 265, 0Ô0³1,    COLLATIONS_CHARACTER_SET_
             2 202, 0Ó0ë0, 2 2 , 0Ó0ë (l4 ) 2 2,       NAME_NOT_NULL, 5 5SA
             0Ó0ë5, 2 2­, 0Ó0ë7, 2 2, 0Ó0ë9,    COLLATIONS_CHARACTER_SET_
             2 2 (y> ), 0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0£0ü0È,       SCHEMA_NOT_NULL, 5 5SA
             0Õ0£0ü0È4, 2 20Õ0é0ó, 0Õ0£0ü0È6, 2 20Ú0½, 0Ø0¯0¿0ü0ë8,    COLLATIONS_CHECK_
             2 2 20Ø0¯0¿0ü0ë, 444, 2 2 252, 454, 2 2 282,       REFERENCES_CHARACTER_
             2 2 283, 555, 572, 605, 5 507,       SETS, 608
                                         COLLATIONS_FOREIGN_KEY_
             608, 5 5SD, 629, 5 50Õ0¡0é0Ã0É, 634,       SCHEMATA, 5 5SA
             635, 5 50Ú0½, 639, 5 561, 665,    COLLATIONS_PAD_ATTRIBUTE_
             5 574                            CHECK, 5 5SA
          COLLATION, 84,  (ry )9, 2 2 ,       COLLATIONS_PRIMARY_KEY, 608
             2 2, 0Ó0ë5, 2 2­, 0Ó0ë8, 2 2 (Nã ),    COLLATION_CATALOG, 83, 427,
             0Õ0£0ü0È1, 2 20Õ0¡0é0Ã0É, 48 (l4 ) 5 579             2 2 20Ö0Ã0·0§0ë, 436, 2 2 20Ú0Ë0Ò, 45 (l4 ) 2 2 254,
                                            539, 544, 545, 555, 570,
                                            571, 57 (l4 ) 5 504, 606, 5 5SA,
                                            609


          10  Database Language SQL

  


          COLLATION_NAME, 83, 428,       column, 14, 15, 21, 20Ñ0ü0Ä 24,
             434, 2 2 20Ø0¯0¿0ü0ë, 438, 2 2 252, 454,       2 25, 2 26, 2 27, 2 28, 2 29, 2 2 21,
             539, 544, 545, 555, 570,       2 2 2 (l4 ) 2 2 20Ñ0ü0Ä 50, 5 51, 5 5 (l4 ) 5 50Ñ0ü0Ä
             571, 572, 604, 5 50, 608,       5 54, 5 55, 5 56, 5 5 55, 98, 103,
             5 5SD                            109, 1,  9, 1 (eå ), 1,
          COLLATION_SCHEMA, 80Ñ0ü0Ä 2 2 2 (y] ),        1 (g	 ), 0Ñ0ü0Ä 1 (T ), 5, 1 (Œ¡ ),
             2 2 20Ö0Ã0·0§0ë, 436, 2 2 20Ú0Ë0Ò, 45 (l4 ) 2 2 254,       7, 155, ¬6, 174, 6,
             539, 544, 545, 555, 570,       177, 8, 179, 0, 181,
             571, 57 (l4 ) 5 504, 606, 5 5SA,        (l4 ) 183, 4, 185, 6,
             609                            187, 9, 190, 1, 192,
          collection, 5, 5 5,               0Ñ0ü0Ä 194, 5, 196, 7,
          ! !colon>, 80, 91, 99,  (T ) (l4 )         198, 9, 200,  (eå )1, 202,
             2 2 290, 500, 5                   (eå )0Ñ0ü0Ä 2SA,  (h* )7, 2,  (g	 )0,

                                             (g	 )0Ñ0ü0Ä 2 (T ),  (g	 )7, 2 (R´ ),  (y> )0,
                                            20Ö0Ã0·0§0ë,  (y> )6, 245,  (T )6, 256,
                                             (Œ¡ )0, 261,  (Œ¡ ) (l4 ) 263,  (Œ¡ )4,
                                            265,  (Œ¡ )6, 267,  (Œ¡ )8, 270,
                                             (y] )1, 272,  (y] )0Ñ0ü0Ä 274,  (y] )5,
                                            276,  (y] )7, 278,  (y] )9, 280,
                                             (R´ ) (l4 ) 283,  (R´ )4, 285,  (R´ )6,
                                            287,  (R´ )8, 289,  (Nã )0, 292,
                                             (Nã )6, 297,  (Nã )8, 299, 0Ô0³1,
                                            2 202, 0Ô0³4, 2 20, 0Ô0³9, 2 2,
                                            0Õ0¡0é0Ã0É5, 2 2 (Œ¡ ), 0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1,
                                            2 20Õ0£0ü0È, 0Õ0£0ü0È4, 2 20Õ0é0ó, 0Õ0£0ü0È6, 2 20Ú0½,
                                            0Ú0½1, 2 272, 0Ú0½0Ñ0ü0Ä 2 274, 0Ú0½7,
                                            2 279, 0Ú0Ë0Ò0, 2 283, 0Ú0Ë0Ò6, 2 288,
                                            0Ú0Ë0Ò9, 2 290, 0Ø0ë0Ä1, 2 292, 0Ø0ë0Ä0Ñ0ü0Ä
                                            2 294, 0Ø0ë0Ä5, 2 296, 0Ø0ë0Ä7, 2 298,
                                            420, 2 2 20Ø0¯0¿0ü0ë, 446, 2 2 247, 450,
                                            2 2 251, 45 (l4 ) 2 2 257, 464, 2 2 269,
                                            474, 2 2 275, 487, 50Ô0³, 530Ñ0ü0Ä
                                            544, 547, 552, 558, 561,
                                            56 (l4 ) 569, 570, 572, 579,
                                            580, 581, 582, 584, 588,
                                            589, 591, 594, 596, 597,
                                            5 501, 60 (l4 ) 5 503, 610Ñ0ü0Ä 5 5,
                                            641, 5 543, 644, 5 545, 647,
                                            5 548, 665, 5 569, 670, 5 571,
                                            67 (l4 ) 5 573, 674, 5 577
                                                            ! ?ndex   

 
          COLUMN, 84, 284,  (R´ )6, 289,     <column reference>,  (h* ),
             5 579                            1, 1 (g	 ), 0Ñ0ü0Ä 1 (T ), 5,
          ! !column constraint>,  (Œ¡ ) (l4 )         1 (Œ¡ ), 7, 155, ¬6, 177,
             264,  (Œ¡ )5, 5 545                  1, 185, 7, 189, 0,
          ! !column constraint                191,  (l4 ) 193,  (h* )7, 2,
             definition>,  (Œ¡ ) (l4 ) 263,          (y> )0, 264,  (R´ )4, 2 202, 0Ø0ë0Ä0,
              (Œ¡ )4                            579, 594, 5 50Ô0³, 641, 5 543,
          <column definition>, 1SD,         644, 5 569, 670
             256,  (Œ¡ )0, 261,  (Œ¡ ) (l4 ) 263,    Columns, 0Ø0¯0¿0ü0ë
              (Œ¡ )4, 265,  (Œ¡ )6, 273,  (R´ )4,    COLUMNS, 50Ø0ë0Ä, 544, 545,
             2 2 (ry ), 0Ø0ë0Ä7, 2 298, 644, 5 545        56 (l4 ) 572, 576, 580, 584,
          column descriptor, 0Ú0½, 0Ø0ë0Ä,        588, 596, 5 502, 640
             187,  (l4 ) 197, 8, 199,    COLUMNS base table, 580
              (eå )0, 265,  (Œ¡ )7, 268,  (R´ )6,    COLUMNS view, 544
             287,  (R´ )8, 297, 0Ô0³ (l4 ) 2 20,    COLUMNS_CHECK_DATA_TYPE,
             2 2SD, 0Ó0ë8, 2 272, 0Ø0ë0Ä0Ñ0ü0Ä 2 297,       580
             2 2 251, 580, 581               COLUMNS_CHECK_REFERENCES_
          ! !column name>, 0Ø0¯0¿0ü0ë, 98, 100Ñ0ü0Ä       DOMAIN, 580
              8, 1, 1, 174, 1,    COLUMNS_FOREIGN_KEY_TABLES,
             182, 1, 192, 7, 198,       580
             199,  (eå )0, 245,  (T )6, 262,    COLUMNS_PRIMARY_KEY, 580
             265,  (y] ) (l4 ) 273,  (y] )6, 282,    COLUMNS_UNIQUE, 580
                                         COLUMN_DEFAULT, 544, 580,
             284,  (R´ )6, 287,  (R´ )8, 289,       581
             296,  (Nã )7, 298, 0Ô0³9, 2 2 (Œ¡ ),    COLUMN_DOMAIN_USAGE, 56 (l4 )
             0Õ0£0ü0È1, 2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5, 2 271, 0Ú0½ (l4 )       5 540
             0Ú0½0Ñ0ü0Ä 2 288, 0Ú0Ë0Ò9, 2 290, 0Ø0ë0Ä1,    COLUMN_DOMAIN_USAGE view,
             2 292, 0Ø0ë0Ä4, 2 298, 474, 2 2 287,       56 ( )             50Ô0³, 645, 5 548, 670          COLUMN_NAME, 83, 480, 2 2 281,
          <column name list>, 64, 65,       487, 50Ø0ë0Ä, 544, 545, 547,
             66,  8, 180, 6, 245,        552, 558, 561, 56 (l4 ) 570,
             272,  (y] )4, 296, 0Ú0½1, 2 272,       571, 572, 570Ñ0ü0Ä 580, 581,
             0Ú0½0Ñ0ü0Ä 2 274, 0Ú0Ë0Ò8, 2 292, 464,       584, 588, 589, 596, 597,
             2 2 274, 635, 5 50Ú0Ë0Ò                  60 (l4 ) 5 503, 617, 5 5
          column privilege descriptor    COLUMN_POSITION_NOT_NULL,
             , 5 56                           580
                                         COLUMN_PRIVILEGES, 54 (l4 )
                                            545, 547, 5 502, 640


            Database Language SQL

  


          COLUMN_PRIVILEGES base         COMMITTED, 68, 69, 83, 0Ø0ë0Ä9
             4able, 60 (N  )                 common column name, 1 (h* ),
          COLUMN_PRIVILEGES view, 547        (l4 ) 181
          COLUMN_PRIVILEGES_FOREIGN_     comparable, 6, 21, 27, 2 21,
             KEY_COLUMNS, 5 502               2 20Ñ0ü0Ä 2 24, 2 25, 10Ö0Ã0·0§0ë,  (l4 )
          COLUMN_PRIVILEGES_GRANTEE_        169, 1, 207,  (eå )9, 2 ,
             FOREIGN_KEY_USERS, 60 (N  )         (h* )4, 2 (eå ),  (g	 )4, 2 (y] ),  (y> )1,
          COLUMN_PRIVILEGES_GRANTOR_        20Ö0Ã0·0§0ë,  (y> )7
             FOREIGN_KEY_USERS, 60 (N  )     ! !comparison 0redicate>,
          COLUMN_PRIVILEGES_IS_             156,  (eå )0Ñ0ü0Ä 205,  (eå )7, 2SD,
             ? ?RANTABLE_CHECK, 60 (N  )           (g	 )0, 2 (h* ), 0Ú0½0Ñ0ü0Ä 2 2 244, 446,
          COLUMN_PRIVILEGES_IS_             50Ó0ë, 64 (l4 ) 5 543
             GRANTABLE_NOT_NULL,         compilation unit, 1, 2, 46,
             5 502                            47, 61, 67, 490, 501,
          COLUMN_PRIVILEGES_PRIMARY_        505, 5SD, 51 (l4 ) 5¬, 517,
             KEY, 5 502                       5 (h* ), 654
          COLUMN_PRIVILEGES_TYPE_        COMPLETION, 85
             CHECK, 60 (N  )                 completion condition, 10
          <comma>, 80, 107, 108, 1,    ! !comp op>,  (eå )7, 2SA,  (eå )9,
             1, 173, 6, 178, 7,       210,  (g	 )0, 2 (h* ), 0Ú0½0Ñ0ü0Ä 50Ó0ë
             1, 2,  (y> )9, 245,  (Œ¡ )0,    <concatenation>, 160, ­1,
             0Õ0¡0é0Ã0É9, 2 20Õ0£0ü0È, 0Ö0Ã0·0§0ë6, 2 271, 0Ú0½7,       162, ­0Ñ0ü0Ä 164, 64 ( )             2 282, 0Ø0ë0Ä1, 2 299, 401, 2 2 20Ö0Ã0·0§0ë,    ! !concatenation operator>,
             438, 2 2 251, 474, 2 2 279, 500,       2 (l4 ) 80Ñ0ü0Ä 160, 445
             504, 505, 5, 515, 5,    Concepts, 19
             5 (eå )                         ! !condition>, 497, 2 2 299
          COMMAND_FUNCTION, 80Ñ0ü0Ä 2 2 279,     <condition action>, 497,
             481, 2 2 282, 488                  2 2 299
          ! !comment>, 83, 86, 444, 2 2 262    Conditional rules, 10ª0ü0à          <comment character>, 80µ0ó0Á0ü0à       ! !condition information>,
          <comment introducer>, 83,         479, 2 2 285
             86                          <condition information
          COMMIT, 5 58, 5 5 50, 84, 260,          item>, 479, 2 2 280, 485
             275,  (R´ )1, 2 297, 400Ñ0ü0Ä 2 2 282     ! !condition information item
          ! !commit statement>, 2 2 21, 50,       name>, 479, 2 2 280, 481
             5 (l4 ) 54, 5 57, 5 59, 5 5 51, 253,    ! !condition number>, 2 2 279,
             2 242, 0Ø0¯0¿0ü0ë9, 2 2 203, 410Ñ0ü0Ä 2 2 282,       480, 2 2 285, 670ª0ü0à
             526, 5 571

                                                            Index  10ª0ü0à
  


          CONDITION_NUMBER, 83, 0Õ0é0ó4,     CONSTRAINT, 84, 292, 0Ô0³8,
             479, 2 2 281, 485                  2 20Ú0Ë0Ò, 484, 50Ø0¯0¿0ü0ë, 565, 568,
          conformance, 9, , ­, ,       569, 570, 571, 572, 570Ñ0ü0Ä
             75, 76, 560Ñ0ü0Ä 5 5, 614,         574, 576, 578, 580, 583,
             5 5 (ry ), 626, 5 5 (y] )                  584, 585, 586, 588, 590,
          Conformance, 625                  591, 590Ñ0ü0Ä 595, 596, 598,
          CONNECT, 84, 2 249, 407, 2 2 283,       600, 5 502, 604, 5 505, 606,
             527, 5 579                       5 5SA, 610, 5 5 , 61 (l4 ) 5 579
          CONNECTION, 84, 2 249, 410,      <constraint attributes>,
             484, 5 (y] ), 679                  252,  (ry )0Ñ0ü0Ä 262,  (Œ¡ )0Ñ0ü0Ä 270,
          connection does not exist,        0Ô0³1, 2 2SD, 0Õ0¡0é0Ã0É5, 5 50Õ0£0ü0È
             0Ö0Ã0·0§0ë9, 2 2 210, 41 (l4 ) 5 (y] ), 620     <constraint check time>,
          connection exception, 5 5 51,         252,  (ry )0ª0ü0à             2 249, 408, 2 2 2SD, 410, 2 2 2,    constraint mode, 40, 41,
             5 (y] ), 620                       67, 74,  (ry )0Ñ0ü0Ä 270, 0Õ0¡0é0Ã0É6,
          connection failure, 5 5 51,           2 250, 401, 2 2 202, 528
             2 2 210, 620                    ! !constraint name>, 99, 100Ñ0ü0Ä
          Connection management, 407        105,  (ry ) (l4 ) 259,  (y] )0, 292,
          <connection name>, 5 5 51, 99,
             100Ñ0ü0Ä 104, 407, 2 2 2SA, 410,       2 202, 0Ô0³8, 2 2SD, 0Õ0¡0é0Ã0É5, 2 2 (Œ¡ ),
             2 2 2, 488                       0Õ0¡0é0Ã0É8, 2 20Ú0Ë0Ò, 401, 2 2 202, 586,
          connection name in use,           5 5­, 640, 5 570
             408, 5 5 (eå )                    <constraint name
          ! !connection object>, 410,         definition>,  (ry ) (l4 ) 253,
             2 2 2 , 41 (N  )                       (Œ¡ ) (l4 ) 263,  (Œ¡ )5, 270,  (y] )1,
          ! !connection 4arget>, 407          2 201, 0Ô0³ (l4 ) 2 2SD, 645, 5 565,
          CONNECTION_NAME, 80Ñ0ü0Ä 2 252,         670
             2 254, 480, 2 2 281, 488          ! !constraint name
          <connect statement>, 54,          definition> and
             5 55, 5 5 50, 5 5 51, 5 5 5 (l4 ) 5 5 54, 2 249,       <constraint attributes>,
             0Ø0¯0¿0ü0ë9, 2 2 207, 408, 2 2 2SD, 480Ñ0ü0Ä       252
             488, 5 (y] ), 636, 5 555, 66 (l4 )    <constraint name list>,
             5 569, 67 (N  )                      401, 2 2 202
          consistent, 5 573                CONSTRAINTS, 84, 2 2 201, 400Ñ0ü0Ä
          constraint, 2 2 25                    5 579


            Database Language SQL

  


          CONSTRAINT_CATALOG, 83,        Conventions, 9
             2 2 280, 481, 2 2 286, 487, 541,    CONVERT, 84, ª (l4 ) 5 579
             549, 550, 551, 552, 550Ñ0ü0Ä    Coordinated Universal Time,
             559, 561, 574, 575, 585,       5
             586, 588, 589, 590, 591,    ! !correlation name>, 99,
             590Ñ0ü0Ä 595, 596, 598, 616,       102, 100Ñ0ü0Ä 1,  9, 1 (h* ),
             5 5, 618, 5 565                   ( )          CONSTRAINT_COLUMN_USAGE,       CORRESPONDING, 84, 6,
             561, 5 540                       198, 9, 202,  (R´ )9, 5 543,
          CONSTRAINT_COLUMN_USAGE           679
             6iew, 561                   ! !corresponding column list>
          CONSTRAINT_NAME, 83, 480,         , 196, 8
             2 2 281, 486, 2 2 287, 541, 549,    corresponding join columns,
             550, 551, 55 (l4 ) 553, 559,       181,  (l4 ) 183
             561, 574, 575, 585, 586,    <corresponding spec>, 6
             588, 589, 590, 591, 593,    COUNT, 62, 84, 4, 1 (ry ),
             595, 596, 598, 616, 5 5,       6, 192, 434, 2 2 20Õ0é0ó, 436,
             618, 5 565                       2 2 20Ú0Ë0Ò, 439, 2 2 252, 450Ñ0ü0Ä 2 2 255,
          CONSTRAINT_SCHEMA, 80Ñ0ü0Ä 2 2 280,       457, 2 2 285, 537, 586, 616,
             481, 2 2 286, 487, 541, 549,       5 5, 641, 5 559
             550, 551, 55 (l4 ) 553, 559,    CREATE, 84,  (ry )5, 260,  (Nã )6,
             561, 574, 575, 585, 586,       2 201, 0Ó0ë1, 2 2, 0Õ0¡0é0Ã0É0, 2 2 (ry ),
             588, 589, 590, 591, 593,       48 (l4 ) 2 2 283, 484, 50Õ0é0ó, 536,
             595, 596, 598, 5 5­, 617,       50Ú0½, 538, 50Ø0ë0Ä, 541, 542,
             5 5, 665                       540Ñ0ü0Ä 544, 546, 547, 548,
          CONSTRAINT_TABLE_USAGE,           549, 550, 551, 55 (l4 ) 553,
             559, 640                       554, 555, 556, 557, 558,
          CONSTRAINT_TABLE_USAGE            559, 561, 562, 560Ñ0ü0Ä 564,
             6iew, 559                      565, 567, 568, 569, 570,
          CONSTRAINT_TYPE, 549, 585,        573, 574, 576, 578, 580,
             586, 587, 588, 590, 591,       580Ñ0ü0Ä 584, 585, 588, 590,
             618                            593, 595, 596, 598, 5 500,
          CONSTRAINT_TYPE_CHECK, 585,       60 (l4 ) 5 504, 606, 5 5SA, 610,
             588, 590                       5 5, 616, 5 5, 618
          CONSTRAINT_TYPE_NOT_NULL,
             585
          CONTINUE, 84, 2 2 297, 499


                                                            ! ?ndex  ¬

 
          created local 4emporary        CURRENT_USER, 70, 84,  4,
             table, 2 27, 2 28, 2 29, 5 5 5 (l4 )         1¬,  6, 1,  (Œ¡ )6, 267,
             258,  (Œ¡ )0, 261,  (y] )5, 281,        (Œ¡ )8, 269,  (R´ ) (l4 ) 2 2 (ry ), 0Ú0½5,
             655, 5 568                       50Ô0³, 538, 50Ø0ë0Ä, 541, 542,
          CROSS, 84, 180,  (l4 ) 5 579          540Ñ0ü0Ä 545, 546, 547, 548,
          ! !cross join>, 180, 0Ñ0ü0Ä           549, 550, 551, 55 (l4 ) 553,
             184, 631                       554, 555, 556, 557, 558,
          ! !C storage class>, 504            559, 561, 562, 641, 5 545,
          CURRENT, 84, 2 284, 0Ø0ë0Ä1, 2 2 2,       658, 5 579
             47 (l4 ) 2 2 274, 476, 2 2 277          cursor, 49
          ! !current date 6alue            CURSOR, 84, 0Ú0½1, 2 2 264, 465,
             function>, 10Ø0ë0Ä                 2 2 282, 480Ñ0ü0Ä 2 2 284
          current SQL-connection, 5 5 51,    <cursor name>, 5 5 (l4 ) 99, 103,
             5 5 5 (l4 ) 2 2 2SA, 409, 2 2 210, 411,        0Ö0Ã0·0§0ë1, 2 242, 0Ú0½1, 2 275, 0Ú0½7,
             41 (l4 ) 2 2 2ª                       2 281, 0Ú0Ë0Ò4, 2 291, 0Ø0ë0Ä (l4 ) 2 2 243,
          current SQL-session, 2 2 24,          46 (l4 ) 2 2 264, 467, 2 2 269, 471,
             45, 72, 73, 93, 100,           2 2 272, 474, 2 2 275, 476, 2 2 277,
             101, 100Ñ0ü0Ä 104,  5, 2 2SD,       49 (l4 ) 5 50Õ0é0ó, 636
             2 2 201, 408, 2 2 2SD, 410, 2 2 2 ,    cursor operation conflict,
             2 2 2¬, 417, 2 2 2, 420, 2 2 2 (h* ),        (y] )9, 2 285, 0Ú0Ë0Ò7, 2 292, 0Ø0ë0Ä5,
             42 (l4 ) 2 2 287, 526, 5 553, 654,       2 2 286, 62 ( )             5 556                         Cursors, 49
          ! !current timestamp value       <cursor specification>, 62,
             function>, ª9                  9, 2 271, 0Ú0½ (l4 ) 2 273, 0Ú0½4,
          ! !current time 6alue               2 275, 0Ú0½7, 2 281, 0Ú0Ë0Ò4, 2 291,
             function>, ª9                 44 (l4 ) 2 2 248, 449, 2 2 264, 465,
          CURRENT_DATE, 5 5 50, 84, 10Ø0ë0Ä,        2 2 267, 469, 2 2 272, 474, 2 2 276,
             153, 645, 5 569, 679             477, 5 50Õ0é0ó, 636, 5 50Ú0Ë0Ò, 647
          CURRENT_TIME, 84, ª9, 5 545,    cursor specification cannot
             669, 5 579                       be executed, 459, 5 5 (h* )
          CURRENT_TIMESTAMP, 84, ª9,    CURSOR_NAME, 80Ñ0ü0Ä 2 252, 0Õ0é0ó4,
             645, 5 569, 679                  2 2 280, 481, 2 2 286, 487

                                         <c VARCHAR 6ariable>, 504,
                                            505, 506, 507, 651, 5 564
                                         <c 6ariable definition>,
                                            2 2 290, 504, 505, 506, 507


          ­  Database Language SQL

  


          <c 6ariable specification>,    DATA_TYPE, 0Õ0é0ó4, 50Ø0ë0Ä, 544,
             504                            545, 570, 571, 57 (l4 ) 573,
          CYCLE, 85                         580, 581
                      - D -              DATA_TYPE_CHECK_REFERENCES_
          DATA, 83, 85, 427, 2 2 20Ö0Ã0·0§0ë,           COLLATION, 571
             435, 2 2 20Ø0¯0¿0ü0ë, 439, 2 2 252, 450Ñ0ü0Ä    DATA_TYPE_DESCRIPTOR, 539,
             455, 2 2 256, 458, 5 573             545, 570, 571, 57 (l4 ) 573,
          Data assignment rules, 20Ó0ë        581
          database, 1, 2, 7, 14, 2 2 25,     DATA_TYPE_DESCRIPTOR base
             61, 63, 70, 625                4able, 570
          data exception,  1, 1,      DATA_TYPE_DESCRIPTOR_CHECK_
             6, 10Õ0é0ó, ª6, 10Ú0½, 6,       USED, 572
             7, 148, 9, 150, ¬1,    DATA_TYPE_DESCRIPTOR_
             152, ¬0Ñ0ü0Ä 154, ¬8, 163,       PRIMARY_KEY, 571
             ­7, 2¬,  (y> )1, 20Õ0£0ü0È,  (y> )4,    date, 5
             20Õ0é0ó, 0Ö0Ã0·0§0ë8, 2 263, 42 (l4 ) 2 2 20Õ0é0ó,    DATE, 19, 2 21, 84, 90, 94,
             439, 5 5 (eå )                       1SA,  0, 1 , ª9, 152,
          Data manipulation, 2 271            ­6, 2 2 2 (Nã ), 440, 571, 679
          Data 0arameters, 2 2 28            ! !date literal>, 90, 94
          data 4ype, 19                  ! !date string>, 82, 90
          ! !data 4ype>, 47, 63, 93,       datetime data type
             100Ñ0ü0Ä 107,  0Ñ0ü0Ä 1¬, 4,       descriptor, 29
             192,  (Œ¡ ) (l4 ) 263,  (Œ¡ )4, 265,    ! !datetime factor>, ­5
                                         ! !datetime field>, 2 21, 2 20Ñ0ü0Ä
             0Ô0³1, 2 246, 0Õ0é0ó0, 2 251, 0Õ0é0ó (l4 )       94, 96, 1 ,   (l4 ) 1 (R´ ),
             2 256, 0Õ0é0ó7, 2 258, 0Õ0é0ó9, 2 260,       9, 10Ô0³, 5, 152, ¬0Ñ0ü0Ä
             0Ø0¯0¿0ü0ë1, 2 262, 415, 2 2 2, 420,       154, ­5, 166, ­7, 168,
             2 2 2 (g	 ), 446, 2 2 292, 494, 5 50Ô0³,       ­9, 170,  (eå )9, 2 (y] ),  (y> )8,
             635, 5 540, 647, 5 558             20Ø0ë0Ä,  (T )0, 241,  (Œ¡ )7, 5 559
          data type descriptor, 19,      datetime field overflow,
              (eå ),  (Œ¡ ),  (y] ),  (Nã ), 0Ô0³, 0Ø0¯0¿0ü0ë,        167, 620
             2 27, 192,  (Œ¡ )5, 290, 0Ô0³ (l4 )     ! !datetime literal>, 89, 90,
             0Ô0³9, 2 210, 570, 572             95, 96, 97, 267, 640
          Data 4ypes,                  ! !datetime 0rimary>, 165,
          Data 4ypes of <key 7ord>s         ­6, 167
             used in SQL item            Datetimes, 2 20
             descriptor areas, 2 2 2 (y] )       Datetimes and intervals,  (Nã )
                                         <datetime term>, 165, ­6,
                                            167, ­8, 169, 1, 2 2 245

                                                            Index  17

  


          <datetime type>, 107, 108,     ! !deallocate 0repared
             1 ,  0Ñ0ü0Ä 2 2 2 (Œ¡ ), 450Ñ0ü0Ä 2 2 254,       statement>, 50, 54,
             5 50Ô0³, 640                       60, 61, 63, 0Ø0¯0¿0ü0ë9, 2 2 249,
          <datetime value>, 91, 92,         480Ñ0ü0Ä 5 50Õ0é0ó, 637
             95                          DEC, 84, 108, 2 266, 515,
          ! !datetime 6alue expression>       5­, 520
             , 1 (R´ ), 9, 10Ô0³, ¬5,       DECIMAL, ,  (y] ), 0Ö0Ã0·0§0ë, 84,
             156, ­5, 166, ­7, 168,       107, 1SA, 109, 110, 0Ø0¯0¿0ü0ë0,
             ­9, 170, 64 (N  )                 2 261, 425, 2 2 2 (Œ¡ ), 429, 2 2 240,
          <datetime value function>,        516, 5 (eå ), 52 (l4 ) 571, 657,
             ª9, 140, ­5, 266,  (Œ¡ )7,       5 558
              (Œ¡ )8, 269,  (R´ ) (l4 ) 2 2 (ry ), 0Ú0½5,    DECLARE, 84, 2 271, 0Ø0ë0Ä7, 2 2 264,
             5 541                            490, 5 (eå ), 521
          DATETIME_INTERVAL_CODE, 83,    ! !declare cursor>, 2 2 26, 2 2 29,
             426, 2 2 2 (y] ), 434, 2 2 20Ø0¯0¿0ü0ë, 439,       50, 50Ñ0ü0Ä 56, 57, 58, 5 50,
             440, 2 2 241, 450Ñ0ü0Ä 2 2 254, 455,       2 241, 0Ö0Ã0·0§0ë (l4 ) 2 271, 0Ú0½4, 2 275,
             2 2 256, 457, 5 563                  0Ú0½7, 2 281, 0Ú0Ë0Ò4, 2 291, 464,
          DATETIME_INTERVAL_PRECISION       2 2 276, 477, 2 2 289, 49 (l4 ) 2 2 293,
             , 80Ñ0ü0Ä 2 2 2 (y] ), 434, 2 2 20Ø0¯0¿0ü0ë,           495, 2 2 296, 647, 5 562, 665,
             439, 2 2 240, 441, 2 2 253, 455,       5 568, 671, 5 573, 674, 5 575,
             2 2 256, 457, 5 563                  677
          DATETIME_PRECISION, 539,       declared local temporary
             544, 570, 571, 57 (N  )            table, 2 27, 2 29, 5 5 5 (l4 ) 101,
          <date value>, 90, 91, 96          100Ñ0ü0Ä 245,  (y] )5, 281,  (R´ )0Ñ0ü0Ä
          DAY, 0Ô0³, 0Ó0ë, 0Õ0¡0é0Ã0É, 0Õ0£0ü0È, 84,          294, 0Ø0ë0Ä7, 2 298, 459, 2 2 286,
             95, 1, ­7, 20Ú0Ë0Ò,  (y> )9,        487, 5 555
              (T )0, 2 2 20Ô0³, 441, 2 2 245, 679     DEFAULT, 84, 173, 5, 255,
          <days value>, 91, 94               (Œ¡ )6, 274,  (y] )8, 279,  (R´ )8,
          ! !day-time interval>, 91           2 20, 0Ó0ë1, 2 2, 0Ó0ë4, 2 2­,
          <day-time literal>, 91, 95
          DEALLOCATE, 84, 2 242, 430Ñ0ü0Ä         2 249, 0Ú0Ë0Ò8, 2 291, 0Ø0ë0Ä0Ñ0ü0Ä 2 2 207,
             2 2 247, 449, 2 2 283, 526, 5 579        408, 2 2 210, 41 (l4 ) 5 (y] ), 590,
          ! !deallocate descriptor            591, 59 (l4 ) 5 542, 648, 5 563
             statement>, 54, 60, 62,     <default clause>, 0Õ0é0ó,  (Œ¡ ) (l4 )
             0Ö0Ã0·0§0ë (l4 ) 2 269, 430Ñ0ü0Ä 2 2 283, 526        266,  (Œ¡ )7, 268,  (R´ )7, 2 201,
                                            0Ô0³ (l4 ) 2 205, 0Ô0³9
                                         default collating sequence,
                                            5


          18  Database Language SQL

 
          ! !default option>, 2 26, 2 27,      Definitions, 5
              (Œ¡ )6, 268,  (Œ¡ )9, 573, 581,    Definitions, notations, and
             5 545                            conventions, 5
          ! !default specification>,       definition schema, 2 2 25
             173, 4                    Definition Schema, 75, 77,
          default SQL-connection, 71,       86, 100, 50Õ0£0ü0È, 566
             5 5 5 (l4 ) 2 2 2SA, 41 (N  )               Definitions 0rovided in
          default SQL-session, 72,          4his International
             2 249, 408, 5 (y] )                  Standard, 5
          default time +one, 5 5 50Ñ0ü0Ä 94,     Definitions 4aken from
             96, 1,  (l4 ) 5 556              ISO/IEC 10646, 5
          DEFAULT_CHARACTER_SET_         Definitions taken from ! ?SO
             CATALOG, 50Ú0Ë0Ò, 569              8601, 5
          DEFAULT_CHARACTER_SET_NAME,    DEFINITION_SCHEMA, 5 5 55, 101,
             50Ú0Ë0Ò, 569                       538, 50Ø0ë0Ä, 541, 542, 540Ñ0ü0Ä
          DEFAULT_CHARACTER_SET_            544, 545, 546, 547, 548,
             SCHEMA, 50Ú0Ë0Ò, 569               549, 550, 551, 552, 550Ñ0ü0Ä
          DEFAULT_COLLATE_CATALOG,          554, 555, 556, 557, 558,
             554, 606, 5 507, 674             559, 561, 56 (l4 ) 563, 566,
          DEFAULT_COLLATE_NAME, 554,        567
             606, 5 507, 674               DEFINITION_SCHEMA Schema,
          DEFAULT_COLLATE_SCHEMA,           567
             554, 606, 5 507, 674          degree, 2 27, 2 29, 5 58, 1,
          deferrable, 0Ø0¯0¿0ü0ë, 40, 41,           4, 176, 9, 183, 1,
              (ry )0Ñ0ü0Ä 270,  (y] )5, 2 2 (Œ¡ ), 575,       199,  (eå )0Ñ0ü0Ä 207,  (h* )1, 2,
             587, 598                        (g	 )0, 2 (T ),  (g	 )7, 261,  (Œ¡ )5,
          DEFERRABLE, 84, 252,  (ry )0Ñ0ü0Ä         284,  (Nã )0, 297, 0Ú0½ (l4 ) 2 277,
             270, 0Ô0³1, 2 2 (ry ), 401, 2 2 202,       0Ú0½8, 2 288, 45 (l4 ) 2 2 257, 469,
             541, 549, 550Ñ0ü0Ä 574, 575,       50Ô0³, 617, 5 5
             585, 587, 598, 5 50Õ0£0ü0È, 679     DELETE, 64, 66, 84,  (T )5,
          deferred, 2 2 20, 2 2 21, 5 57, 5 5 56,         260,  (Œ¡ )1, 274,  (y] )5, 281,
             253,  (y] )0, 2 2 (Œ¡ ), 40 (l4 ) 575,        (Nã )8, 2 20Ô0³, 0Ú0Ë0Ò4, 2 286, 0Ø0ë0Ä7,
             587, 599, 655                  2 298, 400Ñ0ü0Ä 2 2 272, 476, 2 2 283,
          DEFERRED, 84,  (ry ) (l4 ) 253,
             2 2 201, 541, 549, 550Ñ0ü0Ä 574,       484, 550, 590, 592, 600,
             575, 585, 587, 598, 599,       5 501
             679                         <delete rule>, 274,  (y] )6,
          Definition, 10                    277,  (y] )8, 279, 59 ( )

                                                            Index  19

  


          <delete statement:             dependent, 10, ª, , ¬,
             0ositioned>, 50, 53,           , 0Ú0½, 0Ø0ë0Ä, 40, 48, 49,
             55, 57, 59, 279, 0Ø0¯0¿0ü0ë9,          50, 51, 64, 65, 66, 69,
             2 284, 0Ú0Ë0Ò5, 2 287, 0Ø0ë0Ä (l4 ) 2 295,       72, 74,  (l4 ) 140, 1,
             47 (l4 ) 2 2 276, 480µ0ó0Á0ü0à                 174,  (l4 ) 197, 9, 200,
          <delete statement:                 (eå )8, 20Ú0½,  (y] )0, 279,  (R´ )9,
             searched>, 50Ñ0ü0Ä 55, 56,         292,  (Nã )6, 2 200, 0Ô0³ (l4 ) 2 204,
             58, 59, 1,  (l4 ) 2 269,         0Ô0³9, 2 20Õ0é0ó, 0Õ0£0ü0È8, 2 242, 0Ö0Ã0·0§0ë6,
             0Ú0Ë0Ò4, 2 286, 0Ú0Ë0Ò7, 2 292, 400Ñ0ü0Ä       2 250, 0Õ0é0ó1, 2 273, 0Ú0½9, 2 280,
             2 2 242, 480Ñ0ü0Ä 2 2 284, 485, 5 (ry ),       0Ú0Ë0Ò (l4 ) 2 283, 0Ø0ë0Ä7, 2 2 200, 41 (l4 )
             670µ0ó0Á0ü0à                           2 2 20Õ0é0ó, 436, 2 2 240, 441, 2 2 248,
          DELETE_RULE, 550, 590, 592        45 (l4 ) 2 2 254, 485, 2 2 293, 494,
          ! !delimited identifier>, 5 5 56,       2 2 295, 526, 50Ô0³, 531, 557,
             8 (l4 ) 86, 87, 98, 50Õ0£0ü0È            558, 562, 607, 5 567, 668,
          ! !delimited identifier body>       5 569, 670, 5 571, 67 (l4 ) 5 573,
             , 8 (l4 ) 86, 87, 88, 100,         674, 5 577, 678
             50Õ0£0ü0È, 629                    dependent 0rivilege
          ! !delimited identifier 0art>       descriptors still exist,
             , 8 (l4 ) 86                       0Õ0£0ü0È8, 5 5 (h* )
          ! !delimiter token>, 82, 86,     deprecated, 47, 75, 0Ö0Ã0·0§0ë6,
             629, 5 540                       2 247, 0Õ0é0ó6, 2 257, 0Õ0é0ó8, 2 259,
          depend, , 0Õ0é0ó, 41, 44, 59,
             2 20Õ0é0ó, 0Õ0£0ü0È6, 2 2 252                  0Ø0¯0¿0ü0ë0, 2 261, 496, 502, 507,
          dependency graph, 2 20Õ0é0ó             510, 514, 5­, 519, 5 (g	 ),
          dependend on,  (Nã ) (N  )                624
                                         Deprecated features, 675
                                         DEPTH, 85
                                         <derived column>,  (l4 ) 182,
                                            1, 192, 5, 2 279, 45 ( )                                         ! !derived column list>,  8,
                                            1, 0, 5 541
                                         derived table, 2 27
                                         ! !derived table>,  8, 1,
                                            0, 178, 0Ñ0ü0Ä 200, 630,
                                            5 50Ó0ë
                                         derived table descriptor,
                                            40


           (eå )  Database Language SQL

  


          DESC, 84, 0Ó0ë4, 2 2­, 0Ú0½1,       Diagnostics area, 2 2 28
             2 273                         diagnostics area limit, 5 57,
          DESCRIBE, 84, 2 2 250, 480Ñ0ü0Ä 5 579       5 5 54, 2 2 200
          ! !describe input statement>,    Diagnostics management, 479
             54, 5 50, 5 51, 2 2 250, 450Ñ0ü0Ä       ! !diagnostics size>, 2 299
             456, 5 50Õ0é0ó, 638, 5 573          DICTIONARY, 85
          ! !describe output statement>    <digit>, 5 5 59, 8 (l4 ) 90, 94,
             , 54, 60, 61, 450, 2 2 251,        96, 98, 148, ¬0, 5 5,
             2 2 257, 670µ0ó0Á0ü0à                      629, 5 566
          ! !describe statement>, 2 269,     <direct implementation-
             2 2 241, 450, 2 2 283, 660µ0ó0Á0ü0à            defined statement>, 525,
          Description, 10                   5 (Œ¡ ), 527, 5 565
          Description of SQL item        Direct invocation of SQL,
             descriptor areas, 2 2 2 (ry )          64, 525
          descriptor, 6, 14              directly, 2 27, 2 2 25, 2 2 29, 51,
          DESCRIPTOR, 84, 2 242, 0Õ0é0ó0Ñ0ü0Ä         58, 5 51, 5 54, 5 5 50, 5 5 50Ñ0ü0Ä 5 5 54,
             0Õ0é0ó4, 2 255, 431, 2 2 20Õ0£0ü0È, 434,       90Ñ0ü0Ä 100, 101, 1 (h* ), 5,
             438, 2 2 251, 48 (l4 ) 2 2 283, 484,       156, ­7, 181, 5, 186,
             5 (Œ¡ ), 539, 545, 570, 571,       9, 190,  (l4 ) 193, 4,
             57 (l4 ) 573, 581, 5 579             20Ô0³,  (Œ¡ )4, 2 201, 0Õ0£0ü0È5, 2 20Ø0¯0¿0ü0ë,
          <descriptor item name>,           0Õ0£0ü0È8, 2 291, 0Ø0ë0Ä (l4 ) 2 294, 415,
             434, 2 2 20Õ0é0ó, 438, 2 2 20Ø0ë0Ä             2 2 2, 419, 2 2 274, 485, 5 (ry ),
          <descriptor name>, 5 5 (l4 ) 99,        640Ñ0ü0Ä 5 556, 670ª0ü0à             102, 104, 105, 0Ö0Ã0·0§0ë (l4 ) 2 2 20Ó0ë,    directly contain, 11, 1 (h* ),
             2 2 20Õ0¡0é0Ã0É, 430Ñ0ü0Ä 2 2 20Ö0Ã0·0§0ë, 435, 2 2 20Ø0¯0¿0ü0ë,       5, 156, ­7, 181, 5,
             437, 2 2 20Ú0Ë0Ò, 439, 2 2 241, 451,       186, 9, 190,  (l4 ) 193,
             2 2 253, 455, 2 2 257, 458, 5 (Œ¡ ),        (y> )0, 264, 0Ô0³1, 2 292, 0Ø0ë0Ä4,
             637, 5 50Ú0Ë0Ò                       2 2 274, 485, 5 543
          Descriptors,                 directly dependent on, 2 20Õ0é0ó
          deterministic, 40, 9,        Directly executable SQL-
             0Ñ0ü0Ä 200,  (R´ ) (l4 ) 2 2 (ry )             statements, 58
          DIAGNOSTICS, 84, 2 299, 479,     ! !directly executable
             2 2 284, 679                       statement>, 525
          diagnostics area, 41, 48,      ! !direct select statement:
             49, 67, 74, 0Ö0Ã0·0§0ë8, 2 250,          multiple rows>, 50Ñ0ü0Ä 56,
             0Õ0é0ó1, 2 2 200, 479, 2 2 282, 485,       57, 58, 59, 1, 480Ñ0ü0Ä
             526, 5 (R´ ), 529, 5 5, 660Ñ0ü0Ä       5 (ry ), 526, 50Ô0³
             668, 5 569


                                                            ! ?ndex   (h* )

 
          ! !direct SQL data statement>    domain, ¬, 0Õ0é0ó, 0Ø0¯0¿0ü0ë, 0Ú0½, 40,
             , 5 (ry ), 528, 5 50Ø0ë0Ä, 65 (N  )          43, 44, 45, 47, 52, 64,
          <direct SQL statement>, 64,       65, 66, 75, 76, 98, 100Ñ0ü0Ä
             67, 71, 73, 74, 93, 100,       105, 109, 1¬, 4, 145,
             101, 0Ö0Ã0·0§0ë9, 2 2 2¬, 417, 2 2 2,       ¬4, 192,  (y> )6, 255,  (ry )6,
             525, 5 (Œ¡ ), 527, 5 (R´ ), 529,       257,  (ry )8, 262,  (Œ¡ )0Ñ0ü0Ä 264,
             5 5, 625, 5 5 (y] ), 640, 5 551,        (Œ¡ )5, 266,  (Œ¡ )7, 268,  (R´ )1,
             655, 5 556                       282,  (Nã )0, 2 201, 0Ô0³ (l4 ) 2 203,
          dirty read, 68                    0Ô0³4, 2 205, 0Ô0³6, 2 207, 0Ô0³8,
          DISCONNECT, 84, 2 255, 41 (l4 )         2 2SD, 0Ó0ë0, 2 2, 0Õ0¡0é0Ã0É9, 2 20Ô0³,
             2 2 283, 679                       0Õ0£0ü0È1, 2 20Õ0£0ü0È, 0Õ0£0ü0È4, 2 20Ø0¯0¿0ü0ë, 0Õ0£0ü0È7,
          disconnect error, 2 2 2ª, 620µ0ó0Á0ü0à       2 20Ú0Ë0Ò, 0Ø0¯0¿0ü0ë8, 2 2 246, 48 (l4 ) 2 2 283,
          <disconnect object>, 2 2 2
          ! !disconnect statement>, 54,       50Õ0£0ü0È, 539, 540, 541, 562,
             5 5 51, 2 269, 41 (l4 ) 2 2 2ª, 480Ñ0ü0Ä        564, 565, 569, 570, 57 (l4 )
             636, 5 572                       573, 574, 575, 581, 593,
          distinct, 5, 5 5, 7, 19, 20,        595, 596, 605, 5 50Õ0£0ü0È, 634,
              (g	 ),  (Nã ), 0Ú0Ë0Ò, 0Ø0ë0Ä, 0Ñ0ü0Ä           5 540, 644, 5 546
             7, 273,  (y] )7, 278,  (y] )9,    DOMAIN, 84,  (ry )8, 2 201, 0Ô0³4,
              (Nã )8, 2 273, 490Ñ0ü0Ä 2 2 294, 495,       2 2SD, 0Õ0¡0é0Ã0É9, 2 20Ú0Ë0Ò, 48 (l4 ) 564,
             2 2 296, 531, 5 568, 670, 5 573,       565, 5 580
             677                         domain constraint, 2 2 20, 2 2 20ª0ü0à          DISTINCT, 84, 4, 1 (Œ¡ ),        ! !domain constraint>, 0Õ0é0ó,
             193, 4, 195,  (eå )8, 50Ø0ë0Ä,        5, 154, 0Ô0³1, 2 202, 0Ô0³7,
             541, 544, 617, 5 50Ô0³, 631,       564
             670                         domain constraint
          division by zero, ¬8, 5 5 (eå )        descriptor, 0Ø0¯0¿0ü0ë, 40,
                                            43, 0Ô0³ (l4 ) 2 2SD, 0Õ0£0ü0È7, 2 20Ú0Ë0Ò
                                         Domain constraints, 43
                                         domain definition, 2 25
                                         ! !domain definition>, 52,
                                            109, 1¬,  (ry )5, 256,  (ry )7,
                                            266,  (R´ )1, 2 201, 0Ô0³ (l4 ) 2 203,
                                            0Ó0ë0, 2 268, 480Ñ0ü0Ä 5 544, 646


           (g	 )  Database Language SQL

  


          domain descriptor, 2 26, 2 2 24,     DOMAIN_CONSTRAINTS_FOREIGN_
             75,  (y> )6, 267,  (Œ¡ )8, 2 201,        KEY_CHECK_CONSTRAINTS,
             2 202, 0Ô0³4, 2 205, 0Ô0³6, 2 207,       574
             2 2SA, 0Ó0ë8, 2 20Ô0³, 0Õ0£0ü0È1, 2 20Ú0½,    DOMAIN_CONSTRAINTS_FOREIGN_
             0Õ0£0ü0È8, 573                       KEY_DOMAINS, 574
          <domain name>, 2 25, 98, 103,    DOMAIN_CONSTRAINTS_FOREIGN_
             105, 144, 5, 154,  (l4 )       KEY_SCHEMATA, 574
              (ry )8, 262,  (Œ¡ )0Ñ0ü0Ä 264,  (Œ¡ )5,    DOMAIN_CONSTRAINTS_
             2 201, 0Ô0³ (l4 ) 2 204, 0Ô0³5, 2 20,       INITIALLY_DEFERRED_
             2 207, 0Ô0³8, 2 2SD, 0Õ0¡0é0Ã0É9, 2 20Ó0ë,       NOT_NULL, 574
             2 20Õ0£0ü0È, 0Õ0£0ü0È8, 2 2 246, 581, 5 540,    DOMAIN_CONSTRAINTS_PRIMARY_
             644                            KEY, 574
          Domains, 2 25                    DOMAIN_DEFAULT, 50Ø0ë0Ä, 570ª0ü0à          DOMAINS, 50Ø0ë0Ä, 56 (l4 ) 572,        DOMAIN_NAME, 539, 541, 544,
             570Ñ0ü0Ä 574, 580, 5 504, 616,       545, 56 (l4 ) 570, 571, 572,
             5 540                            570Ñ0ü0Ä 574, 575, 580, 581,
          DOMAINS base table, 573           5 504
          DOMAINS 6iew, 50Ø0ë0Ä              DOMAIN_NAME_NOT_NULL, 574
          DOMAINS_CHECK_DATA_TYPE,       DOMAIN_SCHEMA, 539, 541,
             573                            544, 545, 56 (l4 ) 570, 571,
          DOMAINS_FOREIGN_KEY_              572, 570Ñ0ü0Ä 574, 575, 580,
             SCHEMATA, 573                  581, 5 504
          DOMAINS_PRIMARY_KEY, 570µ0ó0Á0ü0à      DOMAIN_SCHEMA_NOT_NULL, 574
          DOMAIN_CATALOG, 539, 541,      dormant SQL-connection, 5 5 51,
             544, 545, 56 (l4 ) 570, 571,       5 5 5 (l4 ) 2 2 2SA
             57 (l4 ) 573, 574, 575, 580,    dormant SQL-session, 5 5 5 (l4 )
             581, 5 504                       2 2 2SA, 411
          DOMAIN_CATALOG_NOT_NULL,       DOUBLE, 19, 27, 2 24, 84,
             574                            1SA,  0, 2 252, 0Õ0é0ó7, 2 258,
          DOMAIN_CONSTRAINTS, 541,          0Õ0é0ó9, 2 2 2 (ry ), 426, 2 2 2 (Nã ), 440,
             574, 593, 616                  500, 50 (l4 ) 507, 51 (l4 ) 5ª,
          DOMAIN_CONSTRAINTS base           571, 5 558
             table, 574                  <double period>, 80Ñ0ü0Ä 500,
          DOMAIN_CONSTRAINTS 6iew,          517
             541                         ! !double iuote>, 5 5 59, 80, 8 (l4 )
          DOMAIN_CONSTRAINTS_CHECK_         86, 87
             DEFERRABLE, 574             ! !doublequote symbol>, 8 (l4 )
                                            86, 87


                                                            Index  20ª0ü0à
  


          DROP, 84,  (ry )8, 259,  (R´ )8,       ! !drop 4ranslation
              (R´ )9, 290,  (Nã ) (l4 ) 294, 0Ô0³0,       statement>, 50Ñ0ü0Ä 259,
             2 20, 0Ô0³8, 2 2SD, 0Ó0ë0Ñ0ü0Ä 2 2,       0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (T ), 0Ø0¯0¿0ü0ë8, 2 2 283, 634,
             0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (R´ ), 0Õ0£0ü0È8, 2 298, 480Ñ0ü0Ä       5 50Õ0é0ó, 637, 5 50Ø0ë0Ä
             680                         <drop view statement>, 5 (l4 )
          ! !drop assertion statement>,       258,  (Nã )0, 2 200, 0Õ0£0ü0È8, 2 268,
             5 (l4 ) 259, 0Õ0¡0é0Ã0É8, 2 20Ú0Ë0Ò, 0Ø0¯0¿0ü0ë8,        480Ñ0ü0Ä 5 546
             480Ñ0ü0Ä 5 50Ö0Ã0·0§0ë, 635, 5 50Ú0½, 639     duplicate, 5 5, 7, 1 (Œ¡ ), 1,
          ! !drop behavior>,  (ry )8, 289,        194, 5, 201,  (eå ) (l4 ) 2 (y> ),
             292,  (Nã )4, 2 200, 0Ô0³9, 2 20Õ0£0ü0È        0Õ0£0ü0È (l4 ) 5 5
          ! !drop character set            dyadic,  (T ), ¬7, 158, ­1,
             statement>, 52,  (ry )9,           2 2 243
             0Ó0ë0Ñ0ü0Ä 2 268, 480Ñ0ü0Ä 5 546          dyadic operator, 5 5,  (T ), 440ª0ü0à          <drop collation statement>,    DYNAMIC, 480ª0ü0à             50Ñ0ü0Ä 259, 0Ó0ë8, 2 2, 0Ø0¯0¿0ü0ë8,     ! !dynamic close statement>,
             2 2 283, 634, 5 50Õ0é0ó, 637, 5 50Ø0ë0Ä        50, 53, 55, 57, 58, 59,
          <drop column default              62, 0Ø0¯0¿0ü0ë9, 2 2 271, 480ª0ü0à             clause>,  (R´ )6, 288, 645      ! !dynamic cursor name>, 99,
          <drop column definition>,         104, 105, 467, 2 2 269, 471,
              (R´ )0Ñ0ü0Ä 289,  (Nã )0, 5 545             2 2 272, 474, 2 2 275, 638, 5 540
          ! !drop domain constraint        <dynamic declare cursor>,
             definition>, 0Ô0³4, 2 2SA,         49, 53, 56, 57, 58, 60,
             5 50Ö0Ã0·0§0ë                            62, 0Ö0Ã0·0§0ë1, 2 243, 448, 2 2 264,
          <drop domain default              467, 2 2 269, 471, 2 2 272, 474,
             clause>, 2 204, 0Ô0³6, 5 50Ö0Ã0·0§0ë         2 2 276, 477, 2 2 289, 49 (l4 ) 2 2 294,
          <drop domain statement>,          495, 5 50Ú0Ë0Ò, 647, 5 551
             52,  (ry )8, 2 2SD, 0Ó0ë0, 2 20Ú0Ë0Ò,     <dynamic delete statement:
             0Ø0¯0¿0ü0ë8, 2 2 283, 646                  0ositioned>, 50, 53,
          <drop schema statement>,          55, 57, 59, 60, 62, 0Ø0¯0¿0ü0ë9,
             52,  (ry )8, 259, 0Ø0¯0¿0ü0ë8, 2 2 283,        2 2 272, 480ª0ü0à             5 544                         ! !dynamic fetch statement>,
          <drop table constraint            50, 53, 55, 57, 58, 59,
             definition>,  (R´ )0Ñ0ü0Ä 292,         62, 0Ø0¯0¿0ü0ë9, 2 2 241, 451, 2 2 256,
             293, 646                       457, 2 2 269, 470, 2 2 283, 638,
          ! !drop 4able statement>, 5 (l4 )       5 563
              (ry )8, 294,  (Nã )5, 2 268, 0Ø0ë0Ä8,
             480Ñ0ü0Ä 5 544


           (T )  Database Language SQL

  


          <dynamic open statement>,      effective, , ª, ,  (y> ),
             50, 50Ñ0ü0Ä 55, 57, 58, 59,         (Œ¡ ), 0Ó0ë, 0Õ0£0ü0È, 0Ö0Ã0·0§0ë, 0Õ0é0ó, 0Ú0Ë0Ò,
             5 5 (l4 ) 2 269, 441, 2 2 255, 464,        0Ø0ë0Ä, 41, 49, 51, 72, 73,
             2 2 265, 467, 2 2 268, 480Ñ0ü0Ä 5 563        74, 87, 94, 96,   (l4 )
          ! !dynamic parameter                1, 0Ñ0ü0Ä 10Ø0ë0Ä, ­6, 171,
             specification>, 5 50Ñ0ü0Ä            0Ñ0ü0Ä 184, 5, 190, 8,
              4, 1¬,  6, 168,  (R´ )1,       2SA,  (eå )9, 20Ø0¯0¿0ü0ë,  (T )8, 253,
             296, 0Õ0¡0é0Ã0É5, 2 2 20Ø0¯0¿0ü0ë, 439, 2 2 243,        (ry )6, 258,  (ry )9, 273,  (y] )6,
             450, 2 2 253, 454, 2 2 255, 456,       280,  (R´ ) (l4 ) 289,  (Nã )0, 292,
             2 2 260, 46 (l4 ) 2 2 267, 525, 5 541,        (Nã )4, 299, 0Ô0³0, 2 202, 0Ó0ë0,
             67 (N  )                           2 2ª, 0Ó0ë5, 2 2, 0Ó0ë8, 2 2 (h* ),
          <dynamic select statement>,       0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (Œ¡ ), 0Õ0£0ü0È0, 2 20Ó0ë, 0Õ0£0ü0È (l4 )
             53, 56, 57, 58, 59, 60,        2 20Ú0Ë0Ò, 0Ö0Ã0·0§0ë (l4 ) 2 249, 0Ú0½0Ñ0ü0Ä 2 275,
             5 51, 5 5 (l4 ) 2 250, 44 (l4 ) 2 2 252,         0Ú0½6, 2 285, 0Ú0Ë0Ò6, 2 287, 0Ú0Ë0Ò9,
             455, 2 2 256, 459, 2 2 262             2 293, 0Ø0ë0Ä5, 2 297, 0Ø0ë0Ä8, 2 2 203,
          <dynamic single row select        417, 2 2 20Ø0ë0Ä, 455, 2 2 256, 457,
             statement>, 53, 56, 57,        2 2 258, 485, 2 2 293, 526, 5 (y] ),
             58, 59, 5 51, 5 5 (l4 ) 2 250,           531, 570, 570Ñ0ü0Ä 574, 576,
             44 (l4 ) 2 2 252, 456, 2 2 259, 460,       578, 580, 585, 598, 5 500,
             2 2 262, 480Ñ0ü0Ä 5 50Ú0½                  60 (l4 ) 5 504, 656, 5 568, 669
          Dynamic SQL, 2 2 2 (ry )               effectively, 
          dynamic SQL error, 431,        ELSE, 84, 1, 142, 540Ñ0ü0Ä
             435, 2 2 20Ø0ë0Ä, 448, 2 2 255, 456,       544, 680
             2 2 257, 458, 2 2 259, 460, 2 2 265,    ! !else clause>, 1, 142,
             2 2 267, 621                       0ª0ü0à          <dynamic 5pdate statement:     ELSEIF, 85
             0ositioned>, 50, 53,        Embeddable SQL-statements,
             55, 57, 59, 5 50, 5 5 (l4 ) 299,       55
             0Ø0¯0¿0ü0ë9, 2 2 274, 475, 2 2 283
          DYNAMIC_FUNCTION, 80Ñ0ü0Ä 2 2 279,
             2 2 281, 48 (l4 ) 2 2 288

                      - E -
          EACH, 85


                                                            ! ?ndex   (ry )

 
          embedded, 1,  (l4 ) 2 2 29, 51,        <embedded SQL declare
             5 (l4 ) 55, 56, 57, 58, 5 50,        section>, 61, 489, 2 2 290,
             5 51, 5 5 (l4 ) 5 50Ñ0ü0Ä 5 5 55, 5 5 59, 1,       491, 2 2 295, 496, 501, 505,
              5, 1­, 489, 2 2 290, 491,       5SD, 51 (l4 ) 5¬, 517, 5 (h* )
             49 (l4 ) 2 2 293, 494, 2 2 295, 496,    <embedded SQL end declare>,
             2 2 297, 498, 2 2 299, 500, 501,       61, 489, 2 2 290, 491, 2 2 295,
             502, 504, 505, 506, 507,       517
             5SA, 509, 510, 51 (l4 ) 5ª,    ! !embedded SQL Fortran
             514, 5¬, 516, 5, 518,       0rogram>, 5 51, 2 2 289, 491,
             519, 5 (eå ), 521, 5 (g	 ), 610Ñ0ü0Ä       2 2 293, 495, 2 2 296, 498, 5,
             5 5, 625, 5 5 (y] ), 639, 5 551,       510Ñ0ü0Ä 5
             655, 5 561, 66 (l4 ) 5 563, 670Ñ0ü0Ä    <embedded SQL host 0rogram>
             5 574, 675, 5 578                  , 61, 63, 489, 2 2 290, 491,
          ! !embedded character set           2 2 292, 490Ñ0ü0Ä 2 2 296, 497, 2 2 299,
             declaration>, 2 2 289, 490,        614, 5 5 (ry ), 627, 5 573, 674,
             49 (l4 ) 2 2 293, 495, 2 2 296, 651,       5 578
             660µ0ó0Á0ü0à                        <embedded SQL MUMPS
          <embedded exception               declare>, 489, 2 2 290,
             declaration>, 55, 2 2 289,         491, 2 2 295
             495, 2 2 297, 498, 2 2 299          <embedded SQL MUMPS
          Embedded SQL, 489                 program>, 61, 489, 2 2 291,
          <embedded SQL Ada program>,       490Ñ0ü0Ä 2 2 298, 515, 5­
             61, 489, 2 2 291, 490Ñ0ü0Ä 2 2 295,     <embedded SQL Pascal
             498, 500, 501, 502             0rogram>, 5 51, 2 2 289, 491,
          ! !embedded SQL begin               2 2 293, 495, 2 2 298, 517, 5,
             declare>, 5 51, 2 2 289, 490,        519
             2 2 291, 495, 5               ! !embedded SQL PL/I program>
          ! !embedded SQL COBOL               , 5 51, 2 2 289, 491, 2 2 293,
             0rogram>, 5 51, 2 2 289, 491,        495, 2 2 298, 520, 5 (h* ), 52 ( )             2 2 293, 495, 2 2 298, 508, 5SD,    ! !embedded SQL statement>,
             510, 5 575                       5 51, 1¬, 489, 2 2 290, 491,
          ! !embedded SQL C 0rogram>,         2 2 292, 490Ñ0ü0Ä 2 2 295, 501, 505,
             5 51, 2 2 289, 491, 2 2 293, 495,        509, 5, 515, 5, 521,
             498, 504, 505, 50, 507        5 50Ø0ë0Ä, 651
                                         Embedded syntax, 61


           (Œ¡ )  Database Language SQL

  


          <embedded variable name>,      ! !escape character>, 2,
             1,  5, 1­, 490, 2 2 293,        (h* )5, 2, 447, 5 543
             494, 5 573                    <exact numeric literal>,
          END, 84, 1, 142, 490,           90, 94, 95, 147, 9,
             540Ñ0ü0Ä 544                       267
          END-EXEC, 84, 2 2 289, 491, 5 580    <exact numeric 4ype>,  (R´ ),
          <end field>, 171,  (y> )8, 20Ø0ë0Ä,       107, 1SD, 0Õ0é0ó6, 2 2 253, 454,
              (T )0, 241,  (T ) (N  )                 502, 658, 5 561
          end-af-line indicator, 83,     exact numeric value, 28
             5 556                         EXCEPT, 84, 196, 7, 201,
          Entry SQL, 5 5 (ry ), 629, 5 540           (eå ) (l4 ) 576, 640Ñ0ü0Ä 5 580
          Entry SQL Specifications,      exception, 10, 1 (l4 ) 10Ñ0ü0Ä 2 24,
             640                            2 25, 2 26, 2 2 21, 2 2 27, 2 2 28, 5 (l4 )
          environment,  (l4 ) 14, 16, 2 2 25,       55, 56, 57, 58, 5 50, 5 54,
             46, 70, 71, 72, 74, 75,        5 57, 5 59, 5 5 51, 86, 95, 1 ,
             5 5 57, 246, 0Ö0Ã0·0§0ë4, 5 554, 655,          (l4 ) 1 (Œ¡ ), ª5, 10Ø0¯0¿0ü0ë, ª7,
             660Ñ0ü0Ä 5 569                       146, 7, 148, 9, 150,
          EQUALS, 85                        ¬1, 152, ¬0Ñ0ü0Ä 154, ¬8,
          ! !equals operator>, 80,  (eå )7,       163, ­7, 203,  (h* )5, 20Ó0ë,
             2 291, 434, 2 2 20Ú0Ë0Ò, 479, 500,        (y> )0Ñ0ü0Ä 20Ö0Ã0·0§0ë,  (y> )5, 20Ø0¯0¿0ü0ë,  (ry )0Ñ0ü0Ä
             505                            279,  (Nã )9, 2 20Ú0Ë0Ò, 0Ö0Ã0·0§0ë8, 2 249,
          EQUAL_KEY_DEGREES, 5 5
          EQUAL_KEY_DEGREES assertion       2 250, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 275, 0Ú0½8, 2 279,
             , 5 5                          0Ú0Ë0Ò0, 2 281, 0Ú0Ë0Ò (l4 ) 2 283, 0Ú0Ë0Ò4,
          equivalent, 1, , ¬, 61,        2 286, 0Ú0Ë0Ò9, 2 292, 0Ø0ë0Ä0Ñ0ü0Ä 2 294,
             5 5 (l4 ) 5 5 51, 86, 87, 9 (l4 ) 90Ñ0ü0Ä        400, 2 2 203, 404, 2 2 205, 407,
             94, 100, 1SA, 1, 142,        2 2 2SA, 409, 2 2 210, 41 (l4 ) 2 2 2ª,
             146, 7, 174, 1, 197,       415, 2 2 2, 419, 2 2 2 (eå ), 42 (l4 )
             8, 2 ,  (h* ) (l4 ) 2,  (g	 )9,       2 2 20Ó0ë, 430Ñ0ü0Ä 2 2 20Õ0é0ó, 439, 2 2 241,
             241,  (T )5, 246,  (Œ¡ )0Ñ0ü0Ä 264,       440Ñ0ü0Ä 2 2 247, 448, 2 2 249, 450,
             0Õ0£0ü0È0Ñ0ü0Ä 2 288, 0Ø0ë0Ä7, 2 2 292, 496,       2 2 251, 455, 2 2 256, 457, 2 2 258,
             501, 50 (l4 ) 50, 507, 510,       459, 2 2 260, 46 (l4 ) 2 2 265, 466,
             510Ñ0ü0Ä 5­, 518, 5, 521,       2 2 267, 479, 2 2 282, 485, 2 2 286,
             5 (g	 ), 530µ0ó0Á0ü0à                      489, 2 2 295, 497, 2 2 298, 499,
          error in assignment, 435,         5 (Œ¡ ), 527, 5 (R´ ), 624, 5 554,
             2 2 20Ø0ë0Ä, 620                       655, 5 562, 666, 5 567, 67 ( )          ESCAPE, 84,  (h* )4, 2¬, 0Õ0é0ó0µ0ó0Á0ü0à     EXCEPTION, 84, 479, 5 580

                                         exception condition, 10

                                                            Index  27

  


          Exceptions, 10                 explicit, 8, 10, ¬,  (eå ),
          EXEC, 84, 489, 2 2 291                 (y> ), 0Ó0ë, 0Õ0é0ó, 41, 44, 45,
          EXECUTE, 84, 2 254, 459, 2 2 262,       50, 66, 67, 68, 69, 70,
             2 2 283, 680                       71, 72, 74, 86, 101,
          ! !execute immediate                102, 104, 1 , 5, 10Ô0³,
             statement>, 14, 2 2 24,            0Ñ0ü0Ä 152, ¬0Ñ0ü0Ä 174, 6,
             45, 54, 59, 61, 63, 64,        197, 8, 202,  (T )1, 242,
             5 5 50Ñ0ü0Ä 90Ñ0ü0Ä 100, 101, 1¬,          (ry )0Ñ0ü0Ä 256,  (ry )8, 260,  (y] )0,
             0Ø0¯0¿0ü0ë9, 2 2 2¬, 417, 2 2 2, 46 (l4 )       272,  (R´ )0Ñ0ü0Ä 284,  (Nã ) (l4 ) 294,
             2 2 283, 650Ñ0ü0Ä 5 554, 656              (Nã )6, 297, 0Ô0³0, 2 201, 0Ô0³ (l4 )
          ! !execute statement>, ,          2 204, 0Ô0³9, 2 2 , 0Ó0ë (l4 ) 2 2ª,
             54, 59, 5 51, 5 54, 2 269,           0Ó0ë5, 2 2­, 0Ó0ë8, 2 2 (h* ), 0Õ0¡0é0Ã0É0Ñ0ü0Ä
             441, 2 2 247, 448, 2 2 255, 456,       2 2 (ry ), 0Õ0¡0é0Ã0É6, 2 2 (R´ ), 0Õ0¡0é0Ã0É9, 2 20Õ0£0ü0È,
             2 2 257, 459, 2 2 260, 480Ñ0ü0Ä 5 563        0Õ0£0ü0È4, 2 20Õ0é0ó, 0Ö0Ã0·0§0ë1, 2 248, 0Ú0½7,
          ! !existing character set           2 279, 0Ø0ë0Ä (l4 ) 2 2 200, 446, 2 2 247,
             name>, 0Ó0ë1, 2 2                469, 2 2 274, 488, 2 2 293, 579,
          EXISTS, 84, 2 (g	 ),  (y] )1, 273,
             2 203, 544, 576, 617, 5 5        584, 594, 629, 5 50Õ0¡0é0Ã0É, 654,
          ! !exists 0redicate>, 191,          5 555, 656, 5 561, 66 (l4 ) 5 567
              (eå )5, 2 (g	 )                    Explicit,  (y> ),  (T ),  (ry ),  (Œ¡ ),
                                            0Õ0é0ó, ­1, 187, 0Ú0½ ( )                                         ! !explicit 4able>, 196, 7,
                                            202, 63 ( )                                         explicit type conversion,
                                            2 25
                                         ! !exponent>, 90, 95
                                         exposed,  8, 1
                                         <extended cursor name>, 62,
                                            99, 10 (l4 ) 104, 440Ñ0ü0Ä 2 2 262,
                                            465, 2 2 266, 467, 5 5 (Nã ), 657
                                         ! !extended statement name>,
                                            62, 99, 10 (l4 ) 104, 447,
                                            2 2 248, 465, 5 5 (Nã ), 657, 5 572
                                         Extensions and options, 626
                                         EXTERNAL, 84, 2 2, 0Õ0¡0é0Ã0É0,
                                            5 561, 680
                                         ! !external collation>, 2 2,
                                            0Ó0ë7


           (R´ )  Database Language SQL

  


          <external collation name>,     fixed-length, 90Ñ0ü0Ä 94, 1¬,
             2 2, 0Ó0ë5                       5, 147, 8, 150, ¬1,
          ! !external 4ranslation>, 2 2 (eå )       161, ­ (l4 ) 163,  (y> )1, 20Õ0¡0é0Ã0É,
          <external translation name>        (y> )4, 20Õ0é0ó,  (y> )7, 268, 506,
             , 0Õ0¡0é0Ã0É0, 2 2 (h* )                     507, 658
          EXTRACT, 84, 1 (R´ ), ª0, 2 2 244,    fixed-length coding, 5, 5 5
             680                         flagger, 5 5 56, 5 5 57, 5 5 (Œ¡ ), 656
          <extract expression>,  (Nã ),      Flagger requirements, 5 5 (Œ¡ )
             0Ö0Ã0·0§0ë, 8, 1 (Nã ), ª0, 10Ó0ë,     FLOAT, 19, 27, 2 24, 84, 1SA,
             5 541, 659                        0, 2 261, 425, 2 2 2 (Œ¡ ), 429,
          ! !extract field>, 8, 1 (Nã ),        2 2 240, 520, 5 (g	 ), 571, 5 557,
             10Ô0³, 444                       658
          <extract source>, 8, 1 (Nã ),    ! !fold>, 2 (l4 ) 10Õ0¡0é0Ã0É, ª0Ñ0ü0Ä 10Õ0é0ó,
             10Ô0³                            ª6, 10Ú0½, 444, 5 50Ô0³
                      - F -              FOR, 84, 10Õ0¡0é0Ã0É, ª0Ñ0ü0Ä 149,
          <factor>, ¬7, 168, ­9           ¬1, 2 2, 0Õ0¡0é0Ã0É0, 2 20Õ0£0ü0È, 0Õ0£0ü0È5,
          FALSE, 84,  (g	 )9, 20Ô0³, 0Õ0é0ó6,         2 20Ø0¯0¿0ü0ë, 0Õ0£0ü0È7, 2 262, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 264,
             5 580                            0Ø0¯0¿0ü0ë6, 2 271, 0Ú0½ (l4 ) 2 273, 0Ú0½4,
          feature not supported, 407,       2 292, 445, 2 2 264, 465, 2 2 274,
             2 2 210, 621                       635, 5 50Ú0Ë0Ò
          FETCH, 84, 0Ú0½7, 2 2 269, 480µ0ó0Á0ü0à      FOREIGN, 84, 264,  (y] )4, 569,
          <fetch orientation>, 2 277,         570Ñ0ü0Ä 574, 576, 580, 580Ñ0ü0Ä
             0Ú0½8, 2 279, 0Ú0Ë0Ò0, 2 2 269, 635,       584, 585, 587, 588, 590,
             5 50Ú0Ë0Ò                            591, 595, 596, 598, 600,
          ! !fetch statement>, 50, 53,        5 502, 605, 5 50, 608, 5 510,
             55, 57, 58, 59, 2 250,           618
             2 268, 0Ú0½7, 2 280, 480Ñ0ü0Ä 5 50Õ0é0ó,    Format, 9,  , , ¬, 86,
             5 547, 671, 5 577                  407, 2 2 2SA, 415, 2 2 2, 419,
          ! !fetch target list>, 0Ú0½7,         2 2 2 (eå ), 431, 2 2 243, 447, 2 2 259,
             2 279, 0Ú0Ë0Ò0, 2 2 270, 647, 5 571        46 (l4 ) 2 2 265, 525, 5 (Œ¡ ), 625,
          Fields in datetime items,         5 563, 665, 5 567
             0Ô0³                          form-af-use, 5 5,  (eå ),  (h* ),  (g	 ),
          Fields in day-time ! ?NTERVAL       99, 100Ñ0ü0Ä 104, ª (l4 ) 10Õ0£0ü0È,
             items, 0Õ0¡0é0Ã0É                      ª4, 10Ø0¯0¿0ü0ë, ª7, 148, 9,
          Fields in 9ear-month
             ! ?NTERVAL items, 2 2 (N  )            ¬1, 248,  (T )9, 250, 444,
          FIRST, 84, 0Õ0é0ó (l4 ) 2 277, 0Ú0½8,         5 507, 619, 5 50Ô0³, 657, 5 559,
             2 279, 680                       660


                                                            Index  29

  


          form-af-use conversion, 6,     FROM, 84, 1 (R´ ), ª0, 10Õ0¡0é0Ã0É,
             20, 2 (l4 ) 103, 104, 10Õ0£0ü0È,         ª0Ñ0ü0Ä 10Ö0Ã0·0§0ë, 9, 151, ¬ (l4 )
             ª4, 10Ø0¯0¿0ü0ë, ª7, 2 2 244, 630,       153, ¬4, 178, 0, 182,
             5 557, 659                       0Ñ0ü0Ä 184, 7, 198,  (y] )1,
          ! !form-af-use conversion>,         272,  (y] )0Ñ0ü0Ä 276,  (R´ )9, 294,
             2 (l4 ) 10Õ0¡0é0Ã0É, ª0Ñ0ü0Ä 10Ø0¯0¿0ü0ë, ª7,        0Ô0³0, 2 203, 0Ó0ë0, 2 2 , 0Ó0ë0Ñ0ü0Ä
             444, 5 50Ô0³, 659                  2 2, 0Ó0ë8, 2 2 (eå ), 0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 20Õ0£0ü0È,
          <form-of-use conversion           0Ø0¯0¿0ü0ë (l4 ) 2 263, 0Ø0¯0¿0ü0ë4, 2 266, 0Ú0½7,
             name>, 99, 103, 104,           2 280, 0Ú0Ë0Ò4, 2 286, 400Ñ0ü0Ä 2 2 207,
             10Õ0¡0é0Ã0É, ª0Ñ0ü0Ä 10Ö0Ã0·0§0ë, ª6, 5 50Ô0³,       408, 2 2 2¬, 417, 2 2 2, 420,
             657                            2 2 20Ó0ë, 44 (l4 ) 2 2 244, 445, 2 2 247,
          FORM_OF_USE, 554, 606, 5 507,       465, 2 2 269, 47 (l4 ) 2 2 276, 485,
             665                            50Ú0½, 538, 50Ø0ë0Ä, 541, 542,
          FORTRAN, 80Ñ0ü0Ä 243, 0Õ0é0ó9, 2 264,       540Ñ0ü0Ä 544, 545, 546, 547,
             490Ñ0ü0Ä 5 5, 610Ñ0ü0Ä 5 5             548, 549, 550, 551, 552,
          <fortran host identifier>,
             490, 5, 510µ0ó0Á0ü0à                 553, 554, 555, 556, 557,
          <fortran 4ype specifica-          558, 559, 561, 562, 560Ñ0ü0Ä
             tion>, 5, 510Ñ0ü0Ä 5,          571, 57 (l4 ) 573, 576, 578,
             5 50Ø0ë0Ä, 651                       580, 581, 580Ñ0ü0Ä 584, 585,
          ! !Fortran variable                 586, 588, 591, 590Ñ0ü0Ä 595,
             definition>, 490, 5,         596, 5 504, 606, 5 5SA, 610,
             510µ0ó0Á0ü0à                           5 5 , 616, 5 5, 618, 5 547
          FOUND, 84, 0Õ0é0ó (l4 ) 2 2 297, 499       <from clause>, 1, 7,

                                            8, 179, 5, 187, 9,
                                            193, 631, 5 50Õ0é0ó, 636, 5 50Ú0Ë0Ò
                                         FULL, 42, 84, 0, 182,
                                            4, 2 (T ),  (g	 )5, 274,  (y] )6,
                                            277,  (y] )8, 590, 591, 5 5ª,
                                            618, 5 580
                                         Full SQL, 625
                                         Function, 9, 10


          0Ô0³  Database Language SQL

  


                      - G -              ! !get diagnostics statement>
          ? ?ENERAL, 85                       , 54, 2 269, 479, 2 2 281,
          <general literal>, 89, 97         48 (l4 ) 2 2 284, 485, 2 2 288, 651
          generally contain, 11, 1 (y] ),    ! !get item information>, 2 2 20Ö0Ã0·0§0ë
             ª9, 186,  (R´ )1, 282,  (Nã )6,    GLOBAL, 0Ú0Ë0Ò, 84, 99, 104,
             0Ô0³1, 2 207, 0Õ0¡0é0Ã0É5, 2 275, 0Ú0Ë0Ò7,       260,  (Œ¡ )1, 576, 577, 5 50Õ0£0ü0È,
             2 290, 0Ø0ë0Ä (l4 ) 2 296, 474, 5 50Ø0¯0¿0ü0ë,       680
             5 541                         global temporary table, 2 27,
          generally 5nderlying table,       2 28, 2 29, 5 5 5 (l4 ) 258,  (Œ¡ )0,
             0Ú0Ë0Ò, 0Ñ0ü0Ä 299, 0Ú0½ (l4 ) 2 287,        261,  (y] )5, 281, 630Ñ0ü0Ä 5 555,
             2 289, 0Ø0ë0Ä0, 2 292, 0Ø0ë0Ä6, 2 2 274        668
          General Rules, 9, 10, ,      ? ?O, 84, 2 2 297, 499
             10Ñ0ü0Ä 14, 15, 2 2 20, 2 2 24, 5 59,     ? ?OTO, 84, 2 2 297
             70, 76, 6, 187,  (eå ) (l4 )      <go to>, 2 2 297, 498, 2 2 299
                                         <goto target>, 2 2 297, 498
             205,  (ry )0Ñ0ü0Ä 258,  (Œ¡ )1, 278,    ? ?RANT, 65, 75, 84,  (T )8,
              (y] )9, 282,  (R´ )4, 289,  (Nã ) (l4 )       2 2¬, 0Õ0¡0é0Ã0É1, 2 2 (Nã ), 0Õ0£0ü0È0, 2 20Ó0ë,
             294, 0Ô0³0, 2 250, 0Õ0é0ó1, 2 276,       0Õ0£0ü0È (l4 ) 2 20Õ0£0ü0È, 0Õ0£0ü0È5, 2 20Ø0¯0¿0ü0ë, 0Õ0£0ü0È7,
             0Ú0½9, 2 283, 0Ú0Ë0Ò9, 2 293, 0Ø0ë0Ä5,       2 2 284, 530Ñ0ü0Ä 5 501, 600Ñ0ü0Ä 5 505
             400Ñ0ü0Ä 2 2 2ª, 441, 2 2 243, 456,    grantable privilege, 5 56
             2 2 257, 458, 2 2 260, 460Ñ0ü0Ä 2 2 264,    ? ?RANTEE, 539, 542, 545,
             465, 2 2 267, 468, 2 2 269, 470,       546, 547, 548, 554, 555,
             2 2 271, 47 (l4 ) 2 2 275, 476, 2 2 277,       556, 5 500, 601, 5 502, 600Ñ0ü0Ä
             485, 2 2 295, 528, 50Ô0³, 625,       5 504, 605
             5 562, 660Ñ0ü0Ä 5 572, 670Ñ0ü0Ä 5 577     ! !grantee>,  (T )5, 246, 0Õ0¡0é0Ã0É9,
          ! !general set function>,           2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0¡0é0Ã0É, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ú0Ë0Ò
             4, 1 (Œ¡ ), 630, 5 541          GRANTOR, 546, 547, 548,
          <general 6alue specifica-         600, 5 502, 600Ñ0ü0Ä 5 504, 605
             4ion>,  4, 1­,  7,       ! !grant statement>, 52, 65,
             2 202, 0Ø0¯0¿0ü0ë (l4 ) 5 541, 658             66,  (T )5, 248,  (ry )5, 2 2¬,
          GET, 84, 2 2 , 434, 2 2 279,           0Õ0¡0é0Ã0É1, 2 2 (Nã ), 0Õ0£0ü0È0, 2 20Ó0ë, 0Õ0£0ü0È (l4 )
             480Ñ0ü0Ä 2 2 284, 680                  2 268, 484
          <get count>, 2 2 20Ö0Ã0·0§0ë               ! !greater than operator>,
          <get descriptor informa-          80,  (eå )7, 2 273, 531
             4ion>, 434                  ! !greater than or equals
          ! !get descriptor statement>,       operator>, 83,  (eå )7
             54, 5 50, 5 5 (l4 ) 2 269, 434,       ? ?ROUP, 84, 7, 5 5­, 617

             435, 2 2 20Ø0¯0¿0ü0ë, 480Ñ0ü0Ä 5 572

                                                            Index  2 21

  


          <group by clause>, 2 28, 1,               - I -
             177, 7, 189, 0Ñ0ü0Ä 203,    identified privilege
             296, 0Ú0Ë0Ò0Ñ0ü0Ä 5 50Ó0ë, 635, 5 543        descriptor, 0Õ0£0ü0È5
          grouped table, 2 28, 1 (T ),        ! !identifier>, 2 2 24, 2 2 26, 5 5 (l4 )
             7, 187, 9, 192, 4        5 5 51, 5 5 50Ñ0ü0Ä 98, 99, 100,
          grouped view, 7, 179,           10 (l4 ) 105, 408, 2 2 2, 431,
             5, 203,  (Nã )6, 2 283, 631,       2 2 247, 451, 2 2 265, 481, 50Õ0£0ü0È,
             5 50Õ0¡0é0Ã0É, 635, 5 543                  534, 564, 630, 5 556, 657,
          ! !grouping column reference>       5 577
             , 7                       <identifier>s for use
          <grouping column reference        with ! !get diagnostics
             list>, 7                     statement>, 481

                      - ? ! -              <identifier body>, 8 (l4 ) 86,
          ? !AVING, 84, 189                   87, 88, 100, 530Ñ0ü0Ä 5 5 (Nã ),
          <having clause>, 2 28, 1,         640
             1 (ry ), 7, 181, 5, 189,    ! !identifier 0art>, 82, 86
             0Ñ0ü0Ä 203,  (Nã )6, 2 283, 631,    <identifier start>, 82, 85,
             5 50Õ0é0ó, 640Ñ0ü0Ä 5 578                  86
          ! !hexit>, 89, 90, 92, 94        IDENTITY, 84, 0Õ0¡0é0Ã0É0, 2 2 (h* ), 680
          <hex string literal>, 82,      ! ?F, 85
             86, 89, 9 (l4 ) 94, 95, 97,     ! ?GNORE, 85
             266,  (Œ¡ )7, 5 5 (Nã )               immediate, 40, 41,  (ry )0Ñ0ü0Ä
          ! !high>, 16, 17                    270, 0Õ0¡0é0Ã0É6, 2 250, 401, 5 (R´ ),
          <host identifier>, 2 2 290,           575, 587, 599
             2 2 292, 495, 2 2 296               ! ?MMEDIATE, 84,  (ry ) (l4 ) 253,
          <host label identifier>,           (y] )0, 2 201, 0Õ0¡0é0Ã0É5, 2 2 201, 400Ñ0ü0Ä
             497, 2 2 298, 499                  2 2 262, 480Ñ0ü0Ä 5 50Õ0£0ü0È, 680
          <host PLg label 6ariable>,    immediate base, 299
             497, 2 2 298, 499               immediately contain, 11,
          host variable,  (y> ),  (T )             14, 1,  9, 1 (g	 ), 9,
          ! !host 6ariable definition>,       155, ¬7, 166, ­7, 173,
             2 2 289, 490, 2 2 292, 494, 2 2 295,       4, 191,  (l4 ) 193,  (eå )0,
             496                            203,  (Œ¡ )0Ñ0ü0Ä 271,  (y] ) (l4 ) 297,
          HOUR, 0Ô0³, 0Ó0ë, 0Õ0¡0é0Ã0É, 0Õ0£0ü0È, 73,         0Ô0³ (l4 ) 2 2 , 0Ó0ë5, 2 2 (eå ), 0Õ0£0ü0È5,
             84, 95,   (l4 ) 1ª, 0Ñ0ü0Ä         2 290, 0Ø0ë0Ä (l4 ) 2 296, 408, 2 2 2 (g	 ),
             10Ô0³, ­6, 167,  (y> )8, 20Ø0ë0Ä,       431, 2 2 244, 465, 2 2 274, 648
             240, 42 (l4 ) 2 2 20Ô0³, 441, 5 580
          ! !hours value>, 91, 94

          0Õ0¡0é0Ã0É  Database Language SQL

  


          immediately-executable         ! !implementation-defined
             SQL-statement, 57              collation name>, 0Ó0ë4,
          implementation-defined, 5 5,        2 2¬, 661
             20, 21, 28, 29, 2 24, 2 2 24,     ! ?mplementation-defined
             2 2 25, 2 2 26, 2 2 27, 51, 56, 5 51,        elements, 650ª0ü0à             5 54, 5 57, 5 59, 5 5 51, 5 5 5 (l4 ) 5 5 50Ñ0ü0Ä     ! !implementation-defined
             74, 77, 83, 87, 93, 101,       4ranslation name>, 0Õ0¡0é0Ã0É0,
             10 (l4 ) 103, 104, 1SA, 109,       2 2 (h* ), 661
             110,   (l4 ) 1¬,  6, 1 (ry ),    ! !implementation-defined
             9, 10Õ0£0ü0È, ª4, 146, 7,       5niversal character
             ¬7, 158, ­1, 162, 1,       form-of-use name>,  (T )8,
              (y> )0Ñ0ü0Ä 20Õ0é0ó,  (y> )8, 240,  (T )8,       249, 660
             249,  (ry )0, 256, 0Ó0ë1, 2 2,    implementation-dependent,
             0Ó0ë5, 2 2, 0Õ0¡0é0Ã0É0, 2 2 (h* ), 0Ö0Ã0·0§0ë1,       5 5, 10, , ª, , 0Ú0½,
             2 244, 0Ö0Ã0·0§0ë8, 2 256, 0Õ0é0ó7, 2 258,       0Ø0ë0Ä, 40, 48, 49, 50, 51,
             2 259, 0Ø0¯0¿0ü0ë0, 2 261, 0Ø0¯0¿0ü0ë (l4 ) 2 263,       64, 65, 66, 69, 72, 74,
             2 264, 0Ø0¯0¿0ü0ë5, 2 266, 0Ú0½0Ñ0ü0Ä 2 2 200,        (l4 ) 140, 1, 174,  (l4 )
             404, 2 2 207, 408, 2 2 2 (eå ), 42 (l4 )       197, 9, 200,  (eå )8, 20Ú0½,
             2 2 20Ó0ë, 43 (l4 ) 2 2 240, 441, 2 2 242,        (y] )0, 279,  (Nã )6, 2 202, 0Ô0³9,
             440Ñ0ü0Ä 2 2 245, 447, 2 2 252, 454,       2 242, 0Ö0Ã0·0§0ë6, 2 250, 0Õ0é0ó1, 2 273,
             2 2 281, 485, 2 2 286, 488, 2 2 292,       0Ú0½9, 2 280, 0Ú0Ë0Ò (l4 ) 2 283, 0Ø0ë0Ä7,
             501, 502, 506, 5SD, 510,       2 2 200, 41 (l4 ) 2 2 20Õ0é0ó, 436, 2 2 240,
             5ª, 516, 5, 521, 5 (g	 ),       441, 2 2 248, 45 (l4 ) 2 2 254, 485,
             525, 5 (Œ¡ ), 527, 5 (R´ ), 529,       2 2 293, 494, 2 2 295, 526, 50Ô0³,
             50Ó0ë, 564, 565, 586, 5 507,       531, 5 507, 667, 5 568, 669,
             609, 5 5, 610Ñ0ü0Ä 5 5, 615,       5 570, 671, 5 572, 670Ñ0ü0Ä 5 574,
             5 5, 624, 5 5 (Œ¡ ), 630, 5 553,       677, 5 578
             654, 5 555, 656, 5 557, 658,    Implementation-dependent
             659, 5 560, 661, 5 562, 660Ñ0ü0Ä       elements, 5 567

             5 564, 665, 5 566
          ! !implementation-defined
             character repertoire
             name>, 20, 248,  (T )9,
             0Ó0ë1, 5 560


                                                            Index  2 20ª0ü0à
  


          implicit, ª,  (eå ), 0Ó0ë, 41,      ! ?N, 84, 1 (R´ ),  (h* ) (l4 ) 2 2 245, 539,
             44, 67, 69, 70, 71, 72,        542, 540Ñ0ü0Ä 545, 546, 547,
             5 5 50Ñ0ü0Ä 5 5 54, 101, 10 (l4 ) 103,         548, 554, 555, 556, 570,
             104, 1SA, 109, 110,  1,       571, 57 (l4 ) 573, 574, 576,
             1¬, 1, 1 (g	 ), 4, 1 (ry ),       578, 580, 581, 583, 584,
             ª0, 10Ö0Ã0·0§0ë,  (l4 ) 143, 9,       585, 586, 588, 590, 591,
             151, ¬ (l4 ) 153, ­6, 174,       590Ñ0ü0Ä 595, 596, 598, 600,
             1, 182,  (y> ) (l4 ) 240,  (T )1,       5 502, 604, 5 50, 608, 5 5 ,
             242,  (ry ) (l4 ) 253,  (ry )5, 256,       61 (l4 ) 5 5ª, 618
             258,  (Œ¡ )0, 263,  (Œ¡ )6, 268,    include, 6, 10Ñ0ü0Ä 14, 15, 19,
              (y] )0, 272,  (y] )5, 276,  (R´ )0Ñ0ü0Ä       21, 2 (l4 ) 2 20, 2 2 (l4 ) 2 24, 2 26,
              (R´ )4, 292,  (Nã )4, 296,  (Nã )7,       2 27, 2 29, 2 2 20, 2 2 21, 2 2 2 (l4 ) 2 2 20Ñ0ü0Ä
             0Ô0³0, 2 201, 0Ô0³ (l4 ) 2 204, 0Ô0³9,       2 2 24, 2 2 28, 50, 5 5 55, 5 5 56, 86,
             0Ó0ë1, 2 2, 0Ó0ë0Ñ0ü0Ä 2 2¬, 0Ó0ë6,       100,  1, 1, 1, 1 (g	 ),
             2 2, 0Õ0¡0é0Ã0É0, 2 2 (h* ), 0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (ry ),       6, 10Õ0é0ó, 5, 153, 6,
             0Õ0¡0é0Ã0É6, 2 2 (R´ ), 0Õ0¡0é0Ã0É9, 2 20Õ0£0ü0È, 0Õ0£0ü0È4,       192, 0Ñ0ü0Ä 194,  (y> )6, 246,
             2 20Õ0é0ó, 0Ö0Ã0·0§0ë1, 2 244, 0Ø0¯0¿0ü0ë (l4 ) 2 263,        (T )8, 249,  (ry )0, 251,  (ry )0Ñ0ü0Ä
             0Ø0¯0¿0ü0ë4, 2 265, 0Ø0¯0¿0ü0ë6, 2 267, 0Ú0½ (l4 )       260,  (Œ¡ )1, 264,  (Œ¡ )5, 268,
             2 277, 0Ú0½9, 2 288, 0Ø0ë0Ä (l4 ) 2 297,        (y] )0, 271,  (y] )0Ñ0ü0Ä 275,  (y] )6,
             0Ø0ë0Ä9, 2 2 200, 400Ñ0ü0Ä 2 2 205, 407,       282,  (R´ )0Ñ0ü0Ä 284,  (R´ )8, 289,
             2 2 2, 431, 2 2 246, 447, 2 2 269,        (Nã )1, 292,  (Nã )4, 296,  (Nã )7,
             474, 2 2 276, 477, 2 2 288, 49 (l4 )       299, 0Ô0³0, 2 201, 0Ô0³ (l4 ) 2 204,
             2 2 293, 501, 50, 510, 5ª,       0Ô0³8, 2 2SD, 0Ó0ë0, 2 2 , 0Ó0ë (l4 )
             518, 5 (h* ), 579, 584, 594,       2 2ª, 0Ó0ë5, 2 2­, 0Ó0ë8, 2 2 (h* ),
             5 50Õ0£0ü0È, 655, 5 556, 657, 5 560,       0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (ry ), 0Õ0¡0é0Ã0É6, 2 2 (R´ ), 0Õ0¡0é0Ã0É9,
             661, 5 562, 660Ñ0ü0Ä 5 564, 669,       2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0é0ó, 0Õ0£0ü0È6, 2 20Ú0½,
             5 572                            0Ú0½ (l4 ) 2 283, 0Ú0Ë0Ò4, 2 286, 0Ú0Ë0Ò9,
          ! ?mplicit, 20Ñ0ü0Ä 24, 25, 26,         2 292, 0Ø0ë0Ä4, 2 297, 45 (l4 ) 2 2 254,
             2 25, 1 (g	 ), ª4                   495, 2 2 296, 505, 50, 521,
          implicit type conversion,         569, 581, 5 50Õ0é0ó, 640, 5 541,
             2 25                             640Ñ0ü0Ä 5 568, 686
          implicit +ero-bit padding,     ! ?ncompatibilities 7ith
             149, ¬1, 152,  (y> ) (l4 ) 268,       ISO/IEC 9075:1989, 5 577
             620µ0ó0Á0ü0à                        independent, 14, 2 20Õ0é0ó, 0Õ0£0ü0È6
                                         independent node, 2 20Õ0é0ó, 0Õ0£0ü0È6
                                         ! ?ndex 4ypography, 15
                                         indicator,  (y> )1, 5 556


          0Ö0Ã0·0§0ë  Database Language SQL

  


          INDICATOR, 84, 1, 0Õ0é0ó (l4 )       ! ?NFORMATION_SCHEMA, 20, 2 2 25,
             0Õ0é0ó0Ñ0ü0Ä 2 2 2 (y] ), 434, 2 2 20Õ0é0ó, 436,       5 5 55, 103,  (T )9, 2 255, 530Ñ0ü0Ä
             439, 2 2 252, 450Ñ0ü0Ä 2 2 255, 456,       50Õ0é0ó, 536, 50Ú0½, 538, 50Ø0ë0Ä,
             2 2 258, 500, 502, 670µ0ó0Á0ü0à            541, 542, 540Ñ0ü0Ä 545, 546,
          indicator overflow, 20Ó0ë,          547, 548, 549, 550, 551,
             5 5 (eå )                            55 (l4 ) 553, 554, 555, 556,
          indicator 0arameter, 48,          557, 558, 559, 561, 562,
             1,  5, 1­,  (l4 ) 20Ó0ë,       568, 569, 570, 573, 574,
             0Õ0é0ó6, 2 2 20Õ0é0ó, 436, 2 2 20Ø0ë0Ä, 630,       576, 578, 580, 580Ñ0ü0Ä 584,
             5 559, 661                       585, 588, 590, 593, 595,
          ! !indicator parameter>,  4,       596, 598, 5 500, 60 (l4 ) 5 504,
             1¬,  6, 192, 436, 2 2 20Ø0ë0Ä,       606, 5 507, 608, 5 5SD, 610,
             630, 5 559                       5 5, 665
          Indicator parameters, 48       ! ?NFORMATION_SCHEMA Schema,
          indicator variable, 47, 48,       535
             1,  5, 1­               ! ?NFORMATION_SCHEMA_CATALOG_
          ! !indicator variable>, 1,        NAME, 50Ø0¯0¿0ü0ë, 537, 50Ú0Ë0Ò,
             1¬,  6, 192, 630, 5 559        539, 541, 54 (l4 ) 543, 545,
          ! ?nformation Schema, 1, 10,
             2 2 25, 5 50Ñ0ü0Ä 5 56, 5 59, 5 5 55, 5 5 57,        546, 547, 548, 549, 550,
              (R´ ) (l4 ) 299, 0Õ0¡0é0Ã0É6, 2 298, 530Ñ0ü0Ä       551, 55 (l4 ) 553, 554, 555,
             50Ö0Ã0·0§0ë, 535, 50Ø0¯0¿0ü0ë, 538, 540,       556, 557, 558, 559, 561,
             541, 542, 540Ñ0ü0Ä 545, 546,       562
             547, 548, 549, 550, 551,    INFORMATION_SCHEMA_CATALOG_
             552, 550Ñ0ü0Ä 554, 557, 558,       NAME base table, 50Ø0¯0¿0ü0ë
             560, 561, 56 (l4 ) 563, 567,    INFORMATION_SCHEMA_CATALOG_
             568, 640, 5 552, 667             NAME_CARDINALITY, 537
          Information Schema and         ! ?NFORMATION_SCHEMA_
             Definition Schema, 50Õ0£0ü0È         CATALOG_NAME_CARDINALITY
                                            assertion, 50Ú0½
                                         INFORMATION_SCHEMA_CATALOG_
                                            NAME_PRIMARY_KEY, 536
                                         ! ?nformative elements, 9
                                         INITIALLY, 84, 252,  (ry )0Ñ0ü0Ä
                                            270, 0Ô0³1, 2 2 (ry ), 541, 549,
                                            550Ñ0ü0Ä 574, 575, 585, 587,
                                            598, 599, 5 50Õ0£0ü0È, 680


                                                            ! ?ndex  0Õ0é0ó

 
          initially deferred, 575,       insufficient item
             587, 599                       descriptor areas, 45 (l4 )
          initially immediate,  (ry )0Ñ0ü0Ä         2 2 253, 620ª0ü0à             575, 587, 599               ! ?NT, 84, 108, 2 256, 0Õ0é0ó7,
          ! ?NITIALLY_DEFERRED, 541,          2 266, 500, 502, 515, 5­
             549, 553, 574, 575, 585,    INTEGER, 19, 27, 2 24, 84,
             587, 598, 599                  1SA,  0, 2SD, 0Õ0é0ó (l4 ) 2 257,
          INNER, 84, 180, 1, 182,         0Õ0é0ó8, 2 259, 0Ø0¯0¿0ü0ë0, 2 261, 425,
             0Ñ0ü0Ä 5 580                       2 2 2 (Œ¡ ), 429, 2 2 240, 50 (l4 ) 507,
          innermost, 8,  ,  8             510, 5, 510Ñ0ü0Ä 5, 516,
          ! !in 0redicate>, 205,  (h* ) (l4 )         5, 519, 5 (g	 ), 565, 571,
             2 2 244, 446                       657, 5 562
          ! !in 0redicate 6alue>, 2      integrity constraint, 1,
          ! ?NPUT, 84, 450, 5 580               2 2 20, 5 57, 5 59, 5 5 54, 154,
          input parameter, 5 51, 5 5 (l4 )
             0Ö0Ã0·0§0ë7, 2 248, 0Õ0é0ó0, 2 257, 0Ø0¯0¿0ü0ë (l4 )       20Ø0¯0¿0ü0ë,  (ry )0Ñ0ü0Ä 270, 0Õ0¡0é0Ã0É5, 2 285,
             2 263, 0Ø0¯0¿0ü0ë4, 2 265, 0Ø0¯0¿0ü0ë6, 2 267,       0Ú0Ë0Ò7, 2 2 203, 486
             2 2 259, 467, 5 561               ! ?ntegrity constraints, 40
          ! ?NSENSITIVE, 50, 84, 0Ú0½1,      integrity constraint
             0Ú0½ (l4 ) 2 274, 0Ú0½6, 2 2 264, 465,       6iolation, ¬4, 20Ø0¯0¿0ü0ë,
             5 50Õ0é0ó, 638, 5 580                   (ry )0Ñ0ü0Ä 2 2 203, 486, 5 5 (h* ), 62 ( )          INSERT, 64, 66, 84,  (T )5,       ! !integrity no>, 16, 17
             246,  (Œ¡ )1, 284,  (R´ )9, 298,    ! !integrity yes>, ­, 
             0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ö0Ã0·0§0ë, 0Ú0Ë0Ò8,    <intermediate>, ­, 
                                         Intermediate SQL, 625, 5 5 (Nã )
             0Ú0Ë0Ò9, 2 298, 484, 5 500, 601,    Intermediate SQL
             60 (l4 ) 5 503, 63 (N  )                 Specifications, 5 5 (Nã )
          ! !insert column list>, 174,     INTERSECT, 84, 196, 7,
             0Ú0Ë0Ò8, 2 289, 446                  200,  (eå )1, 202,  (eå )8, 5 543,
          <insert columns and source>       670, 5 580
             , 0Ú0Ë0Ò8, 2 290, 648             INTERVAL, , 0Ô0³, 0Ó0ë, 0Õ0¡0é0Ã0É,
          <insert statement>, 53, 55,       0Õ0£0ü0È, 49, 73, 83, 84, 91,
             56, 58, 59, 1, 0Ñ0ü0Ä          94, 108, 1,  0Ñ0ü0Ä 1 (y> ),
             174, 6, 202,  (Nã )9, 2 269,       ­6, 167, ­9, 170,  (eå )9,
             0Ú0Ë0Ò8, 2 290, 44 (l4 ) 2 2 244, 446,       2 (y] ),  (g	 )8, 2 253, 42 (l4 ) 2 2 2 (Œ¡ ),
             2 2 284, 485, 5 (ry ), 631, 5 50Õ0¡0é0Ã0É,       427, 2 2 2 (Nã ), 434, 2 2 20Ø0¯0¿0ü0ë, 439,
             636, 5 542, 648, 5 573             2 2 240, 441, 2 2 245, 450Ñ0ü0Ä 2 2 254,

                                            2 2 255, 456, 2 2 257, 571, 5 563,
                                            680

          2 26  Database Language SQL

 
          interval data 4ype             <interval value expression>
             descriptor, 29, 2 20             , 8, 1 (Nã ), ª0, 155,
          <interval factor>, 168, ­9       ¬6, 165, ­6, 167, ­8,
          interval field overflow,          169, 0, 171, 42 (l4 ) 5 542
             ¬4, 20Õ0£0ü0È,  (y> )5, 5 5 (eå )          intervening, 11, 2 26, 1,
          <interval fractional              8, 193, 7, 200
             seconds precision>,         INTO, 84, 0Ú0½7, 2 282, 0Ú0Ë0Ò8,
             0Õ0£0ü0È, 96,  0Ñ0ü0Ä 1 (Nã ),  (y> )9,         2 2 251, 459, 2 2 269
              (T )0, 241,  (T ) (l4 ) 2 2 2 (y] ), 445,    <introducer>, 46, 89, 93,
             2 2 253, 455, 5 560                  98, 100
          <interval leading field        ! ?ntroduction, 50Õ0£0ü0È, 566, 5 5 (ry )
             precision>, 0Õ0¡0é0Ã0É,   (l4 )        in 5sage by, 2 201, 0Ô0³7
             170,  (eå )9, 20Ø0ë0Ä,  (T )0, 241,    invalid authorization
              (T ) (l4 ) 2 2 2 (y] ), 445, 2 2 253, 455,       specification, 0Ö0Ã0·0§0ë8,
             660                            2 2 207, 408, 2 2 2 (eå ), 621
          <interval literal>, 89, 91,    invalid catalog name, 2 2 2¬,
             94, 95, 96, 97, 267, 640       621
          <interval primary>, ­8,       invalid character set name,
             ­9                            2 2 2, 621
          <interval qualifier>, 0Ô0³,      invalid character 6alue
             0Õ0¡0é0Ã0É, 91, 94, 95, 96, 108,       for cast, 146, 7, 148,
             1 ,  0Ñ0ü0Ä 168, 0, 171,       9, 150, ¬1, 152, ¬0Ñ0ü0Ä
              (y> )9, 240,  (T )1, 242,  (Œ¡ )7,       154, 620
             2 2 2 (y] ), 429, 2 2 245, 450Ñ0ü0Ä 2 2 255,    invalid condition number,
             644                            2 2 200, 485, 5 5 (h* )
          ! ?ntervals, 0Õ0¡0é0Ã0É                  invalid connection name,
          ! !interval string>, 82, 86,        2 2 2SA, 62 ( )             91                          invalid cursor name, 440Ñ0ü0Ä
          ! !interval 4erm ´, ­8,           2 2 262, 465, 2 2 266, 467, 5 5 (g	 )
             ­9, 170                    invalid cursor state, 0Ú0½5,
          ! !interval 4erm  (ŒÇ ), ­8, 169       2 278, 0Ú0Ë0Ò1, 2 284, 0Ø0ë0Ä (l4 ) 2 2 249,
          <interval term>, 165, ­6,        487, 5 5 (g	 )
             ­7, 168, ­9, 2 2 245          invalid datetime format,
          ! !interval 4ype>, 107, 1SA,        1, 620
             1 ,  0Ñ0ü0Ä 2 2 2 (y] ), 450Ñ0ü0Ä 2 2 255,    invalid descriptor count,
             640                            2 2 255, 457, 5 5 (h* )
          ! !interval 6alue expression     invalid descriptor index,
             1>, 168, ­9, 170              431, 2 2 20Õ0é0ó, 439, 5 5 (h* )


                                                            ! ?ndex  0Ú0½

 
          invalid escape character,      ISO/IEC 9075, xi, xiii,
             2¬, 620                       xvi, 5 5 55, 5 5 56, 85, 5 577,
          invalid escape sequence,          678, 5 585, 686
             2¬, 620                    ! ?SOgEC 9579- (l4 ) 2 2, 619, 5 5 (g	 )
          invalid 0arameter 6alue,       ISO/IEC 9899, 0Ñ0ü0Ä 243, 505
             2 248, 620                    ! ?SOgEC DIS 1000Õ0¡0é0Ã0É, 1
          invalid schema name, 2 2 2,      ! ?SO 1989, 2 2,  (T )0Ñ0ü0Ä 5SD
             62 (N  )                        ISO  (eå ) (g	 ), 0Ñ0ü0Ä 249
          invalid SQL descriptor         ISO 6160, 0Ñ0ü0Ä 243, 521
             name, 2 2 20Ó0ë, 430Ñ0ü0Ä 2 2 20Õ0é0ó,        ! ?SO 5 5 55, 2 2,  (T )0Ñ0ü0Ä 5
             439, 2 2 251, 62 (N  )              ISO 8601, 0Ñ0ü0Ä 5
          invalid SQL statement name,    ISO 8652, 0Ñ0ü0Ä 243, 501
                                         ! ?SO 9075, 5 5, 610Ñ0ü0Ä 5 5,
             2 2 249, 450, 2 2 259, 465, 2 2 267,       660Ñ0ü0Ä 5 565
             62 (N  )                        ISOLATION, 84, 2 299, 680
          invalid time +one              isolation level, 68, 69,
             displacement value,            70, 74, 76, 0Õ0é0ó0, 2 299,
             167, 42 (l4 ) 5 5 (eå )                  400, 5 (R´ ), 66 ( )          invalid transaction state,     ! !isolation level>, 0Ø0ë0Ä9
             2 250, 0Ú0Ë0Ò4, 2 286, 0Ú0Ë0Ò9, 2 292,    ! ?S_DEFERRABLE, 541, 549,
             2 294, 400, 2 2 2, 420, 5 (y] ),       550Ñ0ü0Ä 574, 575, 585, 587,
             528, 5 5 (g	 )                       598
          invalid 4ransaction            IS_GRANTABLE, 546, 547,
             4ermination, 400Ñ0ü0Ä 2 2 205,         548, 5 500, 601, 5 502, 600Ñ0ü0Ä
             62 (N  )                           5 504, 605
          <in value list>, 2,  (h* )0Ñ0ü0Ä     ! ?S_NULLABLE, 544, 580, 58 ( )             2 2 244, 446, 5 50Õ0¡0é0Ã0É               ! ?S_UPDATABLE, 543, 578, 579
          ! ?S, 2 26, 84, 142,  (h* )8, 2 (Nã ),     IS_UPDATABLE_CHECK, 578
             20Ô0³,  (Œ¡ )4, 272, 500, 504,    ! ?S_UPDATABLE_NOT_NULL, 578
             50, 508, 5, 517, 5 (eå ),    ! !item number>, 434, 2 2 20Õ0é0ó,
             562, 570, 571, 580, 581,       436, 2 2 20Ú0Ë0Ò, 439

             61 (l4 ) 5 5ª, 618                          - J -
          ! ?SOgEC 1020, 0Ñ0ü0Ä 243, 517     JOIN, 84, 0, 182, 4,
          ! ?SOgEC 1046, 0Ñ0ü0Ä 5,  (T )9          50Ø0ë0Ä, 541, 545, 549, 550,
          ISO/IEC  756, 2 2 2,  (T )0Ñ0ü0Ä 5¬        551, 552, 550Ñ0ü0Ä 557, 558,
          ! ?SOgEC 1539, 2 2,  (T )0Ñ0ü0Ä 5         559, 561, 562, 631, 5 580
          ! ?SOgEC 5 546, 0µ0ó0Á0ü0à                <join column list>, 0,
          ! ?SOgEC 8824, 2 2                   181

                                         join columns, 181,  (l4 ) 183

          0Ú0Ë0Ò  Database Language SQL

  


          <join condition>,  8, 180,    KEY_COLUMN_USAGE view, 55 ( )             181, 0Ñ0ü0Ä 200               KEY_COLUMN_USAGE_FOREIGN_
          ! !joined 4able>, 2 2 25, 1,          KEY_COLUMNS, 588
             1 (eå ), 1, 178, 0, 181,    KEY_COLUMN_USAGE_PRIMARY_
              (l4 ) 184, 1, 196, 8,       KEY, 588
             199,  (eå )0, 201,  (eå ) (l4 ) 5 541,    KEY_COLUMN_USAGE_UNIQUE,
             5 543                            588
          <join specification>, 0,     KEY_DEGREE_GREATER_THAN_OR_
             1                            EQUAL_TO_1, 5 5
          ! !join 4ype>, 0, 181, 0µ0ó0Á0ü0à    KEY_DEGREE_GREATER_THAN_
                      - K -                 OR_EQUAL_TO_1 assertion,
          KEY, 2 26, 2 2 21, 2 2 2 (l4 ) 84, 264,         618
             270,  (y] ) (l4 ) 273,  (y] )4, 275,    known not nullable, 2 26,
             481, 50Ø0¯0¿0ü0ë, 55 (l4 ) 561, 568,       199,  (eå )0, 582

             569, 571, 573, 574, 576,               - L -
             578, 580, 583, 584, 585,    LANGUAGE, 84, 243, 560Ñ0ü0Ä
             586, 587, 588, 590, 591,       5 5, 610Ñ0ü0Ä 5 5, 615, 5 540,
             593, 595, 596, 598, 5 500,       665
             5 502, 604, 5 505, 606, 5 5SA,    ! !language clause>, 46,  (T )0Ñ0ü0Ä
             610, 5 5, 618, 5 540, 645        244, 0Ö0Ã0·0§0ë1, 2 242, 0Ö0Ã0·0§0ë4, 2 246,
          <key 7ord>, ,  (h* ), 82, 83,       0Õ0é0ó (l4 ) 2 257, 0Õ0é0ó8, 2 259, 0Ø0¯0¿0ü0ë0,
             85, 87, 101, 1 (eå ), 427,         2 261, 0Ø0¯0¿0ü0ë (l4 ) 2 263, 0Ø0¯0¿0ü0ë4, 2 265,
             5 50Ó0ë, 641, 5 553, 666             0Ø0¯0¿0ü0ë6, 2 267, 45 (l4 ) 2 2 254, 490Ñ0ü0Ä
          KEY_COLUMN_CONSTRAINT_TYPE_       5 544, 670, 5 571
             CHECK, 588                  <language name>, 243
          KEY_COLUMN_ORDINAL_            LAST, 84, 0Ú0½7, 2 278, 0Ú0½9,
             POSITION_NOT_NULL, 588         5 580
          KEY_COLUMN_TABLE_CATALOG_      LEADING, 84, 10Õ0¡0é0Ã0É, ª7, 5 580
             NOT_NULL, 588               leaf generally 5nderlying
          KEY_COLUMN_TABLE_NAME_NOT_        table, 2 28, 2 272, 0Ú0Ë0Ò7,
             NULL, 588                      2 289, 0Ø0ë0Ä0, 2 292, 0Ø0ë0Ä6, 2 2 274
          KEY_COLUMN_TABLE_SCHEMA_       leaf 5nderlying table, 2 28,
             NOT_NULL, 588                  298, 0Õ0£0ü0È0
          KEY_COLUMN_USAGE, 55 (l4 ) 561,    LEAVE, 85
             588, 5 5, 618, 5 540          LEFT, 84, 0, 182, 0Ñ0ü0Ä
          KEY_COLUMN_USAGE base 4able       50Ø0ë0Ä, 545, 5 580
             , 588                       <left bracket>, 79, 80, 83,
                                            504, 5

                                                            Index  2 29

  


          <left paren>, ­, 79, 80,      levels of conformance, 75
             107, 1SA,  8, 1 (T ), 8,    Lexical elements, 79
             ª (l4 ) 10Õ0£0ü0È, ª9, 141, 4,    LIKE,  (y> ), 84,  (h* )4, 2¬,  (h* )6
             155, ­8, 173, 0, 196,    ! !like 0redicate>, 20Ñ0ü0Ä 205,
             203,  (h* ) (l4 ) 2 (Nã ),  (y> )9, 245,        (h* )4, 2­, 447
             260,  (y] ) (l4 ) 274,  (R´ )1, 296,    LIMIT, 85
              (Nã )7, 2 2, 0Õ0¡0é0Ã0É0, 2 2 (ry ), 0Ö0Ã0·0§0ë6,    <limited collation
             0Ú0Ë0Ò8, 2 290, 489, 2 2 291, 500,       definition>, 0Ó0ë1
                                         literal,  (y> ),  (T )
             508, 5¬, 520               <literal>, 19, 89, 102,
          LENGTH, 83, 0Õ0é0ó6, 2 2 2 (ry ), 426,         4, 1­, 6, 147, 9,
             427, 2 2 20Ö0Ã0·0§0ë, 436, 2 2 20Ø0ë0Ä, 440,       151, ¬ (l4 ) 153, ¬4, 191,
             2 2 241, 45 (l4 ) 2 2 253, 454, 2 2 255,        (Œ¡ )6, 267,  (Œ¡ )8, 2 2 20Õ0¡0é0Ã0É, 430Ñ0ü0Ä
             456, 2 2 257, 660µ0ó0Á0ü0à                 2 2 20Ú0½, 441, 2 2 243, 458, 50Ô0³,
          <length>, 63, 93, 107, 1SA,       629, 5 50Ú0½, 638, 5 540
             109, 2 256, 0Õ0é0ó7, 2 258, 0Õ0é0ó9,    LOCAL, 2 28, 2 2 20, 84, 99, 102,
             2 260, 0Ø0¯0¿0ü0ë1, 2 2 245, 447, 500,       104, 165, ­6, 167,  (Œ¡ )0,
             501, 502, 504, 505, 506,       261,  (Nã )6, 299, 0Ø0ë0Ä7, 2 2 2 (g	 ),
             507, 508, 5SD, 510, 5,       576, 577, 578, 579, 680
             5ª, 515, 5­, 517, 5,    ! !local table name>, 98,
             519, 5 (eå ), 521, 5 (g	 ), 639        103, 0Ø0ë0Ä7, 2 2 286, 487
          <length expression>, 20Ñ0ü0Ä       local 4emporary 4able, 0Ú0½,
             27, 29, 1 (R´ ), 9, 10Ó0ë,         0Ú0Ë0Ò, 0Ø0ë0Ä, 72, 101, 103,
             5 50Ô0³, 641, 5 559                   (T )5, 258,  (Œ¡ )0, 261,  (y] )5,
          LESS, 85                          281,  (R´ )0Ñ0ü0Ä 294, 0Ø0ë0Ä7, 2 298,
          <less than operator>, 80,         459, 2 2 286, 487, 577, 655,
              (eå )7, 2 273, 531                  5 568
          ! !less 4han or equals           LOOP, 85
             operator>, 80Ñ0ü0Ä 207          <low>, 16, 17
          LEVEL, 84, 2 299, 680            LOWER,  (g	 ), 84, ª (l4 ) 10Ø0¯0¿0ü0ë,
          Leveling, 75                      681
          Leveling Rules, 9, 1 (l4 ) 15,     lower case, 2 (l4 ) 81, 87, 88,
             625                            10Õ0é0ó, ª6, 50, 534, 5 540
          Leveling the SQL Language,
             5 5 (Nã )
          ! !level of isolation>, 2 299,
             2 2 200, 66 ( )          <levels clause>, 296,  (Nã )7,
              (Nã )9, 5 50Õ0£0ü0È

          40  Database Language SQL

  


                      - M -              MINUTE, 2 20, 2 21, 2 2 (l4 ) 2 20Ñ0ü0Ä 5 5 50Ñ0ü0Ä
          Maintenance and interpreta-       84, 95, 1,  0Ñ0ü0Ä 1 (y> ),
             4ion of SQL, 685               ª0, 166,  (y> )8, 20Ø0ë0Ä,  (T )0,
          ! !mantissa>, 90, 94, 95,           2 2 2 (g	 ), 430, 2 2 241, 681
             148, ¬0                    ! !minutes value>, 91, 94
          marked modified 0rivilege      mixing of data 4ypes, 0Ö0Ã0·0§0ë
             descriptor, 0Õ0£0ü0È6             modified, 0Õ0£0ü0È5
          MATCH, 2 2 2 (l4 ) 2 2 20Ñ0ü0Ä 84, 2 (T ),        modified privilege
             274,  (y] )6, 280, 0Õ0é0ó0Ñ0ü0Ä 2 254,       descriptor, 0Õ0£0ü0È5
             550, 590, 591, 630Ñ0ü0Ä 5 581     MODIFY, 85
          matching rows, 2 (T ),  (y] )7,       module, 2 28, 2 29, 2 2 25, 2 2 26, 2 2 27,
              (y] )8, 279                       2 2 28, 2 2 29, 55, 56, 5 51, 5 5 (l4 )
          ! !match predicate>,  (eå )5,           5 50Ñ0ü0Ä 5 55, 5 57, 5 5 51, 5 5 5 (l4 ) 5 5 50Ñ0ü0Ä
              (eå )6, 2 (T ),  (g	 )5, 2 (Œ¡ ),  (y] )6,       5 5 54, 5 5 56, 85, 86, 9 (l4 ) 90Ñ0ü0Ä
             447, 5 50Õ0¡0é0Ã0É                       99, 100, 101, 102, 100Ñ0ü0Ä
          ! !match type>, 2 2 2 (l4 ) 271,  (y] )4,       104,  5, 1­,  (ry )6, 260,
             276,  (y] )7, 278, 591              (Œ¡ )1, 297, 0Ô0³ (l4 ) 2 2, 0Ó0ë6,
          ! !match value>,  (h* )4, 2,          2 2 (h* ), 0Õ0¡0é0Ã0É6, 2 241, 0Ö0Ã0·0§0ë (l4 ) 2 243,
             2 2 247, 640µ0ó0Á0ü0à                      0Ö0Ã0·0§0ë4, 2 245, 0Ö0Ã0·0§0ë6, 2 248, 0Ö0Ã0·0§0ë9,
          MATCH_OPTION, 550, 590, 591       2 250, 0Õ0é0ó (l4 ) 2 271, 0Ú0½5, 2 277,
          MAX, 84, 1 (T ), 5, 1 (Œ¡ ),           0Ú0Ë0Ò1, 2 284, 0Ø0ë0Ä1, 2 297, 400Ñ0ü0Ä
             9, 193,  (eå )8, 2 2 20Ó0ë, 539,       2 2 205, 408, 2 2 2SD, 411, 2 2 249,
             544, 570, 571, 57 (l4 ) 5 5­,       450, 2 2 259, 464, 2 2 267, 469,
             660Ñ0ü0Ä 5 570                       2 2 271, 47 (l4 ) 2 2 274, 490, 2 2 293,
          MESSAGE_LENGTH, 83, 480,          495, 2 2 296, 610Ñ0ü0Ä 5 5, 625,
             481, 2 2 288                       5 5 (y] ), 634, 5 546, 647, 5 554,
          MESSAGE_OCTET_LENGTH, 83,         655, 5 556, 657, 5 558, 661,
             480, 2 2 281, 488                  5 562, 668, 5 569, 670, 5 571,
          MESSAGE_TEXT, 83, 480, 2 2 281,
             2 2 288, 660µ0ó0Á0ü0à                      670Ñ0ü0Ä 5 574, 678
          MIN, 84, 1 (T ), 5, 1 (Œ¡ ),        Module, 2 241
             9, 193,  (eå )8, 5 570          MODULE, 0Ø0ë0Ä, 84, 98, 0Ö0Ã0·0§0ë4,
          ! !minus sign>, 80, 80Ñ0ü0Ä 86,         2 297, 486, 2 2 287, 61 (l4 ) 5 5ª,
             90, 91, 157, ¬8, 165,         614

             ­8, 169,  (T )1, 242


                                                            ! ?ndex  41

 
          ! !module>, 2 28, 2 29, 2 2 25, 2 2 26,      <module name clause>, 0Ö0Ã0·0§0ë1,
             47, 48, 49, 51, 55, 56,        2 244, 490ª0ü0à             5 51, 5 5 (l4 ) 5 50Ñ0ü0Ä 5 55, 5 57, 5 5 51,     Modules, 46
             72, 73, 74, 93, 100,        monadic, 24, 95, 10Õ0£0ü0È, ª4,
             101, 103, 104, 1¬,  6,       158
              (ry )6, 260,  (Œ¡ )1, 297, 0Ô0³ (l4 )    monadic operator, 6, 24,
             0Ó0ë (l4 ) 2 2­, 0Õ0¡0é0Ã0É1, 2 2 (Œ¡ ), 0Ö0Ã0·0§0ë1,       10Õ0£0ü0È, ª4
             2 242, 0Ö0Ã0·0§0ë0Ñ0ü0Ä 2 244, 0Ö0Ã0·0§0ë6, 2 248,    MONTH, 0Ô0³, 0Ó0ë, 0Õ0¡0é0Ã0É, 0Õ0£0ü0È, 84,
             2 249, 0Õ0é0ó0, 2 252, 0Ú0½1, 2 275,       95,  1, 1,  0Ñ0ü0Ä 20Ú0Ë0Ò,
             2 277, 0Ú0Ë0Ò1, 2 284, 0Ø0ë0Ä1, 2 297,        (y> )9, 240, 430, 2 2 245, 681
                                         ! !months 6alue>, 91, 94, 241
             400Ñ0ü0Ä 2 2 205, 408, 2 2 2SD, 411,    MORE, 83, 479, 2 2 281, 48 ( )             2 2 249, 450, 2 2 259, 464, 2 2 267,    multiple server 4ransac-
             2 2 269, 471, 2 2 272, 474, 2 2 293,       tions, 2 2 207, 410, 5 5 (h* )
             495, 2 2 296, 614, 5 5 (ry ), 627,    multiset, 6, 5 5 5, 0Ø0¯0¿0ü0ë, 0Ú0½, 0Ú0Ë0Ò,
             5 50Ö0Ã0·0§0ë, 646, 5 554, 655, 5 556,       8, 183, 4, 2 20Õ0¡0é0Ã0É
             657, 5 558, 661, 5 562, 668,    MUMPS, 2 2 2, 61, 83,  (T )0Ñ0ü0Ä 244,
             5 569, 670, 5 571, 670Ñ0ü0Ä 5 574,       0Õ0é0ó9, 2 260, 0Ø0¯0¿0ü0ë5, 2 2 289, 490,
             678                            2 2 291, 490Ñ0ü0Ä 2 2 295, 498, 5¬,
          <module authorization             516, 5 5ª, 614, 5 5 (Œ¡ ), 644,
             clause>, 2 2 25, 2 2 26, 5 5 5 (l4 )           5 564
             101, 102, 0Ö0Ã0·0§0ë1, 2 243, 490Ñ0ü0Ä    <mumps character 6ariable>,
             5 554, 657, 5 569                  515, 5­, 664
          <module authorization          ! !MUMPS host identifier>,
             identifier>, 46, 65,           490, 5¬
              (ry )6, 2 241, 0Ö0Ã0·0§0ë (l4 ) 2 248, 408,    <mumps length specifica-
             656, 5 561, 66 (l4 ) 5 573, 678        4ion>, 515, 5­
          ! !module character set          <mumps numeric 6ariable>,
             specification>, 2 2 26,            515, 5­
                                         <mumps 4ype specification>,
             85, 86, 9 (l4 ) 90Ñ0ü0Ä 100,           515
             2 244, 0Ö0Ã0·0§0ë5, 2 2 293, 647, 5 561     ! !MUMPS variable definition>
          ! !module contents>, 0Ö0Ã0·0§0ë1,           , 2 2 290, 515, 5­
             0Ö0Ã0·0§0ë0Ñ0ü0Ä 5 547
          module language, 46, 75
          ! !module name>, 46, 61, 74,
             99, 103, 0Ö0Ã0·0§0ë4, 2 252, 490Ñ0ü0Ä
             669, 5 573


          2 2 2 (N  ) Database Language SQL

 
                      - N -              <nondoublequote character>,
          n-adic operator, 5 5                82, 86
          NAME, 84, 2 2 2 (y] ), 434, 2 2 20Ú0Ë0Ò,       NONE, 85
             45 (l4 ) 2 2 254, 670µ0ó0Á0ü0à              <non-join query expression>
          <named columns join>, 0,        , 6, 197, 8, 199,
             181, 0Ñ0ü0Ä 184                   (eå )0
          NAMES, 84, 2 244, 419, 2 2 284,      ! !non-join iuery 0rimary>,
             490, 5 581                       196, 7, 198, 9, 5 570
          Names and identifiers, 98      <non-join query term>, 196,
          NATIONAL,  (eå ),  (h* ), 84, 107,        7, 198, 9, 5 570
             108, 5 553, 657, 5 581          non-null,  (g	 )0Ñ0ü0Ä 277
          ! !national character string     non-null 6alue, , 42, 89,
             literal>, 8 (l4 ) 86, 89,           1, 2SA,  (g	 )5, 20Ö0Ã0·0§0ë,  (y] )8,
             92, 93, 97, 640                279, 0Ú0½0Ñ0ü0Ä 50Ó0ë, 66 (l4 ) 5 565
          ! !national character string     <nonquote character>, 83,
             4ype>, 107, 1ª, 640           89, 92
          NATURAL, 84, 0, 181, 0Ñ0ü0Ä    non-repeatable read, 5 58
             184,  (R´ )9, 2 252, 681          ! !non-reserved 7ord>, 83
          NCHAR, 84, 107, 1SA, 681       <non-second datetime field>
          NEW, 85                           ,  (y> )9, 241
          ! !newline>, 83, 86, 92, 656     Normative references, 0ª0ü0à          NEXT, 84, 0Ú0½7, 2 278, 0Ú0½9,       no subclass, 619, 5 5 (eå ), 621,
             469, 5 581                       5 5 (g	 ), 620ª0ü0à          NO,  (h* ), 0Õ0é0ó, 84,  (eå )8, 249,      NOT,  (y> ), 0Ø0¯0¿0ü0ë, 84,  (l4 ) 2 ,
             250,  (y] )4, 276, 0Ó0ë4, 2 2¬,        (h* ) (l4 ) 2,  (h* )8, 2 (R´ ),  (g	 )9,
             590, 591, 59 (l4 ) 5 5SA, 609,       20Ô0³,  (ry ) (l4 ) 253,  (Œ¡ ) (l4 ) 264,
             5 560, 670, 5 581                   (y] )0, 271,  (y] ) (l4 ) 273, 0Ô0³1,
          No collating sequence,  (y> ),        2 203, 0Õ0¡0é0Ã0É5, 2 2 297, 499, 562,
             24, 25, 26, 297                569, 570, 571, 574, 576,
          no data, 47, 0Õ0é0ó0, 2 251, 0Ú0½9,       578, 580, 585, 588, 590,
             2 282, 0Ú0Ë0Ò0Ñ0ü0Ä 2 287, 0Ú0Ë0Ò9, 2 295,       598, 5 500, 60 (l4 ) 5 504, 606,
             435, 2 2 299, 528, 50Ô0³, 62 (l4 )       5 5SA, 610, 5 5, 617, 5 5,
             5 5 (T )                            630Ñ0ü0Ä 5 545
          non-deferrable, 2 26, 2 2 21         Notation, 7
          <nondelimiter token>, 82,      ! !not equals operator>, 83,
             86                              (eå )7
          non-deterministic, 2 2 20, 189,
             193,  (eå )0, 282, 0Õ0¡0é0Ã0É5


                                                            Index  2 2 20ª0ü0à
  


          null, 6, 5 5 5, , 0Ø0¯0¿0ü0ë, 42, 43,    ! !null 0redicate> semantics,
             48,  6, 1 (Œ¡ ), 9, 10Ô0³,        2
             ª1, 10Õ0é0ó, ª6, 10Ú0½,  (l4 )    <null specification>, 0Ñ0ü0Ä
             5, 156, ¬8, 162, ­0Ñ0ü0Ä       174, 0Ø0ë0Ä1
             166, ­9, 173, 4, 182,    null value, 5 5, 7, 19, 2 26,
             0Ñ0ü0Ä 192,  (eå )5, 207,  (h* )5,       2 2 2 (l4 ) 1 (Œ¡ ), 9, 10Ô0³, ª1,
              (h* )8, 2 (T ),  (g	 )5, 2 (R´ ),  (y> )1,       10Õ0é0ó, ª6, 10Ú0½,  (l4 ) 145,
             20Ö0Ã0·0§0ë,  (Œ¡ )7, 268,  (y] )8, 279,       ¬6, 158, ­ (l4 ) 163, ­6,
             0Ú0½0Ñ0ü0Ä 2 291, 42 (l4 ) 2 2 20Ø0¯0¿0ü0ë, 444,       169, 4, 183,  (eå )7, 2¬,
             2 2 252, 454, 2 2 256, 458, 50,        (h* )8, 2 (T ),  (g	 )5, 2 (R´ ),  (y> )1,
             525, 50Ó0ë, 570Ñ0ü0Ä 579, 581,       20Ö0Ã0·0§0ë,  (Œ¡ )7, 268,  (y] )8, 279,
             594, 614, 5 544, 66 (l4 ) 5 565,       435, 2 2 20Ø0¯0¿0ü0ë, 454, 2 2 256, 458,
             668, 5 571, 674                  5 (ry ), 579, 594, 614, 5 562,
          NULL, , 0Ø0¯0¿0ü0ë, 84, 1, 142,       665, 5 568, 671, 5 574
             4, 145, 0Ñ0ü0Ä 192,  (h* )8,    null 6alue, no indicator
              (Œ¡ ) (l4 ) 264,  (Œ¡ )6, 267,  (y] ) (l4 )       0arameter,  (y> )1, 2 2 20Õ0é0ó, 620
             273,  (y] )4, 278,  (y] )9, 543,    null value eliminated in
             544, 56 (l4 ) 569, 570, 571,       set function, 6, 5 5 (y> )
             574, 576, 578, 580, 581,    number,  (y] )
                                         NUMBER, 84, 479, 2 2 281, 48 ( )             585, 588, 590, 591, 592,    ! !number of conditions>,
             598, 5 500, 60 (l4 ) 5 504, 606,       2 299, 400, 5 572
             608, 5 510, 61 (l4 ) 5 5ª, 618,    Numbers, 27
             5 545                         NUMBER_OF_CHARACTERS, 554,
          nullability, 2 26, 265              606, 5 507, 665
          nullability characteristic,    NUMERIC, ,  (y] ), 0Ö0Ã0·0§0ë, 84,
             2 26, 2 27, 265                    107, 1SD,  0, 2 253, 0Õ0é0ó8,
          nullable, 2 2 2 (l4 ) 2 2 27, 182,  (l4 )       2 2 2 (ry ), 426, 2 2 2 (Nã ), 440, 2 2 245,
             199,  (eå )0, 2 2 252, 58 (N  )            510, 50Ø0ë0Ä, 544, 565, 570,
          NULLABLE, 84, 2 2 2 (y] ), 434,           571, 57 (l4 ) 5 558
             436, 2 2 20Ú0Ë0Ò, 45 (l4 ) 2 2 253, 454,    numeric data 4ype
             544, 580, 582                  descriptor,  (y] )
          null character, 2 263, 506,      <numeric 0rimary>, 157, ¬8
             5 561                         ! !numeric type>, 107
          NULLIF, 84, 141,  (l4 ) 2 2 244,     <numeric 6alue expression>,
             2 2 246, 681                       ª0Ñ0ü0Ä 155, ¬7, 158
          ! !null 0redicate>, 205,  (h* )8,    <numeric 6alue function>,
             2 2 244                            8, 10Ó0ë, ¬7, 5 50Ô0³, 641


          44  Database Language SQL

  


          numeric value out of range,    octet, 0Ñ0ü0Ä 5,  (g	 ),  (y> ),  (y] ),
             1 (Œ¡ ), 6, 147, ¬8, 20Õ0£0ü0È,       10 (l4 ) 103, 8, 10Ó0ë,  (ry )0,
              (y> )5, 5 5 (eå )                       2 256, 0Õ0é0ó7, 2 258, 0Õ0é0ó9, 2 260,
          NUMERIC_PRECISION, 50Ø0ë0Ä,           0Ø0¯0¿0ü0ë1, 2 262, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 264, 0Ø0¯0¿0ü0ë5,
             544, 565, 570, 571, 57 (N  )       2 266, 0Ø0¯0¿0ü0ë7, 2 2 20Ø0¯0¿0ü0ë, 45 (l4 ) 2 2 253,
          NUMERIC_PRECISION_RADIX,          454, 2 2 258, 488, 501, 506,
             539, 544, 565, 570, 571,       5SD, 510Ñ0ü0Ä 5, 521, 572,
             572                            619
          NUMERIC_SCALE, 50Ø0ë0Ä, 544,       ! !octet length expression>,
             570, 571, 572                  8, 10Ó0ë

                      - O -              OCTET_LENGTH, 80Ñ0ü0Ä 84, 1 (R´ ),
          OBJECT, 85                        ª0, 2 2 2 (y] ), 434, 2 2 20Ø0¯0¿0ü0ë, 438,
          ! !object column>, 0Ø0ë0Ä1, 2 292,        2 2 245, 45 (l4 ) 2 2 253, 454, 2 2 258,
             2 293, 0Ø0ë0Ä4, 2 295, 0Ø0ë0Ä6, 2 2 247,       488, 50Ø0ë0Ä, 544, 570, 571,
             474, 2 2 275, 648                  572, 681
          object identifier, 16, 5 5 (ry )     OF, 84, 2 260, 0Ø0¯0¿0ü0ë1, 2 271, 0Ú0Ë0Ò4,
          Object identifier for             2 291, 47 (l4 ) 2 2 274, 476, 2 2 277,
             Database Language SQL,         517, 5, 519, 5 50Ø0ë0Ä
             ­                          OFF, 85
          <object name>, 245,  (T )6,       OID, 85
             0Õ0¡0é0Ã0É9, 2 20Õ0¡0é0Ã0É, 0Õ0£0ü0È0Ñ0ü0Ä 5 50Ö0Ã0·0§0ë, 646     OLD, 85
          OBJECT_CATALOG, 539, 548,      ON, 84, 180,  (T )8, 260,  (y] )4,
             554, 555, 556, 5 504, 605        275,  (R´ )1, 289,  (Nã )4, 2 200,
          OBJECT_NAME, 50Ø0ë0Ä, 548, 554,       0Ó0ë0, 2 2ª, 0Ó0ë5, 2 2, 0Õ0¡0é0Ã0É1,
             555, 556, 604, 5 505             2 2 (y> ), 0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0¡0é0Ã0É,
          OBJECT_SCHEMA, 50Ø0ë0Ä, 548,          0Õ0£0ü0È0Ñ0ü0Ä 2 297, 400Ñ0ü0Ä 50Ø0ë0Ä, 541,
             554, 555, 556, 5 504, 605        545, 549, 550, 551, 552,
          OBJECT_TYPE, 50Ø0ë0Ä, 548, 554,       550Ñ0ü0Ä 557, 558, 559, 561,
             555, 556, 604, 5 505             562
          ! !occurrences>, 431, 2 2 20Õ0¡0é0Ã0É,       ONLY, 84, 0Ú0½1, 2 272, 0Ø0ë0Ä9,
             435, 2 2 20Ø0ë0Ä, 451, 2 2 253, 455,       2 2 200, 681
             2 2 257, 637, 5 563               OPEN, 84, 2 275, 467, 2 2 283,

                                            2 2 284


                                                            Index  2 2 25

  


          <open statement>, 50, 53,      OPTION, 2 2 20, 5 55, 5 5 55, 84,
             55, 57, 58, 59, 0Ö0Ã0·0§0ë (l4 )           248,  (Nã )6, 297,  (Nã )9, 2 2 (Nã ),
             2 268, 0Ú0½1, 2 275, 464, 2 2 265,       0Õ0£0ü0È0, 2 20Ó0ë, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Õ0é0ó, 0Õ0£0ü0È6,
             484, 2 2 293, 494, 2 2 295, 496,       2 20Ú0½, 0Õ0é0ó6, 2 289, 0Ø0ë0Ä0Ñ0ü0Ä 2 295,
             5 573                            487, 50Õ0£0ü0È, 540Ñ0ü0Ä 550, 578,
          OPERATION, 85                     579, 590, 591, 601, 5 503,
          Operations involving bit          605, 5 577
             strings, 27                 OR, 0Ø0¯0¿0ü0ë, 84,  (g	 )8, 2 (Nã ),  (y> )0,
          Operations involving              50Ø0ë0Ä, 546, 547, 548, 571,
             character strings,  (g	 )          570Ñ0ü0Ä 580, 581, 583, 584,
          Operations involving              585, 586, 591, 595, 596,
             datetimes and intervals,       606, 5 5SA, 611, 5 5, 610ª0ü0à             2 24                          ORDER, 84, 0Ú0½1, 2 272, 0Ú0½4,
          Operations involving              2 2 264, 530, 5 50Õ0é0ó, 638
             numbers,  (Nã )                 ! !order by clause>, 50, 0Ú0½1,
          operator, 5 5, 7, 8, , ª,        2 272, 0Ú0½0Ñ0ü0Ä 2 291, 474, 50Ô0³,
             2 (l4 ) 20Ñ0ü0Ä 24, 27, 29, 2 24,        531, 5 568, 671, 5 574
             0Õ0é0ó, 80, 83, 95, ª0Ñ0ü0Ä        <ordering specification>,
             10Ö0Ã0·0§0ë, ¬7, 158, ­0, 161,       0Ú0½1
             166, ­9, 170, 7, 198,    ORDINAL_POSITION, 544, 55 (l4 )
              (eå )0, 201,  (eå ) (l4 ) 207,  (eå )8,       580, 581, 588, 589
             2 (Nã ),  (y> )7, 2 273, 0Ø0ë0Ä1, 2 2 20Ö0Ã0·0§0ë,    Other operators involving
             438, 2 2 243, 445, 2 2 279, 500,       bit strings,  (y] )
             505, 50Ó0ë, 659, 5 570          Other operators involving
          OPERATORS, 85                     character strings, 20ª0ü0à          Operators that operate on      OTHERS, 85
             bit strings and return      Other 4erms, 
             bit strings, 27             OUTER, 84, 180, 618, 5 581
          Operators 4hat operate         <outer join type>, 180
             on character strings        outermost, 11, 1
             and return character        outer reference, 1 (g	 ), 4,
             strings, 2 (N  )                   1 (Œ¡ ), 1, 185, 9, 190,
                                             (l4 ) 194, 0Ú0Ë0Ò6, 2 295, 641,
                                            5 578
                                         OUTPUT, 84, 450, 5 581
                                         output 0arameter, 0Ö0Ã0·0§0ë7, 2 248,
                                            0Õ0é0ó7, 2 262, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 264, 0Ø0¯0¿0ü0ë5,
                                            2 266, 0Ø0¯0¿0ü0ë7, 5 561


          2 2 26  Database Language SQL

 
          OVERLAPS, 2 24, 84, 2 (y] ), 681     <parameter declaration
          ! !overlaps 0redicate>, 2 24,         list>, 0Ö0Ã0·0§0ë6
             205,  (eå )6, 2 (y] ),  (g	 )8, 2 2 244,    ! !parameter name>, 5 5 55, 99,
             446, 5 543, 644                  103,  4, 1¬,  6, 2 246,
                      - P -                 0Ö0Ã0·0§0ë7, 2 250, 0Ú0½1, 2 2 294, 670Ñ0ü0Ä
          ! !89 0ackage>, 16, 17            5 577
          PAD,  (h* ), 0Õ0é0ó, 85,  (eå )8, 249,     Parameters, 47
              (ry )0, 2 2, 0Ó0ë5, 5 5SA, 609,    PARAMETERS, 85
             660, 5 570, 681               <parameter specification>,
          ! !pad attribute>, 0Ó0ë4, 2 2¬         1,  5, 1­, 525
          PAD_ATTRIBUTE, 555, 608,       ! !parameter using clause>,
             609, 5 565                       2 2 255, 459, 2 2 260
          0arameter,  (R´ ),  (Nã ), 47, 48,     PARTIAL, 2 2 2 (l4 ) 2 2 20Ñ0ü0Ä 85, 2 (T ),
             5 51, 5 5 (l4 ) 5 50Ñ0ü0Ä 5 5 50, 5 5 55, 99,         (g	 )5, 274,  (y] )6, 277,  (y] )8,
             100Ñ0ü0Ä 1,  5, 1­, ­8,       279, 590, 591, 681
             192,  (y> )1, 281,  (Nã )6, 2 2 (ry ),    Pascal, 2 2, 49, 61, 0Ø0¯0¿0ü0ë0,
             0Ö0Ã0·0§0ë6, 2 247, 0Ö0Ã0·0§0ë8, 2 250, 0Õ0é0ó1,       2 261, 0Ø0¯0¿0ü0ë6, 2 2 289, 490, 2 2 291,
             2 252, 0Õ0é0ó6, 2 257, 0Õ0é0ó8, 2 259,       490Ñ0ü0Ä 2 2 295, 498, 5, 518,
             0Ø0¯0¿0ü0ë0, 2 261, 0Ø0¯0¿0ü0ë (l4 ) 2 263, 0Ø0¯0¿0ü0ë4,       5, 615, 5 5 (Œ¡ ), 639, 5 551,
             2 265, 0Ø0¯0¿0ü0ë6, 2 267, 0Ú0½1, 2 2 20Õ0é0ó,       66 ( )                                         PASCAL, 84, 243, 0Ø0¯0¿0ü0ë0, 2 266,
             2 2 20Ø0¯0¿0ü0ë, 439, 2 2 243, 450, 2 2 253,       490Ñ0ü0Ä 5, 61 (l4 ) 5 5ª, 614,
             454, 2 2 255, 456, 2 2 259, 460,       5 5¬
             46 (l4 ) 2 2 267, 48 (l4 ) 2 2 286, 494,    <pascal host identifier>,
             2 2 295, 496, 502, 507, 510,       490, 5, 518
             5, 516, 5, 52 (l4 ) 5 (ry ),    ! !Pascal 4ype specification>
             619, 5 5 (T ), 630, 5 50Õ0é0ó, 641,       , 5, 518, 5, 639,
             647, 5 554, 659, 5 561, 66 (l4 )       5 551
             664, 5 565, 666, 5 571, 67 (l4 )    <pascal variable
             670Ñ0ü0Ä 5 574, 675, 5 577             definition>, 490, 5,
          <parameter declaration>,          518, 5
             47, 0Ö0Ã0·0§0ë6, 2 247, 0Õ0é0ó0, 2 251,     <pattern>, 2,  (h* )7, 2 2 247,
             2 252, 0Õ0é0ó6, 2 257, 0Õ0é0ó8, 2 259,       640ª0ü0à             2 260, 0Ø0¯0¿0ü0ë1, 2 262, 0Ú0½1, 2 2 294,    PENDANT, 85
             495, 2 2 296, 635, 5 547, 674,    <percent>, 5 5 59, 80, 2¬
                                         <period>, 80, 90, 91, 94,
             5 575                            98, 99, 1, 148, ¬0,

                                            1, 242, 508

                                                            ! ?ndex  47

 
          0ersist, 0Ú0½, 0Ø0ë0Ä, 44, 51,       possibly non-deterministic,
             5 (l4 ) 5 57, 5 5 5 (l4 ) 258,  (Œ¡ )0,          40, 9, 193,  (eå )0, 282,
             261,  (y] )5, 281, 0Ø0ë0Ä7, 2 298,       0Õ0¡0é0Ã0É5
             577                         0ossibly nullable, 0Ø0¯0¿0ü0ë,  (l4 )
          0ersistent, 5 5 5, 0Ú0½, 0Ø0ë0Ä, 44,        192, 45 (l4 ) 582
             46, 51, 52, 67,  (ry )8,        precede, 1 (l4 ) 242,  (Nã )7, 2 241,
             260,  (Œ¡ )1, 275,  (R´ )1, 2 297,       0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 273, 400Ñ0ü0Ä 2 2 292, 490Ñ0ü0Ä
             577                            505, 509, 5, 521, 50Ó0ë,
          persistent base table, 2 27         667
          persistent 4able, 44           PRECISION, ,  (y] ), 0Ö0Ã0·0§0ë, 85,
          phantom, 5 58                       108, 110, 0Õ0é0ó (l4 ) 2 257, 0Õ0é0ó8,
          ! !PLg host identifier>,           2 259, 425, 2 2 2 (Œ¡ ), 427, 2 2 2 (Nã ),
             2 2 290, 520, 5 (h* )                  434, 2 2 20Ø0¯0¿0ü0ë, 439, 2 2 240, 441,
          ! !PLg 4ype fixed binary>,         2 2 253, 454, 2 2 255, 456, 2 2 257,
             5 (eå )                            500, 502, 507, 5, 510Ñ0ü0Ä
          ! !PLg 4ype fixed decimal>,        50Ø0ë0Ä, 544, 565, 570, 571,
             5 (eå )                            57 (l4 ) 5 558, 660ª0ü0à          <pl/i type float binary>,      ! !precision>, 63, 107, 1SA,
             5 (eå )                            109, 110, 0Õ0é0ó8, 2 261, 445,
          ! !PLg 4ype specification>,
             5 (eå ), 521, 5 (g	 ), 520Ñ0ü0Ä 5 50Ø0ë0Ä,       515, 5­, 520, 5 (g	 ), 657,
             651, 5 564, 665                  5 558
          ! !PLg 6ariable definition>,    <predicate>, 205,  (eå )6, 2­,
             2 2 290, 520, 5 (h* ), 52 (l4 ) 5 564         (g	 )9, 5 50Õ0¡0é0Ã0É
          PLI, 84,  (T )0Ñ0ü0Ä 2 255, 0Ø0¯0¿0ü0ë1,        Predicates,  (eå )5
             2 267, 490Ñ0ü0Ä 5 5, 610Ñ0ü0Ä 5 5,    PREORDER, 85
             5 5¬                         Preparable and immediately
          <plus sign>, 80, 90, 157,         executable SQL-
             158, ­5, 168                  statements, 56
          POSITION, 85, 1 (R´ ), 445,        <preparable dynamic delete
             544, 552, 580, 581, 588,       statement: positioned>,
             589, 5 581                       50Ñ0ü0Ä 56, 59, 5 50, 5 5 (l4 ) 2 2 242,
          <position expression>, 20Ñ0ü0Ä        440Ñ0ü0Ä 2 2 260, 46 (l4 ) 2 2 263, 476,
              (y] ),  (Nã ), 8, 1 (Nã ), ª0,         2 2 284, 638

             ª1, 2 2 244, 630, 5 559
          0ossible qualifiers, 1


          2 2 28  Database Language SQL

 
          ! !preparable dynamic 5pdate     PRIMARY, 2 26, 2 2 21, 2 2 2 (l4 ) 85,
             statement: 0ositioned>,        270,  (y] ) (l4 ) 273,  (y] )5, 50Ø0¯0¿0ü0ë,
             54, 56, 59, 5 50, 5 5 (l4 ) 299,       568, 569, 571, 573, 574,
             44 (l4 ) 2 2 243, 460, 2 2 262, 460Ñ0ü0Ä       576, 578, 580, 580Ñ0ü0Ä 584,
             2 2 277, 484, 5 50Ø0ë0Ä                  585, 586, 587, 588, 590,
          ! !preparable implementation-       591, 590Ñ0ü0Ä 595, 596, 598,
             defined statement>, 56,        600, 5 502, 604, 5 50, 608,
             44 (l4 ) 2 2 243, 660µ0ó0Á0ü0à                 5 510, 618, 5 545
          ! !preparable SQL data           PRIOR, 85, 2 277, 0Ú0½8, 2 279,
             statement>, 2 2 242, 637           681
          <preparable SQL schema         PRIVATE, 85
             statement>, 44 (l4 ) 5 50Ú0½        privilege, 2 2 24, 5 54, 5 55, 5 56,
          ! !preparable SQL session           5 5 55, 5 5 57, 103,  9, 1 (g	 ),
             statement>, 2 2 242, 637           ª5, 145,  (y> )4, 245,  (T )6,
          0reparable SQL-statement,         248,  (T )9, 251,  (ry )6, 261,
             56, 57                          (Œ¡ )4, 276,  (R´ ) (l4 ) 284,  (Nã )8,
          ! !preparable SQL 4ransaction       2 202, 0Ó0ë0, 2 2, 0Ó0ë5, 2 2­,
             statement>, 2 2 242, 637           0Õ0¡0é0Ã0É1, 2 2 (Œ¡ ), 0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1,
          ! !preparable statement>,           2 20Õ0¡0é0Ã0É, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5, 2 20Ø0¯0¿0ü0ë,
             2 2 24, 2 2 25, 5 54, 5 5 50Ñ0ü0Ä 90Ñ0ü0Ä 100,       0Õ0£0ü0È7, 2 20Ú0Ë0Ò, 0Ö0Ã0·0§0ë (l4 ) 2 284, 0Ú0Ë0Ò6,
             101, 1¬, 415, 2 2 2, 419,       2 289, 0Ø0ë0Ä (l4 ) 2 294, 0Ø0ë0Ä8, 2 2 2 (eå ),
             2 2 242, 440Ñ0ü0Ä 2 2 260, 46 (l4 ) 2 2 263,       487, 5 (Œ¡ ), 530Ñ0ü0Ä 546, 547,
             650Ñ0ü0Ä 5 554, 656                  548, 568, 5 500, 601, 5 502,
          PREPARE, 85, 2 254, 44 (l4 ) 2 2 247,
             2 2 249, 46 (l4 ) 2 2 283, 484, 5 581        600Ñ0ü0Ä 5 504, 605, 5 50Õ0¡0é0Ã0É, 630Ñ0ü0Ä
          0repared statement not a          5 555, 660, 5 569, 677, 5 578
             cursor specification,       <privilege column list>,
             465, 5 5 (h* )                       245,  (T )6, 2 20Õ0£0ü0È, 63 ( )          <prepare statement>, 14,       0rivilege dependency graph,
             44, 45, 54, 60, 61, 63,        2 20Õ0é0ó
             64, 73, 93, 101, 103,       privilege descriptor, 44,
             104,  5, 2 269, 415, 2 2 2,       65, 66,  (T )6, 248,  (Œ¡ )1,
             419, 2 2 242, 449, 2 2 250, 459,       284,  (Nã )8, 2 202, 0Ó0ë (l4 ) 2 2¬,
             2 2 264, 465, 2 2 284, 650Ñ0ü0Ä 5 554,       0Ó0ë6, 2 2 (h* ), 0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1,
             656                            2 20Õ0¡0é0Ã0É, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5, 2 20Ø0¯0¿0ü0ë,
          PRESERVE, 85,  (Œ¡ )0, 281,           0Õ0£0ü0È7, 2 20Ú0Ë0Ò, 0Ø0ë0Ä8, 2 2 2 (eå ), 600,
             0Ø0ë0Ä7, 5 581                       5 502, 604


                                                            ! ?ndex  49

 
          0rivilege not granted, 0Õ0£0ü0È (l4 )    PUBLIC, 66, 75, 85, 10 (l4 )
             620µ0ó0Á0ü0à                           245,  (T )6, 248, 0Ó0ë5, 2 2 (h* ),
          privilege not revoked, 2 20Ú0Ë0Ò,       0Õ0£0ü0È4, 50Õ0£0ü0È, 539, 542, 545,
             620µ0ó0Á0ü0à                           546, 547, 548, 554, 555,
          Privileges, 64                    556, 5 501, 600Ñ0ü0Ä 5 505
          PRIVILEGES, 85, 245,  (T )6,
              (Nã )4, 2 200, 0Õ0£0ü0È (l4 ) 2 20Ú0Ë0Ò, 539,               - Q -
             54 (l4 ) 545, 546, 547, 548,    <qualified identifier>, 98,
             554, 555, 556, 600, 5 502,       10 (l4 ) 1,  (ry ) (l4 ) 2 2 (ry ), 486,
             604, 5 505, 640                  2 2 287
          ! !privileges>, 245, 0Õ0¡0é0Ã0É9,        <qualified join>, 0, 181
             0Õ0£0ü0È0, 2 20Ó0ë, 0Õ0£0ü0È (l4 ) 2 20Õ0£0ü0È, 0Õ0£0ü0È8,    <qualified local 4able
             0Ú0Ë0Ò9                            name>, 98, 101, 104, 0Ø0ë0Ä7
          PRIVILEGE_TYPE, 546, 547,      ! !qualified name>, 2 29, 2 2 24,
             548, 5 500, 601, 5 502, 600µ0ó0Á0ü0à       5 5 50Ñ0ü0Ä 98, 99, 101, 10 (l4 )
          0rocedure, 47                     2 2 2, 656
          PROCEDURE, 85, 2 246             ! !qualifier>, 1, 1 (ry ), 1,
          ! !procedure>, , 0Ø0ë0Ä, 46,          2 290, 640ª0ü0à             2 2 27, 2 2 28, 2 2 29, 55, 56, 5 51,     ! !quantified comparison
             5 50Ñ0ü0Ä 5 55, 5 57, 5 5 51, 5 5 5 (l4 ) 5 5 54,        predicate>,  (eå )5, 2 (eå ),
             103,  (ry )6, 2 241, 0Ö0Ã0·0§0ë (l4 ) 2 246,       447
             2 247, 0Ö0Ã0·0§0ë8, 2 249, 0Õ0é0ó0, 2 252,    ! !quantifier>, 2 (eå ),  (g	 )1
             2 271, 0Ø0ë0Ä7, 2 2 2SA, 409, 2 2 2 ,    ! !query expression>, 11,
             410Ñ0ü0Ä 2 2 260, 460Ñ0ü0Ä 2 2 293, 494,       15, 2 27, 2 28, 2 2 20, 5 5 55, 1,
             2 2 295, 496, 5 (y] ), 528, 5 5 (y] ),       0Ñ0ü0Ä 176, 0Ñ0ü0Ä 196, 7,
             655, 5 561, 66 (l4 ) 5 570, 671,       200,  (eå ) (l4 ) 203,  (eå )4, 20Ú0½,
             5 573, 674, 5 575                   (R´ ) (l4 ) 284,  (R´ )9, 294,  (Nã )6,
          ! !procedure name>, 2 2 27, 5 51,         297,  (Nã )8, 299, 0Ô0³0, 2 2SD,
             99, 103, 0Ö0Ã0·0§0ë6, 2 248, 0Õ0é0ó (l4 )        0Ó0ë0Ñ0ü0Ä 2 2, 0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (ry ), 0Õ0£0ü0È0,
             490Ñ0ü0Ä 2 2 294, 661, 5 571, 670µ0ó0Á0ü0à       2 20Ó0ë, 0Õ0£0ü0È4, 2 20Õ0é0ó, 0Õ0£0ü0È6, 2 271,
          Procedures, 47                    0Ú0½ (l4 ) 2 275, 0Ú0Ë0Ò7, 2 288, 0Ú0Ë0Ò9,
          Processing methods, 5 5 (y] )           2 290, 0Ø0ë0Ä (l4 ) 2 296, 444, 2 2 246,
          programming languages, 2 2 29,        467, 2 2 274, 530, 579, 581,
              (T )0µ0ó0Á0ü0à                           583, 584, 5 50Ó0ë, 63 (l4 ) 5 50Ø0¯0¿0ü0ë,
          PROTECTED, 85                     64 (l4 ) 5 543, 646, 5 548, 671,

                                            677
                                         Query expressions, 0ª0ü0à

          50  Database Language SQL

  


          query expression 4oo long      RECURSIVE, 85
             for information schema,     redundant duplicates, 7
             299, 620µ0ó0Á0ü0à                   REF, 85
          ! !query primary>, 6, 198,     <reference column list>,
             640µ0ó0Á0ü0à                           274,  (y] )5, 280,  (R´ )9
          <query specification>, 2 2 20,     referenced columns, 2 2 2 (l4 )
             10 (l4 ) 1, 1, 192, 0Ñ0ü0Ä       271,  (y] )5, 276,  (Nã ) (l4 ) 2 20Ø0¯0¿0ü0ë,
             194, 5, 196, 7, 200,       0Õ0£0ü0È7
             203,  (eå )4, 282,  (Nã )6, 299,    referenced table, 2 2 2 (l4 ) 2 2 20Ñ0ü0Ä
             0Õ0¡0é0Ã0É5, 2 282, 0Ú0Ë0Ò4, 2 290, 0Ø0ë0Ä1,       271,  (y] )4, 275,  (y] )6, 277,
             2 2 242, 460, 2 2 272, 474, 5 50Ó0ë,        (y] )8, 279,  (R´ )0, 289,  (Nã ) ( )             5 50Õ0¡0é0Ã0É, 640Ñ0ü0Ä 5 546, 648, 5 570     ! !referenced 4able and
          ! !query term>, 196, 9,           columns>, 2 2 2 (l4 ) 271,  (y] )4,
              (eå ) (l4 ) 5 543                       275,  (y] )6, 289
          ! !question mark>, 63, 80,       Reference Model of Data
             1                            Management, 1
          <quote>, 5 5 59, 80, 80Ñ0ü0Ä 87,       REFERENCES, 5 55, 5 56, 85,
             89, 90, 91, 92, 93, 97,        245,  (T )6, 261,  (y] )4, 276,
             2 2, 0Õ0¡0é0Ã0É0                        (R´ ) (l4 ) 284,  (R´ )9, 298, 0Ô0³ (l4 )
          ! !quote symbol>, 87, 89, 90µ0ó0Á0ü0à       2 2 (Œ¡ ), 0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0¡0é0Ã0É,
                      - R -                 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ø0¯0¿0ü0ë, 0Õ0£0ü0È7, 2 298, 569,
          READ, 5 58, 5 59, 85, 2 271, 0Ú0½ (l4 )       571, 570Ñ0ü0Ä 574, 576, 580,
             2 299, 400, 5 581                  580Ñ0ü0Ä 584, 585, 588, 591,
          read-only, 0Ú0Ë0Ò, 40, 50, 67,        595, 596, 598, 600, 5 501,
             5 5 50, 182,  (Nã )6, 2 250, 0Ú0½ (l4 )        60 (l4 ) 5 503, 604, 5 505, 606,
             0Ú0Ë0Ò4, 2 286, 0Ú0Ë0Ò8, 2 289, 0Ø0ë0Ä (l4 )       5 5SA, 610, 5 5 , 630ª0ü0à             2 294, 400, 5 (R´ )               ! !references specification>,
          READ ONLY, 0Ú0½ (l4 ) 2 2 200               262,  (Œ¡ )4, 274,  (R´ )0, 5 50Õ0£0ü0È
          read-write, 5 57, 5 5 50, 2 250,       REFERENCING, 85
             2 2 200, 528                    referencing columns, 42,
          READ 2 2 2 2RITE, 0Ø0ë0Ä9, 2 2 200               (y] )1, 274,  (y] )5, 276, 588
          REAL, ,  (y] ), 0Ö0Ã0·0§0ë, 85, 108,     ! !referencing columns>, 42,
             110, 0Õ0é0ó (l4 ) 2 257, 0Õ0é0ó8, 2 259,        (y] )1, 274,  (y] )5, 276
             0Ø0¯0¿0ü0ë0, 2 261, 0Ø0¯0¿0ü0ë6, 2 2 2 (ry ), 426,    referencing table, 2 2 2 (l4 ) 2 2 20Ñ0ü0Ä
             429, 2 2 240, 500, 502, 507,       274,  (y] )5, 276,  (y] )7
             5, 510Ñ0ü0Ä 5¬, 516, 5,    ! !referential action>, 274,
             5, 571, 5 557, 658              (y] )6, 278,  (y] )9, 591, 59 ( )


                                                            ! ?ndex  51

 
          referential constraint, 2 2 21,    Remote Database Access, 0Ñ0ü0Ä
             42                             5 5 (g	 )
          ! !referential constraint        REPEATABLE, 68, 69, 84, 0Ø0ë0Ä9
             definition>, 42, 45,        repertoire, 5, 7, 20, 21,
              (y] )0, 271,  (y] )4, 276,  (R´ )0,       20Ñ0ü0Ä 24, 2 25, 2 2 26, 5 5 54, 5 5 56,
             645                            85, 86, 9 (l4 ) 90Ñ0ü0Ä 100,
          <referential 4riggered            109, 1 , 9, 10Õ0£0ü0È, ª4,
             action>, 265,  (y] )4, 280,        10Õ0é0ó, ª6, 145, 7, 148,
             5 50Õ0£0ü0È, 645                       9, 150, ¬1, 160,  (eå )8,
          REFERENTIAL_CONSTRAINTS,          20Ú0½,  (T )8, 249,  (ry )0, 266,
             550, 559, 586, 590, 5 5,       0Ó0ë1, 2 2, 0Ó0ë5, 2 2­, 506,
             640                            5 507, 660, 5 569, 674
          REFERENTIAL_CONSTRAINTS        REPLACE, 85
             base 4able, 590             requires, 6, 2 2 2 (l4 ) 5 5 51, 583
          REFERENTIAL_CONSTRAINTS        reserved, 61, 73, 83, 84,
             6iew, 550                      85, 87, 100, 2 2 2SA, 411,
          REFERENTIAL_CONSTRAINTS_          2 2 248, 466, 5 5, 626, 5 555,
             CONSTRAINT_TYPE_CHECK,         678
             590                         ! !reserved 7ord>, 83, 84,
          REFERENTIAL_CONSTRAINTS_          85, 87, 100, 5 5 (Œ¡ ), 678
             PRIMARY_KEY, 590            RESIGNAL, 85
          REFERENTIAL_DELETE_RULE_       RESTRICT, 85, 258,  (R´ )9,
             CHECK, 590                     292,  (Nã )4, 2 200, 0Ô0³9, 2 20Ú0½,
          REFERENTIAL_DELETE_RULE_          0Õ0é0ó4, 5 581
             NOT_NULL, 590               restricted data type
          REFERENTIAL_MATCH_OPTION_         attribute 6iolation,
             CHECK, 590                     456, 2 2 258, 621
          REFERENTIAL_MATCH_OPTION_      ! !result>, 141,  (l4 ) 143
             NOT_NULL, 590               <result expression>, 141,
          REFERENTIAL_UPDATE_RULE_           ( )             CHECK, 590                  ! !result 5sing clause>, 451,
          REFERENTIAL_UPDATE_RULE_          2 2 256, 457, 2 2 259, 460, 5 50Ú0Ë0Ò
             NOT_NULL, 590               Retrieval assignment,  (y> )1
          <regular identifier>, 82,      RETURN, 85
             86, 87, 88, 98, 50Õ0£0ü0È,        RETURNED_LENGTH, 84, 427,
             534, 5 5 (Nã )                       2 2 20Ö0Ã0·0§0ë, 436, 2 2 20Ú0Ë0Ò, 458
          RELATIVE, 85, 0Ú0½7, 2 278,        RETURNED_OCTET_LENGTH, 84,
             2 279, 681                       427, 2 2 20Ö0Ã0·0§0ë, 436, 2 2 20Ú0Ë0Ò, 458


          52  Database Language SQL

  


          RETURNED_SQLSTATE, 84, 2 2 279,    ! !row value constructor  (ŒÇ ),
             2 2 281, 485, 2 2 286, 487, 2 2 288         (g	 )7, 2 (R´ )
          RETURNS, 85                    <row 6alue constructor>,
          REVOKE, 85, 289,  (Nã )4, 2 200,        2 26, 156, 0Ñ0ü0Ä 174, 5,
             0Ó0ë0, 2 2ª, 0Ó0ë8, 2 2 (y> ), 0Õ0£0ü0È0Ñ0ü0Ä       176,  (eå )7, 2 ,  (h* ) (l4 ) 2,
             2 255, 484, 5 581                   (h* )9, 2 (eå ),  (g	 )4, 2 (y] ), 0Ø0ë0Ä0,
          ! !revoke statement>, 5 (l4 )           2 2 244, 446, 2 2 247, 631, 5 542,
             245,  (R´ )9, 294, 0Ô0³0, 2 210,       644, 5 548, 669
             2 2ª, 0Ó0ë8, 2 2 (y> ), 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ø0ë0Ä,    ! !row value constructor
             2 268, 484, 5 546                  element>, 0Ñ0ü0Ä 174, 5,
          RIGHT, 85, 0, 182, 4,         2 290, 444, 2 2 246, 631, 5 542
             0Õ0é0ó0Ñ0ü0Ä 2 256, 681               <row 6alue constructor
          ! !right bracket>, 79, 81,          list>, 0Ñ0ü0Ä 174, 6,
             83, 504, 5                   2 290, 669
          <right 0aren>, 16, 5 5 59, 80,     ROW_COUNT, 84, 479, 2 2 281,
             107, 108, 1, 4, 1 (R´ ),       484, 2 2 285, 670ª0ü0à             10Õ0¡0é0Ã0É, ª0Ñ0ü0Ä 10Ø0ë0Ä, 1, 144,    Rule evaluation order, 
             ¬5, 168, 0Ñ0ü0Ä 180, 6,    Rules determining collating
             203,  (h* ) (l4 ) 2 (Nã ),  (y> )9, 245,       sequence 5sage,  (y> )
              (Œ¡ )0, 272,  (y] )4, 281,  (Nã )6,               - S -
              (Nã )7, 2 2, 0Õ0¡0é0Ã0É0, 2 2 (ry ), 0Ö0Ã0·0§0ë6,    SAVEPOINT, 85
             2 288, 0Ø0ë0Ä0, 2 2 289, 491, 500,    Scalar expressions, 107
             508, 5¬, 520               <scalar subquery>, 155,
          ROLE, 85                          ¬6, 203, 64 ( )          ROLLBACK, 68, 70, 85, 0Õ0é0ó5,     ! !scalar subquery>, <row
             405, 2 2 284                       subquery>, and <table
          ! !rollback statement>, 2 2 21,         subquery>,  (eå )0ª0ü0à             50, 54, 5 57, 5 59, 5 5 50, 2 242,    SCALE, 84, 425, 2 2 2 (Œ¡ ), 427,
             0Ø0¯0¿0ü0ë9, 2 2 205, 484, 5 (Œ¡ ), 655,       2 2 20Ö0Ã0·0§0ë, 436, 2 2 20Ø0ë0Ä, 440, 2 2 241,
             5 571, 674                       450Ñ0ü0Ä 2 2 254, 455, 2 2 256, 457,
          ROUTINE, 85                       50Ø0ë0Ä, 544, 570, 571, 572,
          ROW, 85                           660ª0ü0à          ROWS, 85,  (Œ¡ )0, 275,  (R´ )1,       ! !scale>, 63, 107, 1SA, 109,
             0Ø0ë0Ä7, 5 581                       110, 0Õ0é0ó8, 2 261, 515, 5­,
          <row subquery>, 0Ñ0ü0Ä 174,         520, 5 (g	 ), 658
             203                         SCHEMA, 85, 255,  (ry )8, 2 241,
          <row 6alue constructor 1>,        417, 2 2 283, 484, 50Õ0é0ó, 567
             2 (y] ),  (g	 )8


                                                            Index  50ª0ü0à
  


          <schema authorization          SCHEMATA, 50Ú0Ë0Ò, 541, 543,
             identifier>, 65,  (ry )5,          544, 549, 550, 551, 55 (l4 )
              (ry )6                            553, 557, 558, 559, 561,
          <schema character set name>       56 (l4 ) 569, 571, 573, 574,
             , 0Ó0ë1                          576, 580, 583, 584, 585,
          <schema character set             586, 591, 595, 596, 598,
             specification>, 93,            5 50, 608, 5 510, 611, 5 540
             100, 255,  (ry )6, 257,  (Œ¡ )0Ñ0ü0Ä    SCHEMATA base table, 569
             644, 5 560                    SCHEMATA 6iew, 50Ú0Ë0Ò
          ! !schema collation name>,       SCHEMATA_FOREIGN_KEY, 569
             2 2, 0Ó0ë5                    SCHEMATA_PRIMARY_KEY, 569
          ! !schema definition>, 44,       <schema translation name>,
             52, 65, 93, 100, 101,          2 2 (eå ), 0Õ0¡0é0Ã0É1
             252,  (ry )5, 256,  (Œ¡ )0, 261,    SCHEMA_NAME, 84, 0Õ0é0ó4, 2 2 280,
             263,  (Nã )6, 2 201, 0Ó0ë1, 2 2¬,       481, 2 2 286, 487, 50Ú0Ë0Ò, 541,
             0Õ0¡0é0Ã0É0, 2 2 (ry ), 0Ø0¯0¿0ü0ë8, 2 2 284, 566,       543, 544, 549, 550, 551,
             568, 660                       55 (l4 ) 553, 557, 558, 559,
          Schema definition and             561, 56 (l4 ) 569
             manipulation,  (ry )5           SCHEMA_OWNER, 538, 541,
          <schema element>,  (ry )5, 256,       540Ñ0ü0Ä 544, 549, 550, 551,
             63 (l4 ) 5 544                       552, 550Ñ0ü0Ä 557, 558, 559,
          <schema name>, 15, 2 29, 2 2 24,        561, 562, 569
             2 2 25, 2 2 26, 5 54, 5 5 5 (l4 ) 5 5 50Ñ0ü0Ä 98,     SCHEMA_OWNER_NOT_NULL, 569
             99, 101, 10 (l4 ) 103, 104,     scope, 1, 10, 14, 2 29, 5 5 (l4 )
              (T )9, 252,  (ry )5, 256,  (ry )7,       5 50Ñ0ü0Ä 5 5 50, 99, 102, 100Ñ0ü0Ä
              (ry )8, 260,  (Œ¡ )0Ñ0ü0Ä 283,  (Nã )4,       104,  8, 1, 1, 1 (g	 ),
             296,  (Nã )7, 2 200, 0Ô0³1, 2 202,       5, 260,  (R´ )0Ñ0ü0Ä 2 256, 0Ú0Ë0Ò6,
             0Ô0³4, 2 2SD, 0Ó0ë1, 2 2, 0Ó0ë0Ñ0ü0Ä       2 292, 0Ø0ë0Ä4, 2 297, 431, 2 2 20Õ0£0ü0È,
             2 2¬, 0Ó0ë6, 2 2, 0Õ0¡0é0Ã0É0, 2 2 (h* ),       447, 2 2 249, 450, 2 2 251, 459,
             0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (ry ), 0Õ0¡0é0Ã0É6, 2 2 (R´ ), 0Ö0Ã0·0§0ë1,       2 2 265, 466, 2 2 267, 475, 2 2 292,
             2 297, 0Ø0ë0Ä8, 2 2 2¬, 417, 2 2 286,       501, 5 569
             487, 2 2 293, 616, 5 544, 654,    Scope, 1
             656, 5 557, 661, 5 568, 669     scope clause,  8, 1,
          <schema name clause>, 101,        431, 2 2 20Õ0£0ü0È
              (ry )5, 257, 644, 5 557          <scope option>, 99, 10 (l4 )
                                            104, 431, 2 2 20Õ0£0ü0È, 447, 2 2 251


          54  Database Language SQL

 
          SCROLL, 85, 2 271, 0Ú0½ (l4 ) 2 274,     SELECT, 65, 66, 75, 85,
             2 277, 464, 2 2 265, 469, 5 50Õ0é0ó,        9, 1 (g	 ), 0, 182, 0Ñ0ü0Ä
             638, 5 547, 681                  184, 1, 197, 8, 245,
          SEARCH, 85                         (Œ¡ )1, 271,  (y] ) (l4 ) 273,  (y] )6,
          ! !search condition>, 15, 2 26,       284,  (R´ )9, 298, 0Ô0³0Ñ0ü0Ä 2 2 (Nã ),
             2 2 2 (l4 ) 2 2 20Ñ0ü0Ä 5 58, 1,  (l4 )          0Õ0£0ü0È0, 2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5, 2 20Ø0¯0¿0ü0ë, 0Ú0Ë0Ò (l4 )
             1, 142, 0Ñ0ü0Ä 180, 1,       2 298, 480Ñ0ü0Ä 2 2 284, 485, 50Õ0£0ü0È,
             183, 5, 186, 7, 189,       537, 50Ú0Ë0Ò, 539, 541, 54 (l4 )
             0, 2 (Nã ),  (y> )0, 264,  (y] )1,       543, 544, 545, 546, 547,
             272,  (R´ )1, 282,  (R´ )4, 289,       548, 549, 550, 551, 55 (l4 )
              (Nã )4, 2 200, 0Ô0³1, 2 202, 0Ô0³7,       553, 554, 555, 556, 557,
             2 2SD, 0Ó0ë0Ñ0ü0Ä 2 2, 0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (ry ),       558, 559, 561, 562, 560Ñ0ü0Ä
             0Õ0¡0é0Ã0É6, 2 20Ô0³, 0Õ0£0ü0È7, 2 286, 0Ú0Ë0Ò7,       571, 57 (l4 ) 573, 576, 578,
             2 294, 0Ø0ë0Ä5, 2 296, 485, 593,       580, 581, 580Ñ0ü0Ä 584, 585,
             594, 595, 596, 5 50Õ0£0ü0È, 636,       586, 588, 591, 590Ñ0ü0Ä 595,
             5 543, 677, 5 578                  596, 5 500, 601, 5 502, 600Ñ0ü0Ä
          search condition too long         5 504, 606, 5 5SA, 610, 5 5 ,
             for information schema,        616, 5 5, 618, 5 577
              (R´ ) (l4 ) 2 2 (Œ¡ ), 620µ0ó0Á0ü0à              <select list>, 5 5 55, 1,
          <searched case>, 141,  (N  )         9, 1 (T ), 1, 182, 5,
          ! !searched 7hen clause>,           191,  (l4 ) 193, 4, 195,
             141,  (l4 ) 143                  8, 2 282, 436, 2 2 243, 450,
          SECOND, 2 20, 2 21, 2 2 (l4 ) 2 20Ñ0ü0Ä 85,
             95,  1, 1,  0Ñ0ü0Ä 1 (Nã ),        2 2 251, 457, 2 2 260, 63 (l4 ) 5 572
              (y> )8, 20Ø0ë0Ä,  (T )0, 241,  (T ) (l4 )    <select statement: single
             2 2 20Ô0³, 441, 2 2 245, 659, 5 581        row>, 53, 55, 57, 58,
          <seconds fraction>, 91, 94,       59, 10 (l4 ) 1,  9, 2 250,
             95, 96, 242, 629               0Ø0¯0¿0ü0ë8, 2 282, 484, 5 572, 677
          <seconds integer 6alue>,       ! !select sublist>, 191, 5,
             91, 95,  (T ) (N  )                   5 543
          ! !seconds value>, 91, 94        <select target list>, 0Ú0Ë0Ò (l4 )
          SECTION, 85, 490                  2 283, 671, 5 572
                                         <semicolon>, 80, 2 246, 489,
                                            2 2 291, 504, 5¬, 517, 5 (eå ),
                                            525
                                         SENSITIVE, 85


                                                            ! ?ndex  55

 
          ! !separator>, 82, 83, 86,       set, 2 2, 5, 5 5, 7, 11, 19,
             89, 92, 93, 100, 2 2 291,          20, 21, 2 (l4 ) 20Ñ0ü0Ä 2 20, 2 2 (l4 )
             51 (N  )                           2 25, 2 26, 2 27, 2 28, 2 2 21, 2 2 24,
          sequence, 5, 7, 9, ,  (eå ),        2 2 25, 2 2 26, 2 2 27, 2 2 28, 5 (l4 ) 54,
              (h* ),  (g	 ),  (y> ),  (T ),  (ry ),  (Œ¡ ),        5 50, 5 5 (l4 ) 5 54, 5 55, 5 56, 5 57,
             0Õ0¡0é0Ã0É, 0Õ0é0ó, 0Ú0½, 47, 67, 69,        5 58, 5 5 50, 5 5 51, 5 5 5 (l4 ) 5 5 50Ñ0ü0Ä 5 5 54,
             72, 92, 95, 97, 104,           80, 85, 86, 87, 89, 9 (l4 )
              5, 1 (g	 ), 5, 10Õ0£0ü0È, ª4,       90Ñ0ü0Ä 97, 98, 99, 100,
             145, ¬5, 161, 7, 191,       10 (l4 ) 103, 104, 105, 107,
              (eå )7, 2SA,  (h* )4, 2¬,  (h* )6,       1SA, 109, 1¬, 4, 1 (Œ¡ ),
             2 (eå ),  (g	 )4, 20Ú0½,  (T )9, 250,       7, 10Õ0£0ü0È, ª4, 10Ø0¯0¿0ü0ë,  (l4 )
              (ry )1, 264,  (Nã )7, 2 2, 0Ó0ë5,       153, ¬5, 173, 6, 178,
             2 2­, 0Ó0ë7, 2 2, 0Ú0½ (l4 ) 2 288,       1, 183, 4, 185, 6,
             497, 501, 506, 5SD, 521,       187, 9, 190, 1, 192,
             5 560, 661                       0Ñ0ü0Ä 194, 5, 197, 8,
          SEQUENCE, 85                      199,  (eå )0, 201,  (eå ) (l4 ) 2SA,
          SERIALIZABLE, 68, 69, 84,          (g	 ) (l4 ) 20Ó0ë,  (y> ) (l4 ) 20Õ0£0ü0È,  (y> )4,
             0Õ0é0ó0, 2 299, 528                  20Õ0é0ó,  (y> )7, 20Ú0Ë0Ò,  (T )6, 248,
          serialization failure, 5 59,         (T )9, 250,  (ry )0Ñ0ü0Ä 255,  (ry )6,
             62 (N  )                           257,  (ry )8, 259,  (Œ¡ )1, 263,
          SERVER_NAME, 84, 2 2 279, 481,
             488                            267,  (y] )0Ñ0ü0Ä 275,  (y] )8, 279,
          SESSION, 85, 2 2 2 (eå ), 484, 5 582         (R´ )1, 286,  (R´ )7, 298, 0Ô0³1,
          Session management, 2 2 2¬           2 202, 0Ô0³4, 2 205, 0Ô0³6, 2 2 ,
          SESSION_USER, 85,  4, 1¬,       0Ó0ë (l4 ) 2 2ª, 0Ó0ë4, 2 2¬, 0Ó0ë6,
              6, 1,  (Œ¡ )6, 267,  (Œ¡ )8,       2 2, 0Ó0ë8, 2 2 (eå ), 0Õ0¡0é0Ã0É1, 2 2 (y> ),
             269,  (R´ ) (l4 ) 2 2 (ry ), 0Ú0½5, 50Ô0³,       0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0¡0é0Ã0É, 0Õ0£0ü0È0Ñ0ü0Ä
             641, 5 545, 658, 5 582             2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5, 2 20Ø0¯0¿0ü0ë, 0Õ0£0ü0È7, 2 20Ú0Ë0Ò,

                                            2 244, 0Ö0Ã0·0§0ë5, 2 248, 0Ö0Ã0·0§0ë9, 2 250,
                                            0Õ0é0ó1, 2 262, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 264, 0Ø0¯0¿0ü0ë5,
                                            2 266, 0Ø0¯0¿0ü0ë7, 2 268, 0Ø0¯0¿0ü0ë9, 2 282,
                                            0Ø0ë0Ä1, 2 292, 0Ø0ë0Ä0Ñ0ü0Ä 2 294, 0Ø0ë0Ä5,
                                            2 296, 0Ø0ë0Ä8, 2 299, 400, 2 2 201,
                                            40 (l4 ) 2 2 203, 409, 2 2 210, 411,
                                            2 2 2¬, 417, 2 2 2, 419, 2 2 2 (eå ),
                                            421, 2 2 2 (g	 ), 420Ñ0ü0Ä 2 2 2 (Œ¡ ), 427,
                                            2 2 2 (R´ ), 436, 2 2 20Ú0Ë0Ò, 439, 2 2 240,
                                            441, 2 2 244, 447, 2 2 250, 45 (l4 )
                                            2 2 253, 454, 2 2 255, 456, 2 2 257,
                                            458, 2 2 274, 475, 2 2 277, 48 (l4 )
                                            2 2 283, 484, 2 2 288, 489, 2 2 290,
          56  Database Language SQL         49 (l4 ) 2 2 293, 495, 2 2 296, 500,

                                            501, 503, 504, 50, 507,
                                            5SA, 510, 5 , 51 (l4 ) 5ª,
                                            514, 5­, 517, 5, 519,
                                            5 (eå ), 521, 5 (y> ), 527, 5 (R´ ),
                                            554, 569, 605, 5 50, 607,
                                            5 5SD, 611, 5 5, 625, 5 5 (Nã ),
                                            630, 5 50Õ0¡0é0Ã0É, 630Ñ0ü0Ä 5 50Õ0é0ó, 636,
                                            5 50Ú0½, 639, 5 541, 644, 5 545,
                                            646, 5 547, 648, 5 549, 651,
                                            5 553, 654, 5 556, 657, 5 558,
                                            660, 5 561, 66 (l4 ) 5 563, 664,
                                            5 565, 670, 5 572, 670Ñ0ü0Ä 5 574,
                                            678

  


          SET, 85, 107, 108, 1ª,        ! !set domain default clause>
              (T )8, 255,  (ry )9, 274,  (y] )8,       , 2 204, 0Ô0³5, 5 50Õ0£0ü0È
              (y] )9, 287, 0Ô0³5, 2 2 , 0Ó0ë0Ñ0ü0Ä    <set function specifica-
             0Õ0¡0é0Ã0É9, 2 249, 0Ø0ë0Ä1, 2 294, 0Ø0ë0Ä9,       4ion>,  , 4, 1 (y] ),
             2 2 201, 400Ñ0ü0Ä 2 2 210, 415, 2 2 2,       ¬5, 181, 5, 186, 9,
             419, 2 2 2 (eå ), 42 (l4 ) 2 2 20Ú0Ë0Ò, 474,       190,  (l4 ) 193, 4, 195,
             2 2 277, 48 (l4 ) 2 2 284, 500, 501,        (R´ )1, 2 292, 0Ø0ë0Ä4, 2 2 244, 474,
             504, 505, 506, 5SA, 509,       5 50Õ0¡0é0Ã0É, 641, 5 578
             51 (l4 ) 5ª, 517, 5, 520,    <set function type>, 1 (T )
             521, 5 (y] ), 564, 590, 591,    <set item information>,
             592, 604, 5 540, 658             438, 2 2 20Ø0ë0Ä
          ! !set catalog statement>,       <set local 4ime zone
             45, 54, 64, 73, 0Ø0¯0¿0ü0ë9,           statement>, 54, 5 5 50Ñ0ü0Ä
             415, 2 2 247, 484, 5 50Õ0é0ó, 636,       2 269, 42 (l4 ) 2 2 2 (y> ), 447, 2 2 284,
             5 50Ú0½, 639                       649, 5 551
          ! !set clause>, 2 291, 0Ø0ë0Ä (l4 )        <set names statement>, 54,
             0Ø0ë0Ä0Ñ0ü0Ä 2 294, 0Ø0ë0Ä5, 2 2 247, 474,       5 54, 5 5 50Ñ0ü0Ä 2 269, 419, 2 2 247,
             2 2 275, 636                       484, 5 50Õ0é0ó, 637, 5 50Ø0ë0Ä
          ! !set clause list>, 0Ø0ë0Ä1,        Set operation result data
             2 292, 0Ø0ë0Ä4, 2 296, 474, 2 2 277        types, 20Ú0½
          ! !set column default clause>    <set iuantifier>, 4, 191,
             , 286,  (R´ )7, 5 545                0Ñ0ü0Ä 194, 5, 2 282
          ! !set connection statement>,    <set schema statement>, 44,
             54, 5 5 51, 5 5 5 (l4 ) 5 5 54, 2 249,           54, 64, 73, 0Ø0¯0¿0ü0ë9, 2 2 2,
             2 269, 410, 2 2 2 , 484, 2 2 288,       418, 2 2 247, 484, 5 50Õ0é0ó, 637,
             527, 5 50Ø0¯0¿0ü0ë                       5 50Ø0ë0Ä, 650ª0ü0à          <set constraints mode          ! !set session authorization
             statement>, 2 2 21, 54,            identifier statement>,
              (ry )0Ñ0ü0Ä 2 269, 401, 2 2 202, 484,       54, 5 55, 2 269, 420, 2 2 2 (h* ),
             5 50Õ0é0ó, 636, 5 50Ú0½, 639             447, 2 2 284, 647, 5 549, 651
          <set count>, 2 2 20Ú0Ë0Ò               ! !set time +one value>, 42 ( )          <set descriptor informa-       ! !set transaction statement>
             tion>, 2 2 20Ú0Ë0Ò                     , 2 2 28, 54, 5 57, 5 58, 2 249,
          <set descriptor statement>,       0Õ0é0ó0, 2 269, 0Ø0ë0Ä9, 2 2 200, 484,
             54, 60, 62, 0Ø0¯0¿0ü0ë9, 2 2 20Ú0Ë0Ò,          5 (R´ ), 647, 5 548
             439, 2 2 241, 484, 5 572          <sign>, 90, 91, 95, ¬7,
                                            168, ­9
                                         SIGNAL, 85


                                                            Index  57

  


          <signed integer>, 90           ! !simple 6alue specifica-
          <signed numeric literal>,         tion>, 5 5 (l4 ) 5 5 51, 99, 102,
             89, 90, 95, 146, 7,           4, 1­, ­7, 2 247, 0Ú0½7,
              (Œ¡ )7                            2 278, 0Ø0ë0Ä9, 2 2 2SA, 425, 2 2 2 (Œ¡ ),
          significant, 27, 28, 2 21,          431, 2 2 20Õ0£0ü0È, 434, 2 2 20Ú0Ë0Ò, 44 (l4 )
             0Õ0£0ü0È, 0Ö0Ã0·0§0ë, 6, 149, ¬1,         2 2 243, 447, 2 2 251, 465, 2 2 280,
             154, ¬8, 166, ­9, 170,       657
             171,  (eå )9, 20Ú0Ë0Ò,  (T )0, 241,    ! !simple 7hen clause>, 141
              (T ) (l4 ) 267, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 5, 518,    simply contain,  ,  (T ), 0Ø0¯0¿0ü0ë,
             5 553                             9, 1 (T ), ¬6, 158, ­ (l4 )
          SIMILAR, 85                       163, ­5, 166, ­7, 168,
          <simple case>, 141,  (N  )          ­9, 173, 4, 175, 1,
          ! !simple Latin letter>,  (g	 ),        192, 0Ñ0ü0Ä 197,  (eå )1, 267,
             5 5 59, 98                         0Ú0½ (l4 ) 2 275, 440Ñ0ü0Ä 2 2 244, 446,
          ! !simple Latin lower case          2 2 267, 579, 5 50Ó0ë, 64 ( )             letter>, 79, 81, 87, 88,    simply underlying 4able,
             10Õ0é0ó, ª6, 5 540                  0Ú0Ë0Ò, 0Ñ0ü0Ä 200,  (Nã )9, 2 272,
          <simple Latin upper case          0Ú0Ë0Ò4, 2 291, 47 (l4 ) 2 2 274
             letter>, 5 5 59, 81, 87,        <single datetime field>,
             ª5, 10Ø0¯0¿0ü0ë, 619, 5 566             20Ø0ë0Ä,  (T )0, 241,  (T ) ( )          <simple table>, 6, 197,      SIZE, 85, 2 299, 68 ( )             200,  (eå )1, 202, 63 (l4 ) 5 570     SMALLINT, 19, 27, 2 24, 85,
          ! !simple 4arget specifi-           1SA,  0, 2 252, 0Õ0é0ó6, 2 257,
             cation ´, 434, 2 2 20Õ0é0ó,           0Õ0é0ó8, 2 259, 0Ø0¯0¿0ü0ë1, 2 262, 425,
             67 (N  )                           2 2 2 (Œ¡ ), 429, 2 2 240, 500, 502,
          <simple target specifi-           507, 510, 52 (l4 ) 571, 657,
             cation 2>, 2 2 20Ö0Ã0·0§0ë, 435,           5 562
             67 (N  )                        <solidus>, 80, 157, ¬8,
          ! !simple 4arget specifica-         168
             tion>, 1,  6, 2 247,       SOME, 85,  (g	 )0
             2 2 2 (ry ), 426, 2 2 20Ö0Ã0·0§0ë, 435, 2 2 247,    ! !some>, 2 (eå ),  (g	 )1
             2 2 279, 480, 2 2 282, 485          ! !sort key>, 2 271
          ! !simple 6alue specification    <sort specification>, 0Ú0½1,
             ´, 438                        2 272, 0Ú0½0Ñ0ü0Ä 50Ô0³, 531, 5 575
          ! !simple 6alue specification    <sort specification list>,
              (ŒÇ ), 438, 2 2 20Ø0ë0Ä                   2 271


          58  Database Language SQL

 
          ! !source character set          specifies, 1, 8, 9, ,  (eå ),
             specification>, 2 2 (eå ),            (g	 ),  (R´ ), 0Ô0³, 0Õ0¡0é0Ã0É, 0Ö0Ã0·0§0ë, 0Õ0é0ó,
             2 20Õ0é0ó                            0Ø0¯0¿0ü0ë, 0Ú0Ë0Ò, 41, 47, 49, 50,
          SOURCE_CHARACTER_SET_             62, 63, 65, 66, 67, 68,
             CATALOG, 556, 5 510, 611         72, 87, 94, 100, 1SA,
          SOURCE_CHARACTER_SET_NAME,        109, 110,   (l4 ) 1¬,  6,
             556, 5 510, 611                  1 (Œ¡ ),  (l4 ) 145, ­8, 169,
          SOURCE_CHARACTER_SET_SCHEMA       9, 192, 0Ñ0ü0Ä 197,  (h* )8,
             , 556, 5 510, 611                20Ú0Ë0Ò,  (T )0, 241,  (T ) (l4 ) 243,
          SPACE, 21, 2 25, 85, 249,            (T )5, 246,  (T )9, 263,  (Œ¡ )4,
              (ry )0, 2 2, 0Ó0ë5, 5 5SA, 609,       265,  (Œ¡ )8, 272,  (y] )0Ñ0ü0Ä 275,
             5 560, 68 (N  )                       (y] )6, 277,  (y] )8, 279,  (R´ )1,
          ! !space>,  (eå ), 0Õ0é0ó, 62, 71,
             5 5 59, 80, 80Ñ0ü0Ä 86, 90, 91,         (R´ ) (l4 ) 284, 0Ô0³1, 2 202, 0Ó0ë5,
             ª6, 146, 7, 148, 9,       2 2­, 0Õ0¡0é0Ã0É1, 2 2 (Œ¡ ), 0Õ0¡0é0Ã0É9, 2 20Ô0³,
             151, ­0Ñ0ü0Ä 2SA,  (h* )6, 20Õ0¡0é0Ã0É,       0Õ0£0ü0È0Ñ0ü0Ä 2 242, 0Ö0Ã0·0§0ë4, 2 247, 0Õ0é0ó (l4 )
              (y> )4, 20Õ0é0ó,  (Œ¡ )8, 2 263, 0Ø0¯0¿0ü0ë4,       2 256, 0Õ0é0ó7, 2 258, 0Õ0é0ó9, 2 260,
             2 265, 0Ø0¯0¿0ü0ë6, 2 267, 486, 2 2 287,       0Ø0¯0¿0ü0ë1, 2 262, 0Ø0¯0¿0ü0ë0Ñ0ü0Ä 2 264, 0Ø0¯0¿0ü0ë5,
             488, 2 2 291, 51 (N  )                 2 266, 0Ø0¯0¿0ü0ë7, 2 271, 0Ú0½0Ñ0ü0Ä 2 276,
          spans, 5 5 5 (l4 ) 299                    0Ú0½8, 2 279, 0Ú0Ë0Ò (l4 ) 2 288, 0Ø0ë0Ä0Ñ0ü0Ä
          Specification of syntactic        2 295, 400Ñ0ü0Ä 2 2 2SA, 428, 2 2 2 (Nã ),
             elements, 9                    446, 2 2 249, 45 (l4 ) 2 2 254, 464,
          Specification of the              2 2 282, 49 (l4 ) 2 2 293, 494, 2 2 295,
             ! ?nformation Schema,            496, 2 2 297, 499, 501, 50 (l4 )
             10                             50, 507, 510, 510Ñ0ü0Ä 5,

                                            5­, 518, 5, 52 (l4 ) 5 (Œ¡ ),
                                            531, 564, 619, 5 5 (T ), 625,
                                            5 5 (Œ¡ ), 630, 5 50Õ0¡0é0Ã0É, 638, 5 541,
                                            644, 5 548, 659, 5 561, 668,
                                            5 569, 685
                                         SQL, 85, 489


                                                            Index  59

  


          SQL-agent, 2 2 28, 5 56, 5 58, 5 5 50,     SQL-data, 1, 10, , 0Ó0ë,
             5 5 51, 5 5 5 (l4 ) 5 5 54, 96, 2 242,           0Õ0é0ó, 40, 43, 45, 46, 50,
             2 243, 0Ö0Ã0·0§0ë8, 2 249, 0Õ0é0ó0, 2 252,       51, 52, 53, 55, 56, 57,
             2 299, 400, 2 2 201, 400Ñ0ü0Ä 2 2 205,       58, 59, 60, 67, 68, 69,
             2 2 2SA, 409, 2 2 210, 411, 2 2 2,       70,  (y> )1, 20Ö0Ã0·0§0ë,  (R´ )1, 2 251,
             2 2 2ª, 526, 5 (y] ), 528, 5 546,       0Ú0½9, 2 282, 400Ñ0ü0Ä 2 2 204, 405,
             654, 5 556, 661, 5 568, 669,       5 (R´ ), 655, 5 562, 668
             5 570, 671, 5 572               ! !SQL data change statement>
          SQL-agents, 5 56                    , 2 268, 0Ø0¯0¿0ü0ë9
          SQL-client, 70, 71, 74,        ! !SQL data statement>, 2 250,
             2 2 2SD, 656, 5 569                  0Ø0¯0¿0ü0ë8
          SQL-client 5nable to           SQL descriptor area, 62,
             establish SQL-connection       64, 104, 2 2 20Ó0ë, 43 (l4 ) 2 2 20Õ0£0ü0È,
             , 2 2 2SD, 620                     434, 2 2 20Õ0é0ó, 436, 2 2 20Ú0Ë0Ò, 439,
          SQLCODE, 47, 48, 49, 85,          2 2 251, 450Ñ0ü0Ä 2 2 257, 458, 2 2 260,
             2 246, 0Ö0Ã0·0§0ë7, 2 252, 0Õ0é0ó6, 2 257,       469, 2 2 270, 660Ñ0ü0Ä 5 567
             0Õ0é0ó8, 2 259, 0Ø0¯0¿0ü0ë0, 2 261, 48 (l4 )    <sql diagnostics
             485, 2 2 292, 494, 2 2 295, 496,       information>, 2 2 279
             500, 502, 507, 510, 514,    <sql diagnostics statement>
             5­, 519, 5 (g	 ), 624, 5 554,       , 48, 74, 0Ö0Ã0·0§0ë9, 2 251, 0Ø0¯0¿0ü0ë8,
             661, 5 562, 664, 5 565, 666,       2 269, 647
             5 568, 675                    ! !SQL dynamic data
          SQLCODE 6alues, 5 5 (T )               statement>, 5 57, 2 250,
          <sql conformance>, 16, 17         0Ø0¯0¿0ü0ë9, 5 555
          SQL-connection, 5 (l4 ) 54, 55,    <sql dynamic statement>,
             57, 58, 60, 70, 71, 72,        104, 0Ø0¯0¿0ü0ë8, 2 269, 451, 5 50Õ0é0ó,
             104, 407, 2 2 2SA, 409, 2 2 210,       647
             2 2 2 , 41 (l4 ) 2 2 2ª, 66 (l4 ) 5 572     SQL dynamic statements, 5 51
          SQL-connections, 5 5 50            ! !SQL edition>, ­, 
          ! !SQL connection statement>,    <sql embedded language
             74, 0Ö0Ã0·0§0ë8, 2 249, 0Ø0¯0¿0ü0ë8, 2 269,        character>, 5 5 59
             2 2 288, 525, 5 (Œ¡ ), 527, 5 50Õ0é0ó,    SQL-environment, 45, 46,
             5 540                            70, 71, 72, 74, 75, 0Ö0Ã0·0§0ë4,
                                            5 554, 655, 5 563
                                         SQLERROR, 85, 497, 2 2 299
                                         SQLEXCEPTION, 85
                                         SQL Flagger, 5 5 56, 5 5 57, 5 5 (Œ¡ )


          60  Database Language SQL

  


          SQL-implementation, 1, 5 5,      ! !SQL-server name>, 70, 71,
             5 5 5, ­, 45, 46, 48, 71,         99, 100Ñ0ü0Ä 2 2 207, 408, 2 2 2SD,
             5 5 54, 5 5 56, 5 5 57, 2 250, 0Õ0é0ó (l4 )          488, 5 555, 660ª0ü0à             5 (R´ ), 560Ñ0ü0Ä 5 5­, 625, 5 556,    SQL-server rejected
             66 (N  )                           establishment of SQL-
          ! !SQL language character>,         connection, 2 2 2SD, 620
             20, 2 2 26, 5 5 59, 86, 9 (l4 ) 90Ñ0ü0Ä     SQL-session, 7, 2 21, 2 28, 2 29,
             100, 147, 8, 149, ¬0,       2 2 24, 2 2 25, 2 2 26, 51, 5 (l4 ) 54,
             ¬1, 2 244, 49 (l4 ) 5 558, 661        55, 56, 58, 5 50, 5 5 (l4 ) 5 50Ñ0ü0Ä
          ! !SQL language identifier>,        5 55, 5 59, 5 5 51, 5 5 5 (l4 ) 5 5 50Ñ0ü0Ä 5 5 54,
             98, 99, 100                    90Ñ0ü0Ä 94, 96, 100, 101,
          ! !SQL language identifier          103, 104, 1,  5, 1­,
             0art>, 98, 100                  (l4 ) 10Ø0ë0Ä, ¬0Ñ0ü0Ä 167,  (ry )6,
          ! !SQL language identifier          2 2SD, 0Ö0Ã0·0§0ë (l4 ) 2 243, 0Ö0Ã0·0§0ë8, 2 249,
             start>, 98, 100                0Õ0é0ó0, 2 297, 0Ø0ë0Ä8, 2 2 201, 408,
          ! !SQL object identifier>, ­       2 2 2SD, 410, 2 2 2 , 410Ñ0ü0Ä 2 2 2¬,
          <sql 0refix>, 489, 2 2 290, 491       417, 2 2 2, 420, 2 2 2 (h* ), 42 (l4 )
          ! !SQL procedure statement>,
             2 2 27, 55, 56, 5 5 54, 2 246,           440, 2 2 287, 526, 5 (y] ), 528,
             0Ö0Ã0·0§0ë7, 2 248, 0Ø0¯0¿0ü0ë8, 2 270, 489,       5 553, 654, 5 555, 656, 5 563,
             2 2 294, 495, 2 2 296, 497, 2 2 299,       668, 5 569
             526, 5 50Õ0é0ó, 647, 5 556, 670Ñ0ü0Ä    SQL-sessions, 72
             674                         <sql session statement>,
          ! !SQL provenance>, 16              2 268, 0Ø0¯0¿0ü0ë9, 2 2 242, 525, 5 50Õ0é0ó,
          SQL-schema, 44                    639, 5 547, 651
          <sql schema definition         ! !SQL special character>,
             statement>, 2 268, 0Ú0½0           79, 83
          ! !SQL schema manipulation       SQLSTATE, 47, 48, 49, 75,
             statement>, 2 268                84, 85,  (ry )0Ñ0ü0Ä 2 246, 0Ö0Ã0·0§0ë7,
          SQL-schemas, 44                   2 252, 0Õ0é0ó0Ñ0ü0Ä 2 254, 0Õ0é0ó5, 2 256,
          <sql schema statement>, 44,       0Õ0é0ó7, 2 258, 0Õ0é0ó9, 2 260, 0Ø0¯0¿0ü0ë1,
             0Õ0é0ó0, 2 268, 44 (l4 ) 5 (ry ), 528,       2 2 281, 48 (l4 ) 2 2 285, 486, 2 2 287,
             5 (Nã ), 530Ñ0ü0Ä 5 50Õ0é0ó, 639, 5 547,       488, 2 2 292, 494, 2 2 295, 496,
             651                            500, 50 (l4 ) 507, 510, 5ª,
          SQL-server, 70, 71, 72, 74,       514, 5­, 519, 5 (g	 ), 619,
             99, 100Ñ0ü0Ä 2 2 207, 408, 2 2 2SD,        5 5 (T ), 665, 5 568, 68 ( )             2 2 210, 411, 2 2 288, 655, 5 562,    SQLSTATE class and subclass
             660Ñ0ü0Ä 5 569                       6alues, 5 5


                                                            ! ?ndex  61

 
          SQL-statement, 1, 10, 1 (l4 )      SQL-transaction, 5 5 5, 41, 45,
             14, 2 2 21, 2 2 25, 2 2 28, 50, 51,        49, 50, 52, 54, 55, 56,
             5 (l4 ) 55, 56, 57, 58, 59,        58, 60, 67, 68, 69, 70,
             5 50, 5 51, 5 50Ñ0ü0Ä 5 54, 5 55, 5 56,        71, 75, 76, 0Ö0Ã0·0§0ë9, 2 250,
             5 57, 5 58, 5 59, 5 5 51, 5 5 5 (l4 ) 1­,       0Ú0Ë0Ò4, 2 286, 0Ú0Ë0Ò9, 2 292, 0Ø0ë0Ä4,
             ª9, 140, 4, 192, 7,       2 299, 400, 2 2 201, 400Ñ0ü0Ä 2 2 204,
             199,  (eå )0, 253,  (ry )6, 277,       405, 2 2 207, 410, 2 2 2 (eå ), 448,
              (y] )9, 280, 0Ö0Ã0·0§0ë (l4 ) 2 249, 0Ø0¯0¿0ü0ë8,       5 (y] ), 528, 5 554, 655, 5 562,
             2 2 207, 410, 2 2 249, 48 (l4 ) 2 2 284,       668, 5 572, 677
             2 2 285, 486, 2 2 292, 497, 5 (Œ¡ ),    SQL-transaction isolation
             530Ñ0ü0Ä 5 554, 658, 5 567, 668,       levels and the three
             5 569, 670Ñ0ü0Ä 5 574                  phenomena, 5 58
          SQL-statement character        SQL-transactions, 5 57
             codes for 5se in the        ! !SQL transaction statement>
             diagnostics area, 48 (N  )         , 2 268, 0Ø0¯0¿0ü0ë9, 2 2 242, 525,
          ! !SQL statement name>, 14,         5 50Õ0é0ó, 639, 5 547
             59, 99, 105, 2 2 242, 447,      <sql 6ariant>, 16
             2 2 248, 449, 2 2 250, 459, 5 540     SQLWARNING, 85
          SQL-statements, 51             SQL_IDENTIFIER, 50Ø0¯0¿0ü0ë, 564,
          SQL-statements and                568, 569, 570, 570Ñ0ü0Ä 574,
             4ransaction states,            576, 578, 580, 583, 584,
             59                             585, 588, 590, 590Ñ0ü0Ä 595,
          SQL-statements classified         596, 598, 600, 5 502, 604,
             by function, 5 (N  )               5 50, 608, 5 510
          ! !SQL statement variable>,      SQL_IDENTIFIER domain, 564
             , 59, 44 (l4 ) 2 2 243, 46 (N  )      SQL_LANGUAGES, 563, 61 (l4 )
          ! !SQL terminal character>,         5 540
             79                          SQL_LANGUAGES base 4able,
          <sql 4erminator>, 489, 2 2 290,       61 ( )             2 2 291                         SQL_LANGUAGES 6iew, 563
                                         SQL_LANGUAGES_SOURCE_NOT_
                                            NULL, 61 ( )                                         SQL_LANGUAGES_STANDARD_
                                            VALID_CHECK, 61 ( )                                         SQL_LANGUAGE_BINDING_STYLE,
                                            563, 61 (l4 ) 5 5ª, 614
                                         SQL_LANGUAGE_CONFORMANCE,
                                            563, 61 (l4 ) 5 5ª, 614


          62  Database Language SQL

  


          SQL_LANGUAGE_IMPLEMENTATION    ! !statement information item
             , 560Ñ0ü0Ä 5 5, 614, 5 565           name>, 479, 2 2 280, 481
          SQL_LANGUAGE_INTEGRITY,        ! !statement name>, 5 5 (l4 ) 99,
             560Ñ0ü0Ä 5 5, 610Ñ0ü0Ä 5 5             103, 448, 2 2 249, 450, 2 2 259,
          SQL_LANGUAGE_PROGRAMMING_         464, 2 2 267, 67 ( )             LANGUAGE, 563, 61 (l4 ) 5 5ª,    ! !statement or declaration>,
             614, 5 5¬                       2 2 289
          SQL_LANGUAGE_SOURCE, 560Ñ0ü0Ä      Status codes, 619
             5 5, 610Ñ0ü0Ä 5 5, 665          status parameter, 2 2 27
          SQL_LANGUAGE_YEAR, 563,        ! !status 0arameter>, 2 246,
             5 5, 610µ0ó0Á0ü0à                      0Ö0Ã0·0§0ë7
          SQL_TEXT,  (eå ), 0Ô0³, 87, 100,     Status parameters, 47
             109, 1¬,  (T )8, 267, 427,    Store assignment,  (y> )4
             2 2 2 (R´ ), 564, 5 507, 609, 5 558,    string data, length
             665                            mismatch, 20Õ0é0ó, 620
          <standard character            string data, right
             repertoire name>, 248,         truncation, 7, 148,
             249, 0Ó0ë1, 5 560                  9, 150, ¬1, 152, ­0Ñ0ü0Ä
          ! !standard collation name>,        20Õ0¡0é0Ã0É,  (y> )4, 20Õ0é0ó, 621, 5 5 (y> )
             0Ó0ë4, 2 2¬, 0Ó0ë7, 5 561          <string length>, 10Õ0¡0é0Ã0É, ª0Ñ0ü0Ä
          Standard programming              10Õ0é0ó, ª7
             languages, 49,  (T )0µ0ó0Á0ü0à         ! !string 6alue expression>,
          <standard translation name>       8, 10Ô0³, ª1, 10Õ0é0ó, ¬5,
             , 0Õ0¡0é0Ã0É0, 2 2 (h* ), 661                160, 530ª0ü0à          <standard universal            ! !string 6alue function>,
             character form-of-use          ª (l4 ) 160, ­1
             name>,  (T )8, 249, 660        STRUCTURE, 85
          ! !start field>, 1, 20Ú0Ë0Ò,       structured collection, 14
             20Ø0ë0Ä,  (T )0, 241,  (T ) (N  )         SUBCLASS_ORIGIN, 84, 479,
          ! !start position>, 10Õ0¡0é0Ã0É, ª0Ñ0ü0Ä       2 2 281, 485, 5 563
             ª5, 10Ú0½                    <subquery>,  , 10 (l4 ) 1,
          statement completion              4, 1 (ry ), ¬6, 185, 9,
             unknown, 5 5 51, 5 5 (g	 )               190, 1, 192, 5, 203,
          <statement information>,           (eå )4, 281,  (R´ ) (l4 ) 296, 0Ú0Ë0Ò6,
             479                            2 295, 631, 5 50Õ0¡0é0Ã0É, 630Ñ0ü0Ä 5 50Õ0é0ó,
          <statement information            636, 5 50Ú0Ë0Ò, 640Ñ0ü0Ä 5 578

             item>, 479, 2 2 280, 48 ( )

                                                            Index  5 50ª0ü0à
  


          SUBSTRING, 2 (l4 ) 85, 10Õ0¡0é0Ã0É,        Syntax Rules, 9, 10, ,
             10Õ0£0ü0È, 9, 151, 0Õ0é0ó0Ñ0ü0Ä 2 262,       ª, , ¬, 64, 77, 82,
             2 263, 0Ø0¯0¿0ü0ë4, 2 266, 445, 5 582        89, ª9, 162,  (eå )8, 20Ú0½,
          substring error, 10Õ0é0ó, ª7,         (y] )0, 284, 0Ô0³ (l4 ) 2 242, 0Ö0Ã0·0§0ë7,
             621                            2 271, 0Ú0½7, 2 282, 0Ú0Ë0Ò8, 2 292,
          successful completion, 2 2 27,        0Ø0ë0Ä4, 2 2 207, 408, 2 2 2¬, 417,
             0Õ0é0ó1, 5 5 (g	 ), 624                  2 2 2, 420, 2 2 20Ó0ë, 435, 2 2 20Ø0ë0Ä,
          SUM, 85, 1 (T ), 5, 1 (Œ¡ ), 659       44 (l4 ) 2 2 243, 447, 2 2 256, 458,
          Syntactic containment,           2 2 259, 46 (l4 ) 2 2 265, 469, 2 2 275,
          syntactic element, 11, 1 (l4 )
             ª, 72                         2 2 276, 477, 2 2 295, 496, 2 2 297,
          Syntactic substitution, ª        500, 501, 504, 505, 506,
          syntax error or access rule       5SA, 509, 5, 510Ñ0ü0Ä 5¬,
             6iolation, , ª, 486,        517, 5, 520, 5 (h* ), 525,
             487, 5 5 (g	 )                       5 (Œ¡ ), 530, 5 5 (ry ), 660Ñ0ü0Ä 5 565,
          syntax error or access rule       667, 5 577, 678
             6iolation in direct SQL      SYSTEM, 66,  (T )8, 261,  (R´ )9,
             statement, 1 (l4 ) 2 2 286, 487,       290,  (Nã )4, 298, 0Ô0³0, 2 202,
             5 (Œ¡ ), 62 (N  )                      0Ó0ë0, 2 2, 0Ó0ë0Ñ0ü0Ä 2 2­, 0Ó0ë8,
          syntax error or access rule       2 2 (h* ), 0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0¡0é0Ã0É,
             6iolation in dynamic SQL       0Õ0£0ü0È4, 2 20Õ0é0ó, 0Õ0£0ü0È6, 2 298
             statement, 1 (l4 ) 2 2 243, 46 (l4 )    <system descriptor
             486, 2 2 287, 62 (N  )                 statement>, 2 269
                                         SYSTEM_USER, 85, 1,  5,
                                            1­,  7, 192,  (Œ¡ )6, 267,
                                             (Œ¡ )8, 269,  (R´ ) (l4 ) 2 2 (ry ), 0Ú0½5,
                                            50Ô0³, 641, 5 545, 658, 5 582

                                                    - T -
                                         4able, 0Ú0½


          5 54  Database Language SQL

 
          TABLE, 85, 6, 197,  (ry )8,      <table expression>,  9,
              (Œ¡ )0, 283,  (Nã ) (l4 ) 294, 0Õ0¡0é0Ã0É9,       1 (g	 ), 5, 177, 1, 192,
             2 20Õ0¡0é0Ã0É, 0Õ0£0ü0È8, 2 297, 0Ø0ë0Ä8, 2 2 282,       0Ñ0ü0Ä 195,  (eå )0Ñ0ü0Ä 2 282, 0Ú0Ë0Ò0Ñ0ü0Ä
             480Ñ0ü0Ä 2 2 284, 568, 569, 570,       5 50Ó0ë, 63 (l4 ) 5 50Õ0é0ó, 640Ñ0ü0Ä 5 577
             570Ñ0ü0Ä 574, 576, 577, 578,    <table name>,  , 44, 98,
             580, 580Ñ0ü0Ä 584, 585, 588,       101, 103,  8, 1, 1,
             590, 593, 595, 596, 598,       1 (g	 ), 9, 193, 6, 197,
             5 500, 60 (l4 ) 5 504, 606, 5 5SA,        (eå )0, 245,  (ry )8, 260,  (Œ¡ )1,
             610, 5 5, 646                  263,  (y] ) (l4 ) 274,  (R´ ) (l4 ) 283,
          table check constraint, 41,        (R´ )9, 291,  (Nã ) (l4 ) 294,  (Nã )6,
             43                             297,  (Nã )8, 299, 0Ô0³0, 2 2 (Œ¡ ),
          table constraint, 41, 42          0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1, 2 20Õ0£0ü0È, 0Õ0£0ü0È4,
          ! !table constraint>, 264,          2 20Õ0é0ó, 0Õ0£0ü0È8, 2 284, 0Ú0Ë0Ò6, 2 288,
             270,  (y] )1, 2 2SD, 487             0Ú0Ë0Ò9, 2 291, 0Ø0ë0Ä (l4 ) 2 294, 0Ø0ë0Ä5,
          ! !table constraint                 2 2 259, 47 (l4 ) 2 2 274, 475, 2 2 276,
             definition>,  (Œ¡ )0, 263,         477, 2 2 285, 49 (l4 ) 5 50Ó0ë, 635,
              (Œ¡ )4, 270,  (Nã )1, 2 2SD, 0Ó0ë0,       5 50Ø0¯0¿0ü0ë, 638
             586                         4able 0rivilege descriptor,
          4able constraint descriptor       5 56
             , 2 2 20, 2 2 21, 2 2 2 (l4 ) 270,  (y] )1,     ! !table reference>,  8,
              (y] )5, 289,  (Nã )1, 2 20Ø0¯0¿0ü0ë, 0Õ0£0ü0È8        1, 0, 1 (h* ),  (l4 ) 1 (ry ),
          Table constraints, 2 2 21             8, 179, 0, 192, 0Ñ0ü0Ä
          ! !table definition>, 2 27, 2 28,       197, 9, 200,  (R´ )1, 296,
             5 (l4 ) 255,  (Œ¡ )0, 261,  (Œ¡ ) (l4 )         (Nã )8, 2 20Ó0ë, 630, 5 50Ó0ë, 641
             263,  (Œ¡ )5, 272,  (y] )4, 281,    Tables, 2 27
             284, 0Ø0¯0¿0ü0ë8, 2 2 284, 566          TABLES, 542, 540Ñ0ü0Ä 576, 578,
          4able descriptor, 15, 2 29,         580, 580Ñ0ü0Ä 585, 586, 595,
             2 2 20, 2 2 24, 5 5 55, 260,  (Œ¡ )1,          600, 5 540
              (Œ¡ )5, 273,  (y] )5, 283,  (R´ )9,    TABLES base table, 576
              (Nã )1, 292,  (Nã )6, 2 2SD, 0Õ0¡0é0Ã0É6,    <table subquery>,  8, 1,
             2 275, 576, 581                   (eå )0Ñ0ü0Ä 2,  (g	 )0, 2 (g	 ),  (g	 )0Ñ0ü0Ä
          ! !table element>,  (Œ¡ )0, 261         2 (T ),  (g	 )5, 2 2 246, 447
          <table element list>,  (Œ¡ )0,     TABLES view, 54 ( )             2 297                         TABLES_CHECK_NOT_VIEW, 576
                                         TABLES_FOREIGN_KEY_SCHEMATA
                                            , 576
                                         TABLES_PRIMARY_KEY, 576
                                         TABLES_TYPE_CHECK, 576


                                                            Index  5 55

  


          <table 6alue constructor>,     TABLE_CONSTRAINTS_TABLE_
             175, 6, 196, 7, 200,       SCHEMA_NOT_NULL, 585
              (eå ) (l4 ) 2, 0Ø0ë0Ä0, 2 2 244, 446,    TABLE_CONSTRAINTS_UNIQUE_
             5 50Ó0ë, 63 (l4 ) 5 542, 648             CHECK, 586
          ! !table value constructor       TABLE_NAME, 84, 480, 2 2 281,
             list>, 6                     486, 2 2 287, 54 (l4 ) 543, 544,
          TABLE_CATALOG, 54 (l4 ) 543,          545, 546, 547, 549, 552,
             544, 545, 546, 547, 549,       557, 558, 559, 561, 56 (l4 )
             55 (l4 ) 557, 558, 559, 561,       572, 576, 578, 580, 581,
             562, 57 (l4 ) 576, 578, 580,       580Ñ0ü0Ä 584, 585, 586, 587,
             581, 583, 584, 585, 586,       588, 589, 595, 596, 597,
             587, 588, 589, 591, 595,       600, 5 501, 60 (l4 ) 5 503
             596, 597, 600, 5 501, 60 (l4 )    TABLE_OR_DOMAIN_CATALOG,
             600µ0ó0Á0ü0à                           50Ø0ë0Ä, 545, 570, 571, 572,
          TABLE_CONSTRAINTS, 549,           570Ñ0ü0Ä 581
             559, 561, 585, 586, 588,    TABLE_OR_DOMAIN_CHECK_
             590, 591, 590Ñ0ü0Ä 5 5­, 618        COMBINATIONS, 570
          TABLE_CONSTRAINTS base         TABLE_OR_DOMAIN_DATA_TYPE_
             table, 585                     NOT_NULL, 570
          TABLE_CONSTRAINTS 6iew, 549    TABLE_OR_DOMAIN_NAME, 539,
          TABLE_CONSTRAINTS_CHECK_          545, 570, 571, 57 (l4 ) 573,
             REFERENCES_TABLES, 585         581
          TABLE_CONSTRAINTS_CHECK_       TABLE_OR_DOMAIN_SCHEMA,
             VIEWS, 586                     50Ø0ë0Ä, 545, 570, 571, 572,
          TABLE_CONSTRAINTS_DEFERRED_       570Ñ0ü0Ä 581
             CHECK, 585                  TABLE_PRIVILEGES, 54 (l4 ) 546,
          TABLE_CONSTRAINTS_                600, 5 540
             INITIALLY_DEFERRED_         TABLE_PRIVILEGES base table
             NOT_NULL, 585                  , 600
          TABLE_CONSTRAINTS_IS_          TABLE_PRIVILEGES view, 546
             DEFERRABLE_NOT_NULL,        TABLE_PRIVILEGES_FOREIGN_
             585                            KEY_TABLES, 5 500
          TABLE_CONSTRAINTS_PRIMARY_     TABLE_PRIVILEGES_GRANTABLE_
             KEY, 585                       CHECK, 5 500
          TABLE_CONSTRAINTS_TABLE_       TABLE_PRIVILEGES_GRANTABLE_
             CATALOG_NOT_NULL, 585          NOT_NULL, 600
          TABLE_CONSTRAINTS_TABLE_       TABLE_PRIVILEGES_GRANTEE_
             NAME_NOT_NULL, 585             FOREIGN_KEY_USERS, 600


          66  Database Language SQL

  


          TABLE_PRIVILEGES_GRANTOR_      4emporary 4able, 0Ú0½, 0Ú0Ë0Ò,
             FOREIGN_KEY_USERS, 600         0Ø0ë0Ä, 46, 53, 56, 57, 58,
          TABLE_PRIVILEGES_PRIMARY_         60, 72, 73, 76, 101,
             KEY, 5 500                       103,  (T )5, 258,  (Œ¡ )0, 261,
          TABLE_SCHEMA, 54 (l4 ) 543,            (Œ¡ ) (l4 ) 265,  (y] )5, 281,  (R´ )0Ñ0ü0Ä
             544, 545, 546, 547, 549,       294,  (Nã )6, 2 2 (ry ), 0Ö0Ã0·0§0ë0Ñ0ü0Ä 2 284,
             552, 557, 558, 559, 561,       0Ú0Ë0Ò6, 2 289, 0Ø0ë0Ä (l4 ) 2 294, 0Ø0ë0Ä7,
             56 (l4 ) 572, 576, 578, 580,       2 298, 400Ñ0ü0Ä 2 2 2 (eå ), 459, 2 2 286,
             581, 580Ñ0ü0Ä 584, 585, 586,       487, 2 2 292, 494, 2 2 295, 577,
             587, 588, 589, 595, 596,       5 50Õ0£0ü0È, 634, 5 50Ø0¯0¿0ü0ë, 639, 5 552,
             597, 600, 5 501, 60 (l4 ) 5 503        655, 5 568
          TABLE_TYPE, 542, 576, 578,     <temporary 4able
             586                            declaration>, 2 29, 2 2 26,
          TABLE_TYPE_NOT_NULL, 576          50Ñ0ü0Ä 56, 57, 58, 5 50, 5 5 5 (l4 )
          ! !target character set             262,  (Œ¡ )5, 281,  (Nã )6, 2 241,
             specification>, 2 2 (eå ),           0Ö0Ã0·0§0ë0Ñ0ü0Ä 2 297, 0Ø0ë0Ä8, 2 2 289, 49 (l4 )
             0Õ0£0ü0È5                            2 2 294, 495, 5 (ry ), 634, 5 50Ø0¯0¿0ü0ë,
          <target specification>, 10,
             5 5 (l4 ) 1,  5, 281,  (Nã )6,        639, 5 552
             0Õ0¡0é0Ã0É5, 2 247, 0Õ0é0ó0, 2 275, 0Ú0½7,    temporary view, 668
             2 280, 0Ú0Ë0Ò (l4 ) 2 283, 436, 2 2 20Ø0ë0Ä,    ! !term>, 157, ­8, 169
             451, 2 2 256, 457, 2 2 258, 460,    Terms denoting rule
             2 2 269, 470, 5 547, 667             requirements, 
          TARGET_CHARACTER_SET_          TEST, 85
                                         THEN, 85, 1, 142, 0Ó0ë4,
             CATALOG, 556, 610, 5 5          2 2­, 0Ó0ë8, 543, 544, 5 582
          TARGET_CHARACTER_SET_NAME,     THERE, 85
             556, 610, 5 5                TIME, 19, 29, 2 20, 2 21, 2 2 29,
          TARGET_CHARACTER_SET_SCHEMA       85, 90, 94, 1SA,  0,
             , 556, 5 510, 611                1 ,   (l4 ) 1 (g	 ), 0Ñ0ü0Ä 1 (Nã ),
          TEMPORARY, 2 27, 2 28, 85, 260,       ª9, 152, ¬0Ñ0ü0Ä 165, ­6,
              (Œ¡ )1, 2 297, 576, 577, 630Ñ0ü0Ä       167, 42 (l4 ) 2 2 2 (Nã ), 440, 2 2 246,
             5 582                            484, 571, 68 ( )
                                         <time fractional seconds
                                            0recision>, 2 20, 2 21, 1SA,
                                             0, 1 ,   (l4 ) 1 (Nã ), 658
                                         ! !time interval>, 91
                                         <time literal>, 90, 94, 96

                                                            Index  5 57

  


          <time precision>, 108, 110,    4ransaction, 7, 2 2 21, 2 2 25, 2 2 28,
              1, 1ª, ª9, 140, 426,       2 2 29, 50, 51, 5 (l4 ) 54, 55,
             450Ñ0ü0Ä 2 2 254, 630                  56, 58, 59, 5 50, 5 57, 5 58,
          TIMESTAMP, ,  (Nã ), 0Ô0³, 0Ó0ë,        5 59, 5 5 50, 5 5 51, 5 5 54, 5 5 55, 5 5 56,
             49, 85, 90, 94, 108,           253, 0Ö0Ã0·0§0ë9, 2 250, 0Ø0¯0¿0ü0ë8, 2 269,
             110,  1, 1 (g	 ), 0Ñ0ü0Ä 1 (Nã ),       0Ú0Ë0Ò4, 2 286, 0Ú0Ë0Ò9, 2 292, 0Ø0ë0Ä4,
             ª9, 153, ­6, 2 2 2 (Nã ), 440,       2 299, 400, 2 2 201, 400Ñ0ü0Ä 2 2 204,
             2 2 246, 571, 5 582                  405, 2 2 207, 410, 2 2 2, 420,
          ! !timestamp literal>, 90,          2 2 242, 448, 2 2 284, 486, 5 (ry ),
             94, 96                         526, 5 (y] ), 528, 5 50Õ0é0ó, 637,
          ! !timestamp precision>, 108,       5 50Ø0ë0Ä, 647, 5 548, 654, 5 555,
             110,  1, 1ª, ª9, 140,       66 (l4 ) 5 565, 668, 5 572, 677
             2 2 2 (Œ¡ ), 450Ñ0ü0Ä 2 2 254, 630          TRANSACTION, 85, 0Õ0é0ó0Ñ0ü0Ä 2 254,
          <timestamp string>, 82, 86,       0Õ0é0ó5, 2 299, 484, 5 582
             90                          <transaction access mode>,
          ! !time string>, 82, 90             2 299, 400
          <time value>, 90, 91, 96       4ransaction-initiating, 5 57,
          ! !time +one>, ­5, 166, ­7        2 249, 407, 2 2 210, 526, 5 (y] )
          ! !time +one field>, 8, 1 (Nã )    Transaction management, 0Ø0ë0Ä9
          <time zone interval>, 90,      ! !transaction mode>, 2 299
             94, 95, 96                  transaction resolution
          ! !time +one specifier>, ­5,       5nknown, 71, 620
             166, ­7                    4ransaction rollback, 5 59,
          TIMEZONE_HOUR, 0Ô0³, 85,   (l4 )       5 5 51, 253, 400Ñ0ü0Ä 2 2 204, 486,
             8, 10Ô0³, 68 (N  )                 5 5 (g	 ), 655, 5 562
          TIMEZONE_MINUTE, 0Ô0³, 85,       transaction states, 59
               (l4 ) 1 (R´ ), 68 (N  )              TRANSLATE, 85, 10Õ0¡0é0Ã0É, 68 ( )          TO, 0Ó0ë, 85, 0Ñ0ü0Ä 154, ­6,
             0, 2SD,  (y> )8, 20Ø0ë0Ä,  (T )0,
              (T )8, 2 2¬, 0Õ0¡0é0Ã0É0, 2 2 (h* ), 0Õ0¡0é0Ã0É9,
             0Õ0£0ü0È0, 2 20Ó0ë, 0Õ0£0ü0È (l4 ) 2 249, 407,
             42 (l4 ) 2 2 20Ô0³, 441, 2 2 297, 499,
             527
          <token>, 8 (l4 ) 86, 2 2 291
          ! !token> and ! !separator>, 82
          TRAILING, 85, 10Õ0¡0é0Ã0É, ª6, 5 582


          5 58  Database Language SQL

 
          4ranslation, 7, 2 (l4 ) 2 2 24, 50Ñ0ü0Ä    TRANSLATIONS_CHECK_
             5 54, 5 55, 5 56, 5 5 56, 99, 103,       REFERENCES_SOURCE, 5 510
             104, 10Õ0¡0é0Ã0É, ª4, 10Õ0é0ó, ª6,    TRANSLATIONS_CHECK_
             10Ú0½,  (ry )5, 256,  (ry )7, 258,       REFERENCES_TARGET, 5 5 
              (ry )9, 2 202, 0Ó0ë4, 2 2­, 0Õ0¡0é0Ã0É0,    TRANSLATIONS_FOREIGN_KEY_
             2 2 (h* ), 0Õ0¡0é0Ã0É (l4 ) 2 2 (y> ), 0Õ0¡0é0Ã0É4, 2 2 (Nã ),       SCHEMATA, 610
             2 20Ó0ë, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5, 2 20Ø0¯0¿0ü0ë,    TRANSLATIONS_PRIMARY_KEY,
             0Õ0£0ü0È7, 2 268, 444, 2 2 283, 484,       5 510
             556, 5 505, 610, 5 5 , 630,    TRANSLATIONS_SOURCE_
             63 (l4 ) 5 50Ö0Ã0·0§0ë, 635, 5 50Ú0½, 639,       CHARACTER_SET_CATALOG_
             5 559, 661                       NOT_NULL, 610
          TRANSLATION, 85, 259, 0Ó0ë4,     TRANSLATIONS_SOURCE_
             2 2 (eå ), 0Õ0¡0é0Ã0É1, 2 2 (y> ), 0Õ0¡0é0Ã0É9, 2 20Ó0ë,       CHARACTER_SET_NAME_
             2 20Õ0¡0é0Ã0É, 480Ñ0ü0Ä 2 2 284, 556, 5 504,       NOT_NULL, 610
                                         TRANSLATIONS_SOURCE_
             5 505, 610, 5 5 , 634, 5 582        CHARACTER_SET_SCHEMA_
          <translation collation>,          NOT_NULL, 610
             2 2, 0Ó0ë6, 2 2 (y> )               TRANSLATIONS_TARGET_
          <translation definition>,         CHARACTER_SET_CATALOG_
             53,  (ry )5, 257, 0Õ0¡0é0Ã0É0, 2 2 (h* ),        NOT_NULL, 5 510
             0Õ0¡0é0Ã0É (l4 ) 2 20Ó0ë, 0Õ0£0ü0È5, 2 268, 484,    TRANSLATIONS_TARGET_
             63 (l4 ) 5 50Ö0Ã0·0§0ë, 635, 5 50Ú0½, 639        CHARACTER_SET_NAME_
          4ranslation descriptor, 2 (l4 )       NOT_NULL, 5 510
             44, 0Ó0ë0Ñ0ü0Ä 2 2 (h* )                TRANSLATIONS_TARGET_
          ! !translation name>, 2 (l4 ) 99,       CHARACTER_SET_SCHEMA_
             100Ñ0ü0Ä 104, ª (l4 ) 10Ö0Ã0·0§0ë, ª5,       NOT_NULL, 5 510
              (ry )9, 2 202, 0Ó0ë4, 2 2­, 0Õ0¡0é0Ã0É0,    TRANSLATION_CATALOG, 556,
             2 2 (h* ), 0Õ0¡0é0Ã0É0Ñ0ü0Ä 2 2 (Nã ), 0Õ0£0ü0È1, 2 20Õ0£0ü0È,       604, 5 510, 611
             2 20Õ0é0ó, 630                    TRANSLATION_NAME, 556, 604,
          TRANSLATIONS, 556, 604,           5 510, 611
             5 510, 611                    TRANSLATION_SCHEMA, 556,
          TRANSLATIONS base table,          604, 5 510, 611
             5 510                         TRIGGER, 85
          ! !translation source>, 2 2 (eå )      triggered data change
          <translation specification>       violation, 279, 486,
             , 0Õ0¡0é0Ã0É0                          5 5 (g	 )
          TRANSLATIONS view, 556


                                                            ! ?ndex  69

 
          TRIM, 85, 10Õ0¡0é0Ã0É, ª4, 152,       Type conversions and mixing
             153, ¬4, 2 253, 407, 2 2 2SA,       of data types, 2 24
             2 2 2¬, 417, 2 2 2, 420, 2 2 20Ó0ë,               - U -
             2 2 247, 465, 5 582               UNCOMMITTED, 68, 69, 84,
          <trim character>, ª (l4 ) 10Ö0Ã0·0§0ë,       0Ø0ë0Ä9, 2 2 200
             ª6, 2 2 244                    UNDER, 85
          trim error, ª6, 5 5 (h* )           5nderlying column,  (l4 )
          ! !trim function>,  (g	 ), ª (l4 )         155, 7, 192,  (eå )0, 201,
             10Ö0Ã0·0§0ë, ª6, 10Ú0½, ª8, 2 2 244,        (Nã )7, 298, 0Õ0£0ü0È1
             5 541                         5nderlying data 4ype, 144
          ! !trim operands>, ª (N  )          underlying 4able, 0Ú0½, 0Ú0Ë0Ò,
          <trim source>, 10Õ0¡0é0Ã0É, ª4,          0Ñ0ü0Ä 200,  (Nã )8, 299, 0Õ0£0ü0È0,
             ª6, 2 2 244                       2 20Ö0Ã0·0§0ë, 0Ú0½ (l4 ) 2 284, 0Ú0Ë0Ò7, 2 289,
          <trim specification>, ª (l4 )        0Ø0ë0Ä0, 2 291, 0Ø0ë0Ä (l4 ) 2 296, 47 (l4 )
             ª4, 10Ø0¯0¿0ü0ë                       2 2 274, 476, 2 2 277
          TRUE, 85, 2 (Nã ),  (y> )0, 2 256,       <underscore>, 80, 81, 82,
             5 582                            87, 88, 89, 98, 101,
          Truth 4able for 4he AND           2¬, 629
             boolean,  (y> )0                UNION, 85, 6, 180, 1,
          Truth 4able for 4he ! ?S            182, 0Ñ0ü0Ä 184, 6, 197,
             boolean,  (y> )0                    (eå )0, 201,  (eå ) (l4 ) 2SA, 54 (l4 )
          Truth 4able for 4he OR
             boolean,  (y> )0                   559, 561, 57 (l4 ) 586, 590Ñ0ü0Ä
          ! !truth value>,  (g	 )9, 20Ô0³,          5 504, 616, 5 50Ó0ë, 640Ñ0ü0Ä 5 570
             63 (N  )                        UNIQUE, 41, 85,  (g	 )0Ñ0ü0Ä 2 (T ),
          TYPE, 84, 85, 0Õ0é0ó (l4 ) 2 253,            (g	 )5, 270,  (y] ) (l4 ) 273, 550,
             0Õ0é0ó4, 2 255, 0Õ0é0ó6, 2 2 2 (ry ), 426,       559, 580, 585, 586, 587,
             2 2 2 (y] ), 434, 2 2 20Ø0¯0¿0ü0ë, 439, 2 2 240,       588, 590, 591, 5 5­, 617,
             441, 2 2 252, 450Ñ0ü0Ä 2 2 254, 455,       5 5, 645
             2 2 256, 457, 2 2 258, 500, 502,    ! !unique column list>, 2 2 21,
             539, 542, 544, 545, 546,       270,  (y] ) (l4 ) 273,  (y] )5, 5 545
             547, 548, 549, 554, 555,    unique constraint, 2 2 21, 2 2 2 ( )             556, 570, 571, 57 (l4 ) 573,    ! !unique constraint
             576, 578, 580, 581, 585,       definition>, 2 26, 270,
             586, 587, 588, 590, 591,        (y] ) (l4 ) 273,  (y] )5, 5 577
             600, 5 501, 60 (l4 ) 5 503, 604,    unique matching rows,  (y] )7,
             605, 5 5, 660Ñ0ü0Ä 5 564             278,  (y] )9

          Type conversions, 2 24

          5 5 50  Database Language SQL

 
          ! !unique 0redicate>, 205,       <unsigned numeric literal>,
             20,  (g	 )0Ñ0ü0Ä 5 543, 644             82, 89, 90
          ! !unique specification>, 2 26,    <unsigned value specifi-
              (Œ¡ ) (l4 ) 264,  (y] ) (N  )                 cation>,  4, 1¬,  6,
          UNIQUE_CONSTRAINT_CATALOG,        155
             550, 559, 590, 591, 617     unterminated C string, 2 263,
          UNIQUE_CONSTRAINT_CATALOG_        621
             NOT_NULL, 590               ! !updatability clause>, 0Ú0½1,
          UNIQUE_CONSTRAINT_CHECK_          2 272, 0Ú0½0Ñ0ü0Ä 2 274, 0Ø0ë0Ä (l4 ) 2 2 264,
             REFERENCES_UNIQUE_             474, 5 50Õ0é0ó, 638, 5 547
             CONSTRAINT, 591             updatable, 2 28, 2 2 20, 50, 1,
          UNIQUE_CONSTRAINT_NAME,           0Ñ0ü0Ä 195, 7, 296,  (Nã )7,
             550, 559, 590, 591, 616,       298,  (Nã )9, 2 20Ô0³, 0Õ0£0ü0È4, 2 272,
             5 5                            0Ú0½0Ñ0ü0Ä 2 284, 0Ø0ë0Ä1, 2 294, 467,
          UNIQUE_CONSTRAINT_NAME            2 2 272, 474, 579, 640ª0ü0à             assertion, 616              UPDATE, 5 54, 5 56, 85, 245,
          UNIQUE_CONSTRAINT_NAME_NOT_        (T )6, 261,  (y] )4, 284,  (R´ )9,
             NULL, 590                      298, 0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ö0Ã0·0§0ë,
          UNIQUE_CONSTRAINT_SCHEMA,         0Ú0½1, 2 272, 0Ú0½0Ñ0ü0Ä 2 274, 0Ø0ë0Ä1,
             550, 559, 590, 591, 617        2 292, 0Ø0ë0Ä4, 2 298, 464, 2 2 274,
          UNIQUE_CONSTRAINT_SCHEMA_         477, 2 2 283, 484, 550, 590,
             NOT_NULL, 590                  591, 600, 5 501, 60 (l4 ) 5 503,
          UNIQUE_TABLE_PRIMARY_KEY_
             CHECK, 586                     635, 5 50Ú0Ë0Ò
          UNKNOWN, 85,  (g	 )9, 20Ô0³, 0Õ0é0ó0Ñ0ü0Ä    update operation,  (Nã )9
             2 255, 68 (N  )                   ! !update rule>,  (y] )4, 276,
          UNNAMED, 84, 2 2 2 (y] ), 434, 2 2 20Ø0¯0¿0ü0ë,        (y] )8, 279,  (R´ )0, 5 50Õ0£0ü0È
             438, 2 2 252, 450Ñ0ü0Ä 2 2 254, 67 (N  )    <update source>, 1,  (l4 )
          5nordered collection, 5 5           2 291, 0Ø0ë0Ä (l4 ) 2 293, 0Ø0ë0Ä5, 2 296,
          <unqualified schema name>,        474, 5 548
             98, 101, 102,  (ry )6, 2 2 2,     <update statement:
             486, 2 2 287, 530µ0ó0Á0ü0à                 0ositioned>, 50, 53,
          <unsigned integer>, 90, 91,       55, 57, 59, 60,  (y] )9,
             92, 96, 108, 148, ¬0,         299, 0Ø0¯0¿0ü0ë9, 2 285, 0Ú0Ë0Ò7, 2 291,
             20Ø0ë0Ä, 0Ú0½1, 2 272, 497, 2 2 298,       0Ø0ë0Ä (l4 ) 2 293, 0Ø0ë0Ä5, 2 2 275, 477,
             499, 50Ô0³, 629, 5 575             2 2 284, 648
          <unsigned literal>, 89,
             1, 629, 5 540


                                                            ! ?ndex  71

 
          ! !update statement:             USAGE_PRIVILEGES_IS_
             searched>, 50Ñ0ü0Ä 55, 56,         ? ?RANTABLE_CHECK, 604
             58, 5 50, 1,  (l4 ) 299,      USAGE_PRIVILEGES_IS_
             2 269, 0Ú0Ë0Ò5, 2 292, 0Ø0ë0Ä4, 2 296,       GRANTABLE_NOT_NULL,
             2 2 242, 484, 2 2 285, 525, 5 548,       604
             5 573                         USAGE_PRIVILEGES_OBJECT_
          UPDATE_RULE, 550, 590, 591        TYPE_CHECK, 604
          UPPER, 2 (l4 ) 85, 10Õ0¡0é0Ã0É, ª5,       USAGE_PRIVILEGES_PRIMARY_
             68 (N  )                           KEY, 604
          upper case,  (g	 ), 81, 87,        Use of terms, 10
             10Õ0é0ó, ª6, 50, 534, 5 5,    USER, 85, 1,  5, 1,
             5 566                             (Œ¡ )6, 2 2 207
          USAGE, 65, 66, 85, ª5,        <user-defined character
             145,  (T )5, 248,  (T )9, 251,       repertoire name>,  (T )8,
              (Œ¡ )4, 2 202, 0Ó0ë0, 2 2, 0Ó0ë0Ñ0ü0Ä       249
             0Ó0ë5, 2 2­, 0Ó0ë8, 2 2 (h* ), 0Õ0¡0é0Ã0É0Ñ0ü0Ä    <user name>, 5 5 5 (l4 ) 99, 103,
             2 2 (Nã ), 0Õ0£0ü0È0, 2 20Ó0ë, 0Õ0£0ü0È0Ñ0ü0Ä 2 20Ø0¯0¿0ü0ë,       407, 2 2 2SA, 409, 5 562
             0Õ0£0ü0È7, 2 258, 0Õ0é0ó9, 5SA, 510,    USERS, 568, 569, 5 500, 60 (l4 )
             530Ñ0ü0Ä 50Ø0ë0Ä, 548, 552, 554,       5 505
                                         USERS base 4able, 568
             555, 556, 557, 558, 559,    USERS_PRIMARY_KEY, 568
             561, 56 (l4 ) 583, 584, 588,    USER_NAME, 568
             595, 596, 5 504, 605, 5 5,    USING, 85, ª (l4 ) 180, 0Õ0é0ó4,
             618, 5 540, 664, 5 582             2 2 251, 539, 561, 618, 5 582
          5sage 0rivilege descriptor,    <using arguments>, 2 2 251,
             5 56                             455, 2 2 256, 457, 2 2 259, 469,
          USAGE_PRIVILEGES, 50Ø0ë0Ä, 548,       2 2 270
             554, 555, 556, 5 504, 605,    <using clause>, 451, 2 2 255,
             5 540                            456, 2 2 257, 459, 2 2 267, 469
          USAGE_PRIVILEGES base table    5sing clause does not
             , 604                          match dynamic 0arameter
          USAGE_PRIVILEGES view, 548        specifications, 2 2 255, 621
          USAGE_PRIVILEGES_CHECK_        5sing clause does not match
             REFERENCES_OBJECT, 5 504         4arget specifications,
          USAGE_PRIVILEGES_GRANTEE_         457, 5 5 (h* )
             FOREIGN_KEY_USERS, 5 505      using clause required for
          USAGE_PRIVILEGES_GRANTOR_         dynamic parameters, 460,
             FOREIGN_KEY_USERS, 5 505         2 2 267, 621


          72  Database Language SQL

  


          using clause required for      ! !value specification>,  4,
             result fields, 2 2 260, 621        1¬,  6, 2ª,  (h* )7, 282,
          <using descriptor>, 450,          0Õ0¡0é0Ã0É5, 2 247, 0Ú0½5, 2 290, 415,
             451, 2 2 255, 456, 2 2 257, 459,       2 2 2, 419, 2 2 2 (eå ), 444, 2 2 246,
             2 2 260, 469                       447, 5 (ry ), 530, 5 50Õ0¡0é0Ã0É, 64 (l4 )
          UTC, 5, 2 21, 2 2 (l4 ) 96, 1 (y> ),          5 543, 658, 5 565
             ­7                         <value specification> and

                      - V -                 ! !target specification>,
          Valid operators involving         1
             datetimes and intervals,    VARCHAR, 85, 107, 108, 1ª,
             2 24                             504, 505, 506, 507, 515,
          Valid 6alues for fields in        5­, 640, 5 551, 664, 5 582
             datetime items,   (N  )        variable, ,  (y> ),  (T ), 47,
          Valid values for fields in        48, 49, 59, 61, 62, 63,
             ! ?NTERVAL items, 2 2 (l4 ) 1         4, 1¬,  6, 192, 44 (l4 )
          6alue,                          2 2 243, 451, 2 2 262, 489, 2 2 290,
          VALUE, 2 26, 85, 1,  5,          49 (l4 ) 2 2 293, 494, 2 2 295, 496,
              6, 2 2SD, 434, 2 2 20Ú0Ë0Ò, 509,       2 2 297, 498, 2 2 299, 500, 501,
             565, 641, 5 564, 68 (N  )            50 (l4 ) 504, 505, 50, 507,
          ! !value expression>, 1,          5SA, 509, 510, 51 (l4 ) 5ª,
             1 (g	 ), 4, 1 (ry ), 6, 1 (y] ),       514, 5¬, 516, 5, 518,
             1, 142, 4, 145, ¬5,       5, 520, 5 (h* ), 52 (l4 ) 5 (ry ),
             156, 0Ñ0ü0Ä 176, 1, 185,       630, 5 50Ø0ë0Ä, 651, 5 555, 664,
             6, 187, 1, 192, 0Ñ0ü0Ä       5 573
             4, 2,  (h* )0Ñ0ü0Ä 2 282, 0Ø0ë0Ä1,    VARIABLE, 85
             0Ø0ë0Ä (l4 ) 2 293, 0Ø0ë0Ä4, 2 295, 0Ø0ë0Ä6,    variable-length, 8iii, 5 5 56,
             440Ñ0ü0Ä 2 2 244, 445, 2 2 246, 447,       1SD,  5, 10Õ0£0ü0È, ª4, 145,
             2 2 274, 475, 5 50Ô0³, 63 (l4 ) 5 50Ø0¯0¿0ü0ë,       8, 149, ¬0, 151, ¬ (l4 )
             641, 5 542, 640Ñ0ü0Ä 5 548, 677        161, ­ (l4 ) 163,  (h* )6, 20Õ0¡0é0Ã0É,
          <value expression primary>,        (y> )4, 20Õ0é0ó,  (y> )7, 266,  (Œ¡ )8,
             ¬5, 156, ¬7, 160, ­1,       2 265, 0Ø0¯0¿0ü0ë6, 50, 516, 564,
             165, ­8, 5 542                  658, 5 563
          VALUES, 85, 176,  (h* ) (l4 ) 2 288,     variable-length coding, 5,
             574, 578, 586, 598, 648        5 5

                                         ! !variable specification>,
                                            1,  5, 1­, 525


                                                            Index  5 5 50ª0ü0à
  


          VARYING, 19, 20, 26, 2 25,       VIEW, 85, 258,  (Nã )0, 296,
             85, 107, 108, 1SD,  0Ñ0ü0Ä        0Ô0³0, 2 20Ú0Ë0Ò, 480Ñ0ü0Ä 2 2 284, 538,
              (Œ¡ )0Ñ0ü0Ä 2 201, 0Õ0é0ó1, 2 257, 0Ø0¯0¿0ü0ë0,       50Ø0ë0Ä, 541, 542, 540Ñ0ü0Ä 544,
             2 261, 0Ø0¯0¿0ü0ë (l4 ) 2 263, 0Ø0¯0¿0ü0ë4, 2 265,       546, 547, 548, 549, 550,
             0Ø0¯0¿0ü0ë6, 2 267, 425, 2 2 2 (Œ¡ ), 429,       551, 55 (l4 ) 553, 554, 555,
             2 2 240, 445, 2 2 247, 458, 50,       556, 557, 558, 559, 561,
             516, 5 (eå ), 521, 5 (g	 ), 520Ñ0ü0Ä       562, 560Ñ0ü0Ä 576, 577, 578,
             564, 570, 5 50Õ0é0ó, 639, 5 540,       579, 583, 584, 586, 640
             5 547, 651, 5 582               ! !view column list>, 296,
          <vertical bar>, 80, 81             (Nã )7, 2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5
          view, 10,  , 0Ú0½, 0Ú0Ë0Ò, 0Ø0ë0Ä,      ! !view definition>,  , 0Ú0½,
             2 2 20, 2 2 24, 2 2 25, 5 (l4 ) 5 54, 5 57,        52,  9, 255,  (Nã )6, 297,
             5 5 55, 5 5 57, 1, 7, 179,          (Nã )9, 2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5, 2 268, 484,
             5, 203,  (ry )5, 256,  (ry )8,       579, 646
             267,  (Œ¡ )8, 284,  (R´ )9, 290,    6iew descriptor, 0Ø0ë0Ä, 40,
             294,  (Nã )6, 297,  (Nã )9, 2 200,       44,  (R´ )4, 289,  (Nã )4, 297,
             2 2SD, 0Ó0ë8, 2 2 (y> ), 0Õ0¡0é0Ã0É6, 2 20Ô0³,        (Nã )9, 2 200, 0Ó0ë0Ñ0ü0Ä 2 2, 0Õ0¡0é0Ã0É0Ñ0ü0Ä
             0Õ0£0ü0È1, 2 20Ö0Ã0·0§0ë, 0Õ0£0ü0È5, 2 20Ø0¯0¿0ü0ë, 0Õ0£0ü0È7,       2 2 (Œ¡ ), 0Õ0£0ü0È6, 2 20Ú0Ë0Ò, 578, 581
             0Õ0£0ü0È8, 2 268, 0Ú0Ë0Ò0Ñ0ü0Ä 2 289, 0Ø0ë0Ä0Ñ0ü0Ä    viewed 4able, 10, 0Ú0½, 0Ú0Ë0Ò,
             2 295, 0Ø0ë0Ä8, 2 2 283, 484, 2 2 287,       67, 75,  (Nã )6, 2 200, 540Ñ0ü0Ä
             530Ñ0ü0Ä 50Ú0Ë0Ò, 539, 540, 541,       557, 558, 577, 578, 5 568
             54 (l4 ) 543, 544, 546, 547,    VIEWS, 543, 576, 578, 580Ñ0ü0Ä
             548, 549, 550, 551, 55 (l4 )       584, 586, 5 540
             550Ñ0ü0Ä 554, 555, 556, 557,    VIEWS base 4able, 578
                                         VIEWS 6iew, 543
             558, 559, 560, 561, 56 (l4 )    VIEWS_IN_TABLES_CHECK, 578
             560Ñ0ü0Ä 576, 577, 578, 579,    VIEWS_IS_UPDATABLE_CHECK_
             581, 580Ñ0ü0Ä 584, 631, 5 50Õ0¡0é0Ã0É,       OPTION_CHECK, 578
             5 50Õ0£0ü0È, 635, 5 543, 646, 5 552,    VIEWS_PRIMARY_KEY, 578
             5 567, 668, 5 577, 678          VIEW_CATALOG, 557, 558,
                                            583, 584
                                         VIEW_COLUMN_USAGE, 558,
                                            584, 640
                                         VIEW_COLUMN_USAGE base
                                            table, 584
                                         VIEW_COLUMN_USAGE view, 558
                                         VIEW_COLUMN_USAGE_CHECK_
                                            REFERENCES_COLUMNS, 584


          74  Database Language SQL

  


          VIEW_COLUMN_USAGE_FOREIGN_     2 2 2 2HERE, 85, 5, 271,  (y] )0Ñ0ü0Ä
             KEY_VIEWS, 584                 2 203, 0Ú0Ë0Ò4, 2 286, 0Ø0ë0Ä1, 2 294,
          VIEW_COLUMN_USAGE_PRIMARY_        47 (l4 ) 2 2 274, 476, 2 2 277, 480Ñ0ü0Ä
             KEY, 584                       2 2 284, 485, 50Ú0Ë0Ò, 539, 541,
          VIEW_DEFINITION, 543, 578,        54 (l4 ) 543, 544, 545, 546,
             579                            547, 548, 549, 550, 551,
          VIEW_NAME, 557, 558, 583,         55 (l4 ) 553, 554, 555, 556,
             584                            557, 558, 559, 561, 562,
          VIEW_SCHEMA, 557, 558, 583,       576, 578, 586, 588, 591,
             584                            5 5, 618
          VIEW_TABLE_USAGE, 557, 583,    ! !where clause>, 1, 7,
             640                            185, 7, 189, 0Ñ0ü0Ä 195,
          VIEW_TABLE_USAGE base table
             , 583                          631, 5 543
          VIEW_TABLE_USAGE view, 557     WHILE, 85
          VIEW_TABLE_USAGE_CHECK_        2 2 2 2ITH, 29, 2 20, 2 21, 5 55, 5 5 55,
             REFERENCES_TABLES, 583         85, 94, 1SA,  0, 1 ,
          VIEW_TABLE_USAGE_FOREIGN_           (l4 ) 1 (g	 ), 0Ñ0ü0Ä 1 (Nã ), ª9,
             KEY_VIEWS, 583                 153,  (T )8, 296,  (Nã )7, 299,
          VIEW_TABLE_USAGE_PRIMARY_         0Õ0¡0é0Ã0É9, 2 20Ô0³, 0Õ0£0ü0È1, 2 256, 0Ú0Ë0Ò9,
             KEY, 583                       2 293, 0Ø0ë0Ä5, 2 2 2 (Nã ), 431, 2 2 240,
          VIRTUAL, 85                       446, 2 2 287, 530Ñ0ü0Ä 571, 579,
          6isible, 50, 51, 70, 668          5 501, 600Ñ0ü0Ä 5 505, 660Ñ0ü0Ä 5 577
          VISIBLE, 85                    WITH CHECK OPTION, 5 5 55, 297,

                      - 2 2 2 2 -                 2 289, 0Ø0ë0Ä0Ñ0ü0Ä 2 295, 677
          WAIT, 85                       7ith check option 6iolation
          7arning, 47, 67, 6, 148,        , 299, 487, 5 5 (y> )
             9, 151, ¬ (l4 ) 20Õ0¡0é0Ã0É,  (Œ¡ )8,    WITH ? ?RANT OPTION, 5 5 55, 248,
             279,  (R´ ) (l4 ) 299, 0Õ0¡0é0Ã0É6, 2 20Õ0¡0é0Ã0É,       0Õ0£0ü0È0, 2 20Ó0ë, 530ª0ü0à             2 20Ú0Ë0Ò, 0Õ0é0ó1, 2 285, 0Ú0Ë0Ò7, 2 292,    2 2 2 2ITHOUT, 85
             0Ø0ë0Ä5, 2 2 2ª, 45 (l4 ) 2 2 253, 486,    WORK, 85, 400Ñ0ü0Ä 2 2 204, 405,
             528, 5 5 (g	 )                       2 2 282, 484, 5 548, 649
          WHEN, 85,  (l4 ) 543, 544,       2 2 2 2RITE, 85, 0Ø0ë0Ä9, 2 2 200, 68 ( )
             68 ( )          WHENEVER, 85, 497
          <when operand>, 1, 142,
             2 2 244, 446

                                                            ! ?ndex  75

 
                      - Y -              <years 6alue>, 91, 94, 95,
          YEAR, 2 20, 2 21, 2 2 (l4 ) 2 20Ñ0ü0Ä 85,         241

             95, 1 ,   (l4 ) 20Ú0Ë0Ò,  (y> )9,                - Z -
             240, 430, 2 2 245, 560Ñ0ü0Ä 5 5,    ZONE, 29, 2 20, 2 21, 85, 94,
             610Ñ0ü0Ä 5 582                       1SA,  0, 1 ,   (l4 ) 1 (g	 ),
          <year-month literal>, 91,         0Ñ0ü0Ä 1 (Nã ), ª9, 153, ­5,
             95,  (T )1                        2 2 2 (g	 ), 429, 2 2 240, 446, 2 2 284,

                                            571, 680ª0ü0à


          76  Database Language SQL
 < / d i v > < d i v   c l a s s = " n a k e d _ c t r l " > 
 < f o r m   a c t i o n = " / i n d e x . c g i / s p e e c h "   m e t h o d = " g e t "   n a m e = " g a t e " > 
 < p > < a   h r e f = " h t t p : / / a l t s t y l e . a l f a s a d o . n e t " > A l t S t y l e < / a >  0k0ˆ0c0fY	cÛ0U0Œ0_0Ú0ü0¸   < a   h r e f = " h t t p : / / w w w . c o n t r i b . a n d r e w . c m u . e d u / ~ s h a d o w / s q l / s q l 1 9 9 2 . t x t " > ( - & g t ;0ª0ê0¸0Ê0ë ) < / a > 
 /   < l a b e l >0¢0É0ì0¹ :   < i n p u t   t y p e = " t e x t "   n a m e = " n a k e d _ p o s t _ u r l "   v a l u e = " h t t p : / / w w w . c o n t r i b . a n d r e w . c m u . e d u / ~ s h a d o w / s q l / s q l 1 9 9 2 . t x t "   s i z e = " 2 2 "   / > < / l a b e l >   < l a b e l >0â0ü0É :   < s e l e c t   n a m e = " n a k e d _ p o s t _ m o d e " > 
 < o p t i o n   v a l u e = " d e f a u l t " >0Ç0Õ0©0ë0È < / o p t i o n > 
 < o p t i o n   v a l u e = " s p e e c h "   s e l e c t e d = " s e l e c t e d " >—óXð0Ö0é0¦0¶ < / o p t i o n > 
 < o p t i o n   v a l u e = " r u b y " >0ë0ÓNØ0M < / o p t i o n > 
 < o p t i o n   v a l u e = " c o n t r a s t " >‘M‚rSÍŽâ < / o p t i o n > 
 < o p t i o n   v a l u e = " l a r g e r - t e x t " >e‡[WbáY' < / o p t i o n > 
 < o p t i o n   v a l u e = " m o b i l e " >0â0Ð0¤0ë < / o p t i o n > 
 < / s e l e c t > 
 < i n p u t   t y p e = " s u b m i t "   v a l u e = "ˆhy: "   / > 
 < / p > 
 < / f o r m > 
 < / d i v > 	 	 