Pdostatement Methods

Front 1

bindColumn

Back 1

PDOStatement::bindColumn() arranges to have a particular variable bound to a given column in the result-set from a query. Each call to PDOStatement::fetch() or PDOStatement::fetchAll() will update all the variables that are bound to columns.

Front 2

bindParam

Back 2

Binds a PHP variable to a corresponding named or question mark placeholder in the SQL statement that was use to prepare the statement. Unlike PDOStatement::bindValue(), the variable is bound as a reference and will only be evaluated at the time that PDOStatement::execute() is called.

Most parameters are input parameters, that is, parameters that are used in a read-only fashion to build up the query. Some drivers support the invocation of stored procedures that return data as output parameters, and some also as input/output parameters that both send in data and are updated to receive it.

Front 3

bindValue

Back 3

Binds a value to a corresponding named or question mark placeholder in the SQL statement that was use to prepare the statement.

Front 4

closeCursor

Back 4

PDOStatement::closeCursor() frees up the connection to the server so that other SQL statements may be issued, but leaves the statement in a state that enables it to be executed again.

This method is useful for database drivers that do not support executing a PDOStatement object when a previously executed PDOStatement object still has unfetched rows. If your database driver suffers from this limitation, the problem may manifest itself in an out-of-sequence error.

Front 5

columnCount

Back 5

Returns the number of columns in the result set

Front 6

debugDumpParams

Back 6

Dumps the informations contained by a prepared statement directly on the output. It will provide the SQL query in use, the number of parameters used (Params), the list of parameters, with their name, type (paramtype) as an integer, their key name or position, the value, and the position in the query (if this is supported by the PDO driver, otherwise, it will be -1).

This is a debug function, which dump directly the data on the normal output.

Front 7

errorCode

Back 7

Fetch the SQLSTATE associated with the last operation on the statement handle

Identical to PDO::errorCode(), except that PDOStatement::errorCode() only retrieves error codes for operations performed with PDOStatement objects.

Front 8

errorInfo

Back 8

Fetch extended error information associated with the last operation on the statement handle

Front 9

execute

Back 9

Execute the prepared statement. If the prepared statement included parameter markers, you must either:

*call PDOStatement::bindParam() to bind PHP variables to the parameter markers: bound variables pass their value as input and receive the output value, if any, of their associated parameter markers

*or pass an array of input-only parameter values

Front 10

fetch

Back 10

Fetches the next row from a result set

Fetches a row from a result set associated with a PDOStatement object. The fetch_style parameter determines how PDO returns the row.

Front 11

fetchAll

Back 11

Returns an array containing all of the result set rows

Front 12

fetchColumn

Back 12

Returns a single column from the next row of a result set or FALSE if there are no more rows.

Front 13

fetchObject

Back 13

Fetches the next row and returns it as an object. This function is an alternative to PDOStatement::fetch() with PDO::FETCH_CLASS or PDO::FETCH_OBJ style.

Front 14

getAttribute

Back 14

Gets an attribute of the statement. Currently, no generic attributes exist but only driver specific:

Front 15

nextRowset

Back 15

Advances to the next rowset in a multi-rowset statement handle

Some database servers support stored procedures that return more than one rowset (also known as a result set). PDOStatement::nextRowset() enables you to access the second and subsequent rowsets associated with a PDOStatement object. Each rowset can have a different set of columns from the preceding rowset.

Front 16

rowCount

Back 16

PDOStatement::rowCount() returns the number of rows affected by the last DELETE, INSERT, or UPDATE statement executed by the corresponding PDOStatement object.

If the last SQL statement executed by the associated PDOStatement was a SELECT statement, some databases may return the number of rows returned by that statement. However, this behaviour is not guaranteed for all databases and should not be relied on for portable applications.

Front 17

setAttribute

Back 17

Sets an attribute on the statement. Currently, no generic attributes are set but only driver specific:

Front 18

setFetchMode

Back 18

Set the default fetch mode for this statement