Additional information available:

$@ALTERATTACHBEGIN_DECLARECLOSE
COMMENT_ONCOMMITCONNECTCREATEDBKEYDECLARE
DELETEDESCRIBEDISCONNECTDROPEDITEND_DECLARE
EXECUTEEXECUTE_IMMEDIATEEXITEXPORTFETCHFINISH
GRANTHELPIMPORTINCLUDEINSERTINTEGRATE
LSENULLOPENPREPAREPRINTQUITRELEASE
REVOKEROLLBACKRUN_TIME_ONLY_KITSELECTSETSET_ALIAS
SET_ALL_CONSTRAINTSET_ANSISET_CATALOGSET_CONNECT
SET_SCHEMASET_TRANSACTIONSHOWSQLCASQLDA
UPDATEUSERWHENEVER

aliasarith expressionauthorization idcol select expr
Command recallcorrelation namedatabase handleData Distributor
data typesDCL invokedefault databaseDynamic SQLDyn DECLARE CURSOR
Dyn FETCHDyn INSERTDyn OPENErrorExecute(@)Ext Dyn DEC CURSOR
FunctionsGRANT ANSI styleInteractive kitLinking programs
literalsModule languageNew featuresPrecompilerpredicateRelease Notes
REVOKE ANSI styleSample Databasesselect exprsingleton select
Value expression

 An alias is a name that identifies a particular attachment to a
 database so that your program or interactive SQL statements can refer
 to more than one database.

 You can specify the alias in an ATTACH, CONNECT, CREATE DATABASE or
 DECLARE ALIAS statement.  (Specify an alias in addition to the file
 specification or a data dictionary path name that you supply in these
 statements.) An alias must be no longer than 25 characters.

 Once you specify an alias, you must use it when referring to the
 database in subsequent SQL statements (unless those statements are
 within a CREATE DATABASE statement).  You must use an alias when you
 declare more than one database.

 DIGITAL proprietary database languages (such as RDO in Rdb/VMS) use
 the term database handle instead of alias.  The two terms mean the
 same thing.

Additional information available:

Examples

 Example 1:  Qualifying domain names

 This example attaches to a PERSONNEL database by the alias CORPORATE
 and creates a domain within PERSONNEL.  When you create a domain for
 a database that you have attached to using an alias, you must qualify
 the domain name with that alias.

 SQL> ATTACH 'ALIAS CORPORATE FILENAME DISK01:[DEPT3]PERSONNEL';
 SQL> CREATE DOMAIN ADDRESS_DATA2_DOM CHAR(20) DEFAULT NULL;
 %SQL-F-NODEFDB, There is no default database
 SQL> CREATE DOMAIN CORPORATE.ADDRESS_DATA2_DOM CHAR(20) DEFAULT NULL;
 SQL> SHOW DOMAINS;
 User domains in database with alias CORPORATE
 ADDRESS_DATA2_DOM               CHAR(20)
 SQL>
 Example 2:  Qualifying catalog names in a multischema database

 When you use the alias to qualify the name of a catalog, you must
 separate the alias from the catalog name with a period and use double
 quotation marks to delimit the name pair, as follows:

 SQL> SET ANSI QUOTING ON;
 SQL> SHOW DOMAIN "CORPORATE.MARKETING".DEPT1.LAST_NAME;

 An arithmetic expression is a value expression formed by combining
 value expressions with arithmetic operators.  When you use an
 arithmetic expression in a statement, SQL calculates the value
 associated with the expression and uses that value when executing the
 statement.  Therefore, an arithmetic expression must be reducible to
 a value.

 If either operand of an arithmetic expression is a null value, the
 resulting value is also null.

 Select More_Information to continue.

Additional information available:

Date and time arithmeticMore Information

 The list of legal date arithmetic operations and their results
 follows:

 Operand1     Operator        Operand 2    Result Type

 date-time      - (subtract)  date-time     interval
 date-time      + or -        interval      date-time
 interval       +             date-time     date-time
 interval       + or -        interval      interval
 interval       * or /        numeric       interval
 interval       /             numeric       interval
                - (negate)    interval      interval

 The arithmetic operators and their functions are:

 +       Add
 -       Subtract
 *       Multiply
 /       Divide

 You can use parentheses to control the order in which SQL performs
 arithmetic operations.  SQL follows the normal rules of precedence.
 That is, it evaluates arithmetic expressions in the following order:

 1.  Value expressions in parentheses

 2.  Multiplication and division, from left to right

 3.  Addition and subtraction, from left to right

 When you issue a CREATE SCHEMA statement (alone or as part of a
 CREATE DATABASE statement), you must specify either a schema name or
 an authorization identifier.  If you wish to comply with the ANSI/ISO
 standard, you must specify an authorization identifier.

 An authorization identifier is a user name that SQL uses for
 privilege checking when you specify ANSI_AUTHORIZATION in the
 precompiler or module language command line options.  Under ANSI
 privilege checking, SQL restricts access to the schema to that user
 whose user name matches the authorization identifier.

 col-select-expr =

 ─┬─┬─> col-select-clause ─┬─┬────────────────────┬─┐
  │ └─>( col-select-expr )─┤ └─> order-by-clause ─┘ │
  │ ┌─────────<────────────┘                        │
  │ └─> 
U
N
I
O
N ─┬───────┬────┐                       │
  │            └> 
A
L
L ─┘    │                       │
  └────────<────────────────┘                       │
  ┌─────────────────────────────────────────────────┘
  └─┬────────────────────┬───────────────────────────>
    └─> limit-to-clause ─┘

Additional information available:

UNION

col select clauseMore Information

 col-select-clause =

 SELECT ─┬──────>──────┬─┬─> typebox (*) ─────────────────────────────┬ 
F
R
O
M ┐
         ├─> 
A
L
L ──────┤ ├─> table-name ───────┬─> .typebox (*) ──────┤      │
         ├─> 
D
I
S
T
I
N
C
T ─┘ ├─> view-name ────────┤            │      │
         │               ├─> correlation-name ─┘            │      │
         │               └─> value-expr ────────────────────┤      │
         └┬──────┬─┬───> 
S
U
M ───┬┬─> (
D
I
S
T
I
N
C
T column-name) ┤      │
          ├─> typebox (+) ─┤ ├───> 
A
V
G ───┤└─> (typebox (A)typebox (L)typebox (L) value-expr) ──────┤      │
          └─> - ─┘ ├───> 
M
A
X ───┤                           │      │
                   ├───> 
M
I
N ───┘                           │      │
                   └───> 
C
O
U
N
T ─┬──> (typebox (*)) ───────────────────┤      │
                                └──> (
D
I
S
T
I
N
C
T column-name) ┘      │
   ┌────────────────────────────────<──────────────────────────────┘
   └┬┬─> table-name ┬┬────────────────────┬┬─┬────────>───────────┬┐
    │└─> view-name ─┘└─> correlation-name ┘│ └─> 
W
H
E
R
E predicate ─┘│
    └────────── , <────────────────────────┘                       │
   ┌──────────────────────────────<────────────────────────────────┘
   └┬─────────────>──────────────────┬─┬──────────>──────────┬──>
    └─> 
G
R
O
U
P 
B
Y ─┬─> column-name ─┬─┘ └─> 
H
A
V
I
N
G predicate ─┘
                  └─────── , <─────┘

 The UNION operator merges the results of a select expression or
 select clause with another select expression or select clause into
 one result table by appending the values of columns in one table with
 the values of columns in other tables.

Additional information available:

ALL

 The ALL qualifier specifies that duplicate rows should not be
 eliminated from the result table.

 A column select expression is a select expression that specifies a
 one-column result table.  Column select expressions cannot specify a
 list of select items.

 SQL accepts a column select expression as a type of value expression.
 However, since a value expression must correspond to a single value,
 a column select expression used as a value expression should not
 return more than one value.  If it does, SQL generates an error.  A
 column select expression used as a value expression cannot include
 GROUP BY or HAVING clauses.

                                 NOTE

         IN predicates allow column select expressions used as
         value expressions to return more than one value.


 Column select expressions are also called subqueries.

 Interactive SQL users can recall the 20 most recent command lines
 using the up and down arrow keys or the CTRL/B key sequence:

  o  The up arrow key recalls lines in sequence from most recent to
     least recent.

  o  The CTRL/B key sequence also recalls lines in sequence from most
     recent to least recent.

  o  After you have recalled prior lines, the down arrow key allows
     you to recall more recently entered lines.

 A qualifier for column names.  Users can qualify a column name with
 its table or view name, or with an aribitrary correlation name they
 specify in the FROM clause of an SQL statement.  SQL requires
 correlation names as qualifiers instead of table or view names in
 statements that join a table with itself.

 DIGITAL proprietary database languages (such as RDO in Rdb/VMS) use
 the term database handle instead of alias.  The two terms mean the
 same thing.  For more information see the Help topic on alias.

 VAX Data Distributor is a software product that enables you to make
 data available to users and applications at multiple sites in a
 network.  From a source relational database, you can define the
 following transfers:

  o  Transfer an entire source database or a subset of that database.
     Transfers can remain on the same processor or you can define
     transfers to remote processors.

  o  Transfer data from multiple source databases into a single target
     database.

  o  Transfer data from one or more source databases into an existing,
     user-created target database.

Additional information available:

CREATE_SCHEDULECREATE_TRANSFERDROP_SCHEDULEDROP_TRANSFER
REINITIALIZESHOW_TRANSFERSTART_TRANSFERSTOP_TRANSFER

More InformationRelease NotesError msg doc

 Data Distributor allows three types of transfer:  extraction,
 extraction rollup, and replication transfers.

 Extraction transfers copy the latest version of the tables specified
 in the transfer definition from a single source database to a target
 database.  Once the transfer completes, Data Distributor severs the
 connection between the source and target databases.

 Extraction rollup transfers copy the latest version of the tables
 specified in the transfer definition from multiple source databases
 to a target database.  Once the transfer completes, Data Distributor
 severs the connection between the source and target databases.

 Like extraction transfers, a replication transfer creates tables at a
 target site during initial execution.  Unlike extraction transfers, a
 replication transfer maintains a connection with the target database
 so that the source database can supply updates to the target.  After
 the initial transfer execution, subsequent executions of a
 replication transfer involve only those additions, modifications, and
 deletions that have been made to rows in the source database since
 the previous transfer.

 You can issue Data Distributor statements, options, and qualifiers
 from SQL when VAX Data Distributor is installed on your system.  See
 the VAX Data Distributor Handbook and the SQL Reference Manual for
 details of the Data Distributor statements.

 To see the current Release Notes for VAX Data Distributor, type or
 print the following file:

     SYS$HELP:DDALvvu.RELEASE_NOTES

         where    vv = version
                  u  = update

 For example:

     SYS$HELP:DDAL022.RELEASE_NOTES

 Errors returned by Data Distributor are documented online in the file
 SYS$HELP:DDAL$MSG.DOC, which you can PRINT, TYPE, or SEARCH at DCL
 level.

 CREATE SCHEDULE FOR ───> transfer-name ─┐
  ┌──────────────────────────────────────┘
  └┬───────────>─────────────────────┬───┐
   └─> 
S
T
A
R
T ─────> start-date-time ─┘   │
  ┌──────────────────────────────────────┘
  └┬───────────>───────────────────────┬─┐
   └─> 
E
V
E
R
Y ─┬> every-delta-time ────┬┘ │
              └> every-absolute-time ─┘  │
  ┌──────────────────────────────────────┘
  └┬──────────────────────────────────────┬─>
   └> 
R
E
T
R
Y ─> count ─> 
T
I
M
E
S ──────┐     │
       ┌────────────────────────────┘     │
       └─┬──────────────────────────────┬─┘
         └─> 
R
E
T
R
Y 
E
V
E
R
Y ─> delta-time ─┘

Additional information available:

More Informationtransfer-namestart-date-timeevery-delta-time
every-absolute-timeAT at-timecountdelta-timeExamples

 Creates a schedule definition and stores it in the transfer database.
 The schedule definition specifies when and how often a transfer
 should execute.  A transfer can have only one schedule definition
 associated with it.  Data Distributor returns an error if you attempt
 to create a schedule for a transfer that already has one.

 Names the transfer for which this schedule is being defined.  The
 transfer must already exist before a schedule definition can be
 created for it.

 Specifies the time to execute the initial transfer.  You can specify
 a delta time or an absolute time.  If you use a delta time, Data
 Distributor uses the current time and the delta-time value to
 calculate the actual transfer time.  If you supply an absolute time,
 the initial transfer will be executed at the time specified.  The
 START clause is optional.  If you do not include a START clause, the
 start time is set to the current time.  The transfer then will
 execute as soon as the transfer schedule definition is processed.

 The delta-time format is as follows:

 dddd hh:mm:ss.cc

 The absolute-time format is as follows:

 dd-mmm-yyyy hh:mm:ss.cc

 In the delta-time and absolute designations, the abbreviations have
 the following meanings:

  o  dddd - Number of days

  o  dd - Day of the month

  o  mmm - Month

  o  yyyy - Year

  o  hh - Hours

  o  ss - Seconds

  o  cc - Hundredths of a second

 Used to calculate the time to execute the next transfer.  The EVERY
 clause is optional.  If you specify the EVERY clause, you must
 specify either every-delta-time or every-absolute-time.  If you omit
 the EVERY clause, the transfer occurs only once.The valid
 specification for every-delta-time is the delta-time format used by
 the $BINTIM VMS system service.

 every-absolute-time =

 ──┬──> 
D
A
Y ────┬─┬───────>──────────┬──┬─>
   ├──> 
W
E
E
K ───┤ └─> 
A
T ─> at-time ─┘  │
   ├──> 
M
O
N
T
H ──┘                       │
   └┬─> weekday ──┬───────>──────────┬─┬┘
    │             └─> 
A
T ─> at-time ─┘ │
    └──────────── , <──────────────────┘

 Used to calculate the time to execute the next transfer.  The EVERY
 clause is optional.  If you specify the EVERY clause, you must
 specify either every-absolute-time or every-delta-time.  If you omit
 the EVERY clause, the transfer occurs only once.

 Valid specifications for the every-absolute-time parameter are:

  o  DAY

     The transfer executes on a daily basis.

  o  WEEK

     The transfer occurs every week on the same day of the week as the
     initial transfer.

  o  MONTH

     The transfer occurs on a monthly cycle on the same day of the
     month as the initial transfer.

  o  WEEKDAY

     The transfer executes on the weekdays that you list.  If you list
     more than one weekday, separate the days with commas.  Valid
     weekdays are SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY,
     FRIDAY, and SATURDAY.

 Qualifies every-absolute-time by specifying the time of day the
 transfer should occur.  If you specify DAY, WEEK, or MONTH, but do
 not specify an at-time, Data Distributor uses the time of day of the
 initial transfer.  You can specify in a list of weekdays the at-time
 for each day.  If you omit the at-time for any weekday, Data
 Distributor selects as the default the time used for the previous
 entry in the list.  For the first entry in the list, the time of day
 of the initial transfer is used, if none is specified.

 The at-time argument has the following format:  hh:mm:ss.cc.  For an
 explanation of these abbreviations, see the Help topic on
 start-date-time.

 Specifies the maximum number of times Data Distributor retries a
 transfer if a transfer execution fails.  If you do not include a
 retry count or if the count value is set to zero, Data Distributor
 does not attempt to retry the transfer until the next scheduled
 transfer time as indicated by the EVERY clause.  If you include a
 retry count and the transfer fails, the retry will start at the
 beginning, not where the transfer left off.

 Specifies the length of time Data Distributor waits between the time
 of the last failed attempt and the time of the next retry attempt.
 The RETRY EVERY delta-time clause is optional and can only be
 specified if the RETRY count TIMES clause is included.

 Example 1:  Creating a schedule to run a transfer once a week

 This example calls for the COLLEGE_INFO transfer to execute at 3:00
 pm.  every Wednesday.  The schedule definition calls for a maximum of
 three retries occurring at intervals of 30 minutes.

 SQL> CREATE SCHEDULE FOR COLLEGE_INFO
 cont>  START 14-NOV-1990 15:00:00.00
 cont>     ! Wednesdays at 3 p.m.
 cont>     EVERY WEDNESDAY AT 15:00:00
 cont>     RETRY 3 TIMES
 cont>     RETRY EVERY 0 00:30:00
 cont>  ;

 Example 2:  Creating a schedule to run a transfer on an as-needed
 basis

 In this example, a transfer starts at midnight on December 15.
 Because the transfer will be performed on an as-needed basis, the
 user does not include an EVERY clause.  The user can replace the
 schedule definition if the transfer has to be run on a firm schedule
 at some later date.

 SQL> CREATE SCHEDULE FOR NH_EVALUATION
 cont>   START 15-DEC-1990
 cont>  ;

 CREATE TRANSFER ──> transfer-name ──> 
T
Y
P
E typebox (I)typebox (S) ┐
 ┌─────────────────────────────────────────────┘
 └┬> 
R
E
P
L
I
C
A
T
I
O
N ─> replication-extr-move-clause ─┬┐
  ├> 
E
X
T
R
A
C
T
I
O
N ─> replication-extr-move-clause ──┤│
  └> 
E
X
T
R
A
C
T
I
O
N 
R
O
L
L
U
P ─> rollup-move-clause ─────┘│
  ┌────────────────────────────────────────────────┘
  └─> to-clause ─┬────────────────────────────┬────┐
                 └┬> target-db-param-clause ─┬┘    │
                  └────────────<─────────────┘     │
  ┌────────────────────────────────────────────────┘
  └┬──────────────────────────────────┬────────────┐
   └─┬> transfer-file-options-clause ┬┘            │
     └─────────────<─────────────────┘             │
  ┌────────────────────────────────────────────────┘
  └┬───────────────────┬──────────────────────────> typebox (;)
   └─> comment-clause ─┘

Additional information available:

TYPE_ISREPLICATIONEXTRACTIONEXTRACTION_ROLLUP

More Informationtransfer-namereplication-extrrollup-move-clause
to-clausetarget-db-paramtransfer-filecomment-clauseExamples

 Creates a transfer definition and stores it in the transfer database.
 A transfer definition contains all of the information necessary to
 select a set of records from the source database and to define a
 target database.  A transfer definition also can contain the views to
 be defined on the target database and the command procedures to be
 executed before and after the execution of the transfer.

 Additionally, you can specify the following in a transfer definition:

  o  Whether the target database already exists or whether Data
     Distributor must create a new target database

  o  New names for specified data definitions in the target database

 Identifies the transfer by name.  The transfer name must be unique
 among the set of all transfers defined in the transfer database.
 Because a single transfer database serves all nodes in a VAXcluster
 environment, the transfer name must be unique across all nodes at a
 given VAXcluster site.  The transfer name does not have to be unique
 within the entire communications network.  Two VAXcluster systems can
 define transfers using the same transfer name.  If each transfer
 specifies the same existing target database, the transfers are
 differentiated by their respective network location.

 Names the type of transfer for the transfer definition.  REPLICATION,
 EXTRACTION, and EXTRACTION ROLLUP are the three valid transfer types
 for Data Distributor.

 Declares the transfer type to be a REPLICATION transfer.

 When a replication transfer executes, Data Distributor creates the
 tables at the target site during the initial execution and maintains
 a connection to that target database so the source can supply updates
 to the target database.  Subsequent transfers involve only those
 additions, modifications, and deletions that have been made to the
 selected rows in the source database.

 If the target and source databases become inconsistent with each
 other, you can use the REINITIALIZE TRANSFER statement and then the
 START TRANSFER statement to create new versions of the target tables
 that are consistent with the source tables.

 Declares the transfer type to be an EXTRACTION transfer.

 The tables copied to a target database by an extraction transfer
 maintain no relationship with the source database tables.  Unlike a
 replication transfer, Data Distributor severs the connection between
 the source database and the target database after the extraction
 transfer completes.  Each time an extraction transfer executes, Data
 Distributor copies the latest version of the selected tables to the
 target database.

 Although you can write to tables created by Data Distributor in a
 target database, any future execution of an extraction transfer that
 copies the same tables from the source database will not include data
 written only to the target tables.  For more information on read and
 write restrictions, see the description of the to-clause.

 replication-extr-move-clause =


q
q
q
q
> 
M
O
V
E 
T
A
B
L
E
S 
q
q
w
q
>move-tables-clause

 ─┬─┬───────────────────────┬──>
                    
m
q
q
q
q
q
q
q
q
q
q 
, 
<
q
q
q
q
q
q
q
q
q
j 
m
q
>move-views-clause
q
q
j

 Selects the rows of a table that Data Distributor transfers to the
 target database during an extraction or a replication transfer.  The
 rows selected for replications are specified with a restricted form
 of a select clause.  You must specify a move-tables-clause for each
 user table moved to the target database.

Additional information available:

MOVE_TABLES

move-tables-clausemove-select-clauseselect-listpredicatemove-views-clause

 For extraction transfers, specifies the table name or view name that
 you want copied from the source database.  For replication transfers,
 specifies the table name (not view name) that you want copied from
 the source database.  If you do not specify a table name or view
 name, you can specify a select clause.

 move-tables-clause =


q
q
q
w
q
q
w
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
w
q
q
w
q
q
q 
* 
q
q
q
q
q
q
q
q
q
q
q
q
w
q
q
w
q
q
k
   
x  
t
q
q
>alias
q
q
q
q
> 
. 
q
q
q
j  
t
q
q
>table-name
q
q
q
u  
x  
x
   
x  
x                        
m
q
q
>view-name
q
q
q
q
u  
x  
x
   
x  
m
q
q
q
q
q
q
q
q
q
q
>
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
> 
"
*
.
*
"
.
*
.
* 
q
q
q
q
j  
x  
x
   
m
q
q
>move-select-clause
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
j  
x
   
l
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
j
   
m
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
w
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
w
q
q
q
q
q
q
q
q
q
q
q
q
>
                    
x                    
x
                    
m
q
> 
I
N
T
Otable-name
q
j

 move-select-clause =




q
q
> 
S
E
L
E
C
T 
q
w
q
q
q
q
q
q
q
q
q
q
q
q
q
w
q
q
>select-list
q
q
> 
F
R
O
M

 ─┬───────────────────┬──┐
            
t
q
> 
A
L
L 
q
q
q
q
q
q
u                          
m
q
>alias
q
q
q
q
> 
. 
q
q
j

 │
            
m
q
> 
D
I
S
T
I
N
C
T 
q
j

 │
                                                                            
x

l
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
j

x

m
q
q
w
q
q
>table-name
q
q
q
w
q
q
w
q
q
q
q
q
q
q
q
q
>
q
q
q
q
q
q
q
q
q
q
q
w
q
w
q
q
q
q
q
q
q
>
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
w
q
>
   
m
q
q
>view-name
q
q
q
q
j  
m
q
>correlation-name
q
j 
m
q
> 
W
H
E
R
Epredicate 
q
q
q
j

 select-list  =


q
q
q
w
q
q
q
q
q
q
> 
* 
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
w
q
>
   
m
q
w
q
w
q
q
>column-name
q
q
w
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
w
j
     
x 
m
q
q
q
q
q
q
q 
, 
<
q
q
q
q
q
q
q
j                           
x
     
m
q
w
q
>select-element-list
q
w
q
q
> 
.
* 
q
q
q
q
q
q
q
q
q
q
q
q
q
w
j
       
x                        
m
q
q
> column-name
q
w
q
j
       
m
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q 
, 
<
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
q
j

 select-element-list =


q
q
q
w
q
q
>table-name
q
q
q
q
q
q
q
w
q
>
   
t
q
q
>view-name
q
q
q
q
q
q
q
q
u
   
m
q
q
>correlation-name
q
j