Neoview SQL Reference Manual (R2.4)

Drops a view.“DROP VIEW Statement” (page 116)
Grants access privileges for a table or view to specified
roles.
“GRANT Statement” (page 133)
Grants privileges for executing a stored procedure in Java
(SPJ) to specified roles.
“GRANT EXECUTE Statement” (page 135)
Grants access privileges for a schema to specified roles.“GRANT SCHEMA Statement” (page 137)
Revokes access privileges for a table or view from specified
roles.
“REVOKE Statement” (page 154)
Revokes privileges for executing a stored procedure from
specified roles.
“REVOKE EXECUTE Statement” (page 156)
Revokes access privileges for a schema.“REVOKE SCHEMA Statement” (page 158)
Data Manipulation Language (DML) Statements
Use these DML statements to delete, insert, select, or update rows in one or more tables:
Deletes rows from a table or view.“DELETE Statement” (page 105)
Inserts data into tables and views.“INSERT Statement” (page 141)
Retrieves data from tables and views.“SELECT Statement” (page 162)
Updates values in columns of a table or view.“UPDATE Statement” (page 196)
For information about DELETE, INSERT, SELECT, and UPDATE, see individual entries for these
statements.
Transaction Control Statements
Use these statements to specify user-defined transactions and to set attributes for the next
transaction:
Starts a transaction.“BEGIN WORK Statement” (page 54)
Commits changes made during a transaction and ends the
transaction.
“COMMIT WORK Statement” (page 58)
Performs all table maintenance operations.“MERGE INTO Statement” (page 149)
Undoes changes made during a transaction and ends the
transaction.
“ROLLBACK WORK Statement” (page 161)
Sets attributes for the next SQL transaction — the isolation
level, access mode, size of the diagnostics area, and
whether to automatically commit database changes.
“SET TRANSACTION Statement” (page 187)
Resource Control and Optimization Statements
Use these statements to control access to a Neoview SQL table and its indexes on remote segments:
Executes and SQL statement previously compiled by a
PREPARE statement.
“EXECUTE Statement” (page 117)
Locks the specified table (or the underlying tables of a
view) and its associated indexes for the duration of the
active transaction.
“LOCK TABLE Statement” (page 147)
Compiles an SQL statement for later use with the
EXECUTE statement.
“PREPARE Statement” (page 152)
Updates statistics about the contents of a table and its
indexes.
“UPDATE STATISTICS Statement” (page 202)
40 SQL Statements