Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ibase_query(3) [php man page]

IBASE_QUERY(3)								 1							    IBASE_QUERY(3)

ibase_query - Execute a query on an InterBase database

SYNOPSIS
resource ibase_query ([resource $link_identifier], string $query, [int $bind_args]) DESCRIPTION
Performs a query on an InterBase database. PARAMETERS
o $link_identifier - An InterBase link identifier. If omitted, the last opened link is assumed. o $query - An InterBase query. o $bind_args - RETURN VALUES
If the query raises an error, returns FALSE. If it is successful and there is a (possibly empty) result set (such as with a SELECT query), returns a result identifier. If the query was successful and there were no results, returns TRUE. Note In PHP 5.0.0 and up, this function will return the number of rows affected by the query for INSERT, UPDATE and DELETE statements. In order to retain backward compatibility, it will return TRUE for these statements if the query succeeded without affecting any rows. ERRORS
/EXCEPTIONS If you get some error like "arithmetic exception, numeric overflow, or string truncation. Cannot transliterate character between character sets" (this occurs when you try use some character with accents) when using this and after ibase_query(3) you must set the character set (i.e. ISO8859_1 or your current character set). CHANGELOG
+--------+---------------------------------------------------+ |Version | | | | | | | Description | | | | +--------+---------------------------------------------------+ | 5.3.1 | | | | | | | On success the function now returns TRUE if | | | there were no affected rows, where it previously | | | returned 0 (a zero followed by an empty space). | | | | +--------+---------------------------------------------------+ EXAMPLES
Example #1 ibase_query(3) example <?php $host = 'localhost:/path/to/your.gdb'; $dbh = ibase_connect($host, $username, $password); $stmt = 'SELECT * FROM tblname'; $sth = ibase_query($dbh, $stmt) or die(ibase_errmsg()); ?> SEE ALSO
ibase_errmsg(3), ibase_fetch_row(3), ibase_fetch_object(3), ibase_free_result(3). PHP Documentation Group IBASE_QUERY(3)

Check Out this Related Man Page

MYSQL_UNBUFFERED_QUERY(3)						 1						 MYSQL_UNBUFFERED_QUERY(3)

mysql_unbuffered_query - Send an SQL query to MySQL without fetching and buffering the result rows.

SYNOPSIS
Warning This extension is deprecated as of PHP 5.5.0, and will be removed in the future. Instead, the MySQLi or PDO_MySQL extension should be used. See also MySQL: choosing an API guide and related FAQ for more information. Alternatives to this function include: oSee: Buffered and Unbuffered queries resource mysql_unbuffered_query (string $query, [resource $link_identifier = NULL]) DESCRIPTION
mysql_unbuffered_query(3) sends the SQL query $query to MySQL without automatically fetching and buffering the result rows as mysql_query(3) does. This saves a considerable amount of memory with SQL queries that produce large result sets, and you can start working on the result set immediately after the first row has been retrieved as you don't have to wait until the complete SQL query has been per- formed. To use mysql_unbuffered_query(3) while multiple database connections are open, you must specify the optional parameter $link_iden- tifier to identify which connection you want to use. o $query - The SQL query to execute. Data inside the query should be properly escaped. o $ link_identifier -The MySQL connection. If the link identifier is not specified, the last link opened by mysql_connect(3) is assumed. If no such link is found, it will try to create one as if mysql_connect(3) was called with no arguments. If no connection is found or established, an E_WARNING level error is generated. For SELECT, SHOW, DESCRIBE or EXPLAIN statements, mysql_unbuffered_query(3) returns a resource on success, or FALSE on error. For other type of SQL statements, UPDATE, DELETE, DROP, etc, mysql_unbuffered_query(3) returns TRUE on success or FALSE on error. Note The benefits of mysql_unbuffered_query(3) come at a cost: you cannot use mysql_num_rows(3) and mysql_data_seek(3) on a result set returned from mysql_unbuffered_query(3), until all rows are fetched. You also have to fetch all result rows from an unbuffered SQL query before you can send a new SQL query to MySQL, using the same $link_identifier. mysql_query(3). PHP Documentation Group MYSQL_UNBUFFERED_QUERY(3)
Man Page