Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ingres_next_error(3) [php man page]

INGRES_NEXT_ERROR(3)							 1						      INGRES_NEXT_ERROR(3)

ingres_next_error - Get the next Ingres error

SYNOPSIS
bool ingres_next_error ([resource $link]) DESCRIPTION
Get the next Ingres error for the last executed query. Each call to ingres_next_error(3) can be followed by a call to ingres_errno(3), ingres_error(3) or ingres_errsqlstate(3) to get the respective error number, error text, or SQL STATE. While ingres_next_error(3) returns TRUE, there are more errors to fetch. PARAMETERS
o $link - The connection link identifier RETURN VALUES
ingres_next_error(3) returns TRUE if there is another error to retrieve or FALSE when there are no more errors SEE ALSO
ingres_errno(3), ingres_error(3), ingres_errsqlstate(3). PHP Documentation Group INGRES_NEXT_ERROR(3)

Check Out this Related Man Page

INGRES_PREPARE(3)							 1							 INGRES_PREPARE(3)

ingres_prepare - Prepare a query for later execution

SYNOPSIS
mixed ingres_prepare (resource $link, string $query) DESCRIPTION
Prepares a query for execution by ingres_execute(3). The query becomes part of the currently open transaction. If there is no open transaction, ingres_query(3) opens a new transaction. To close the transaction, you can call either ingres_commit(3) to commit the changes made to the database or ingres_rollback(3) to cancel these changes. When the script ends, any open transaction is rolled back (by calling ingres_rollback(3)). You can also use ingres_autocom- mit(3) before opening a new transaction to have every SQL query immediately committed. Note Related Configurations See also the ingres.describe, ingres.scrollable and ingres.utf8 directives in Runtime Configuration. PARAMETERS
o $link - The connection link identifier o $query - A valid SQL query (see the Ingres SQL reference guide) in the Ingres documentation. See the query parameter in ingres_query(3) for a list of SQL statements which cannot be executed using ingres_prepare(3) RETURN VALUES
ingres_prepare(3) returns a query result identifier that is used with ingres_execute(3) to execute the query. To see if an error occurred, use ingres_errno(3), ingres_error(3), or ingres_errsqlstate(3). SEE ALSO
ingres_unbuffered_query(3), ingres_fetch_array(3), ingres_fetch_assoc(3), ingres_fetch_object(3), ingres_fetch_row(3), ingres_commit(3), ingres_rollback(3), ingres_autocommit(3), ingres_set_environment(3), ingres_errno(3), ingres_error(3). PHP Documentation Group INGRES_PREPARE(3)
Man Page

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

copy, clear and keep to new data only

I have an Ingres database logfile that grows constantly, iircp.log. It is always "attached" to the Ingres process that uses it, and I do not want to screw up the data. I have been copying it to another directory and then using vi on the original to reduce the size 34000 lines at a time. What I want... (1 Reply)
Discussion started by: sarge
1 Replies

2. Shell Programming and Scripting

question on awk

Orig file ========== XX| ABCD9089929 | PEP | 20090114 | 0.00 | 2 | F1 | STATE XX| ABCD9089933 | PEP | 20090114 | 0.00 | 2 | F1 | STATE XX| ABCD9104256 | PEP | 20090114 | 357.50 | 2 | F2 | STATE XX| ABCD9104316 | PEP | 20090114 | 200.00 | 2 | F2 | STATE XX| ABCD9098363 | PEP | 20090115 |... (2 Replies)
Discussion started by: xinoo
2 Replies