Download Database Compatibility for Oracle® Developer`s Guide

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Document related concepts

Concurrency control wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Entity–attribute–value model wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Navitaire Inc v Easyjet Airline Co. and BulletProof Technologies, Inc. wikipedia , lookup

Open Database Connectivity wikipedia , lookup

Database wikipedia , lookup

Functional Database Model wikipedia , lookup

SQL wikipedia , lookup

Ingres (database) wikipedia , lookup

Clusterpoint wikipedia , lookup

ContactPoint wikipedia , lookup

Oracle Database wikipedia , lookup

Extensible Storage Engine wikipedia , lookup

Relational model wikipedia , lookup

Database model wikipedia , lookup

PL/SQL wikipedia , lookup

Transcript
Database Compatibility for Oracle® Developer’s Guide
EXEC SQL [FOR array_size] OPEN cursor
[USING [SQL] DESCRIPTOR descriptor_name]
[INTO [SQL] DESCRIPTOR descriptor_name];
Where:
array_size is an integer value or a host variable that contains an integer value
specifying the number of rows to fetch. If you omit the FOR clause, the statement is
executed once for each member of the array.
cursor is the name of the cursor being opened.
descriptor_name specifies the name of an SQL descriptor (in the form of a single-
quoted string literal) or a host variable that contains the name of an SQL descriptor that
contains the query that initializes the cursor.
For example, the following statement opens a cursor (named emp_cursor), using the
host variable, :employees:
EXEC SQL OPEN emp_cursor USING DESCRIPTOR :employees;
14.5.24
PREPARE
Prepared statements are useful when a client application must perform a task multiple
times; the statement is parsed, written and planned only once, rather than each time the
statement is executed, saving repetitive processing time.
Use the PREPARE statement to prepare an SQL statement or PL/pgSQL block for
execution. The statement is available in two forms; the first form is:
EXEC SQL [AT database_name] PREPARE statement_name
FROM sql_statement;
The second form is:
EXEC SQL [AT database_name] PREPARE statement_name
AS sql_statement;
Where:
database_name is the database identifier or a host variable that contains the database
identifier against which the statement will execute. If you omit the AT clause, the
statement will execute against the current default database.
statement_name is the identifier associated with a prepared SQL statement or PL/SQL
block.
Copyright © 2007 - 2017 EnterpriseDB Corporation. All rights reserved.
1059