Description

The query becomes part of the currently open transaction. If
there is no open transaction, ingres_unbuffered_query()
opens a new transaction. To close the transaction, you can
call either ingres_commit() to commit the changes
made to the database or ingres_rollback() to
cancel these changes. When the script ends, any open transaction
is rolled back (by calling
ingres_rollback()). You can also use
ingres_autocommit() before opening a new
transaction to have every SQL query immediately committed.
Ingres allows only a single unbuffered statement to be active at any
one time. The extension will close any active unbuffered statements before
executing any SQL. In addition you cannot use
ingres_result_seek() to position the row before
fetching.

Parameters

link

The connection link identifier

query

A valid SQL query (see the Ingres SQL reference
guide) in the Ingres documentation.
See the query
parameter in ingres_query() for a list of SQL
statements that cannot be executed via
ingres_unbuffered_query().

A string containing a sequence of types for the parameter values
passed. See the types parameter in
ingres_query() for the list of type codes.

Return Values

ingres_unbuffered_query() returns a query result identifier when
there are rows to fetch; else it returns FALSE when there are no rows, as
is the case of an INSERT, UPDATE, or DELETE statement. To see if an error
occurred, use ingres_errno(),
ingres_error(), or
ingres_errsqlstate().