StatementCommon::__construct ( Connection $conn ) |
Create new statement instance.
|
void StatementCommon::setLimit ( $v ) |
Sets the maximum number of rows to return from db. This will affect the SQL if the RDBMS supports native LIMIT; if not, it will be emulated. Limit only applies to queries (not update sql).
|
int StatementCommon::getLimit ( ) |
Returns the maximum number of rows to return or 0 for all.
|
void StatementCommon::setOffset ( $v ) |
Sets the start row. This will affect the SQL if the RDBMS supports native OFFSET; if not, it will be emulated. Offset only applies to queries (not update) and only is evaluated when LIMIT is set!
|
int StatementCommon::getOffset ( ) |
Returns the start row. Offset only applies when Limit is set!
|
void StatementCommon::close ( ) |
Free resources associated with this statement. Some drivers will need to implement this method to free database result resources.
|
boolean StatementCommon::execute
(
$sql,
$fetchmode = null
)
|
Generic execute() function has to check to see whether SQL is an update or select query. If you already know whether it's a SELECT or an update (manipulating) SQL, then use the appropriate method, as this one will incurr overhead to check the SQL.
|
RestultSet StatementCommon::getResultSet ( ) |
Get result set. This assumes that the last thing done was an executeQuery() or an execute() with SELECT-type query.
|
int StatementCommon::getUpdateCount ( ) |
Get update count.
|
boolean StatementCommon::isSelect
(
$sql
)
[protected]
|
Returns whether the passed SQL is a SELECT statement. Returns true if SQL starts with 'SELECT' but not 'SELECT INTO'. This exists to support the execute() function -- which could either execute an update or a query. Currently this function does not take into consideration comments, primarily because there are a number of different comment options for different drivers: -- SQL-defined comment, but not truly comment in Oracle # comment in mysql /* comment in mssql, others * / // comment sometimes? REM also comment ... If you're wondering why we can't just execute the query and look at the return results to see whether it was an update or a select, the reason is that for update queries we need to do stuff before we execute them -- like start transactions if auto-commit is off.
|
object StatementCommon::executeQuery
(
$sql,
$fetchmode = null
)
|
Executes the SQL query in this PreparedStatement object and returns the resultset generated by the query.
Reimplemented in MSSQLStatement. |
int StatementCommon::executeUpdate ( $sql ) |
Executes the SQL INSERT, UPDATE, or DELETE statement in this PreparedStatement object.
|
boolean StatementCommon::getMoreResults ( ) |
Gets next result set (if this behavior is supported by driver). Some drivers (e.g. MSSQL) support returning multiple result sets -- e.g. from stored procedures. This function also closes any current restult set. Default behavior is for this function to return false. Driver-specific implementations of this class can override this method if they actually support multiple result sets.
Reimplemented in MSSQLStatement. |
Connection StatementCommon::getConnection ( ) |
Gets the db Connection that created this statement.
|
StatementCommon::$conn [protected]
|
|
StatementCommon::$resultSet [protected]
|
|
StatementCommon::$updateCount [protected]
|
|
StatementCommon::$warnings = array() [protected]
|
|
StatementCommon::$resultClass [protected]
|
|
StatementCommon::$stmt [protected]
|
|
StatementCommon::$limit = 0 [protected]
|
|
StatementCommon::$offset = 0 [protected]
|
|
This file is part of the Creole[php5] library.
Copyright © 2004 Hans Lellelid |   |
Creole[php5] CVS
|