Keyboard Shortcuts?
Next menu item
Previous menu item
Previous man page
Next man page
Scroll to bottom
Scroll to top
Goto homepage
Goto search(current page)
Focus search box
Change language:
Brazilian Portuguese
Chinese (Simplified)
PHP Data Objects
— La classe PDO — D&marre une transaction — Valide une transaction — Cr&e une instance PDO qui repr&sente une connexion & la base — Retourne le SQLSTATE associ& avec la derni&re op&ration sur la base de donn&es — Retourne les informations associ&es & l'erreur lors de la
derni&re op&ration sur la base de donn&es — Ex&cute une requ&te SQL et retourne le nombre de lignes affect&es — R&cup&re un attribut d'une connexion & une base de donn&es — Retourne la liste des pilotes PDO disponibles — V&rifie si nous sommes dans une transaction — Retourne l'identifiant de la derni&re ligne ins&r&e ou la valeur d'une s&quence — Pr&pare une requ&te & l'ex&cution et retourne un objet — Ex&cute une requ&te SQL, retourne un jeu de r&sultats en tant
qu'objet PDOStatement — Prot&ge une cha&ne pour l'utiliser dans une requ&te SQL PDO — Annule une transaction — Configure un attribut PDO — La classe PDOStatement — Lie une colonne & une variable PHP — Lie un param&tre & un nom de variable sp&cifique — Associe une valeur & un param&tre — Ferme le curseur, permettant & la requ&te d'&tre de nouveau ex&cut&e — Retourne le nombre de colonnes dans le jeu de r&sultats — D&taille une commande pr&par&e SQL — R&cup&re les informations sur l'erreur associ&e lors de la derni&re op&ration sur la requ&te — R&cup&re les informations sur l'erreur associ&e lors de la derni&re op&ration sur la requ&te — Ex&cute une requ&te pr&par&e — R&cup&re la ligne suivante d'un jeu de r&sultats PDO — Retourne un tableau contenant toutes les lignes du jeu d'enregistrements — Retourne une colonne depuis la ligne suivante d'un jeu de r&sultats — R&cup&re la prochaine ligne et la retourne en tant qu'objet — R&cup&re un attribut de requ&te — Retourne les m&tadonn&es pour une colonne d'un jeu de r&sultats — Avance & la prochaine ligne de r&sultats d'un gestionnaire de lignes de r&sultats multiples — Retourne le nombre de lignes affect&es par le dernier
appel & la fonction PDOStatement::execute() — D&finit un attribut de requ&te — D&finit le mode de r&cup&ration par d&faut pour cette requ&te — La classe PDOException — Fonctions CUBRID (PDO_CUBRID) — Microsoft SQL Server et Fonctions Sybase (PDO_DBLIB) — Fonctions Firebird (PDO_FIREBIRD) — Fonctions IBM (PDO_IBM) — Fonctions Informix (PDO_INFORMIX) — Fonctions MySQL (PDO_MYSQL) — Fonctions Microsoft SQL Server (PDO_SQLSRV) — Fonctions Oracle (PDO_OCI) — Fonctions ODBC et DB2 (PDO_ODBC) — Fonctions PostgreSQL (PDO_PGSQL) — Fonctions SQLite (PDO_SQLITE)
Please note this:Won't work:$sth = $dbh-&prepare('SELECT name, colour, calories FROM ?& WHERE calories & ?');THIS WORKS!$sth = $dbh-&prepare('SELECT name, colour, calories FROM fruit WHERE calories & ?');The parameter cannot be applied on table names!!
I wanted to extend PDO class to store statistics of DB usage, and I faced some problems. I wanted to count number of created statements and number of their executings. So PDOStatement should have link to PDO that created it and stores the statistical info. The problem was that I didn't knew how PDO creates PDOStatement (constructor parameters and so on), so I have created these two classes:&?phpclass PDOp {& & & & protected $PDO;& & & & public $numExecutes;& & & & public $numStatements;& & & & public function __construct($dsn, $user=NULL, $pass=NULL, $driver_options=NULL) {& & & & & & $this-&PDO = new PDO($dsn, $user, $pass, $driver_options);& & & & & & $this-&numExecutes = 0;& & & & & & $this-&numStatements = 0;& & & & }& & & & public function __call($func, $args) {& & & & & & return call_user_func_array(array(&$this-&PDO, $func), $args);& & & & }& & & & public function prepare() {& & & & & & $this-&numStatements++;& & & & & & & & & & & & $args = func_get_args();& & & & & & $PDOS = call_user_func_array(array(&$this-&PDO, 'prepare'), $args);& & & & & & & & & & & & return new PDOpStatement($this, $PDOS);& & & & }& & & & public function query() {& & & & & & $this-&numExecutes++;& & & & & & $this-&numStatements++;& & & & & & & & & & & & $args = func_get_args();& & & & & & $PDOS = call_user_func_array(array(&$this-&PDO, 'query'), $args);& & & & & & & & & & & & return new PDOpStatement($this, $PDOS);& & & & }& & & & public function exec() {& & & & & & $this-&numExecutes++;& & & & & & & & & & & & $args = func_get_args();& & & & & & return call_user_func_array(array(&$this-&PDO, 'exec'), $args);& & & & }& & }& & class PDOpStatement implements IteratorAggregate {& & & & protected $PDOS;& & & & protected $PDOp;& & & & public function __construct($PDOp, $PDOS) {& & & & & & $this-&PDOp = $PDOp;& & & & & & $this-&PDOS = $PDOS;& & & & }& & & & public function __call($func, $args) {& & & & & & return call_user_func_array(array(&$this-&PDOS, $func), $args);& & & & }& & & & public function bindColumn($column, &$param, $type=NULL) {& & & & & & if ($type === NULL)& & & & & & & & $this-&PDOS-&bindColumn($column, $param);& & & & & & else& & & & & & & & $this-&PDOS-&bindColumn($column, $param, $type);& & & & }& & & & public function bindParam($column, &$param, $type=NULL) {& & & & & & if ($type === NULL)& & & & & & & & $this-&PDOS-&bindParam($column, $param);& & & & & & else& & & & & & & & $this-&PDOS-&bindParam($column, $param, $type);& & & & }& & & & public function execute() {& & & & & & $this-&PDOp-&numExecutes++;& & & & & & $args = func_get_args();& & & & & & return call_user_func_array(array(&$this-&PDOS, 'execute'), $args);& & & & }& & & & public function __get($property) {& & & & & & return $this-&PDOS-&$property;& & & & }& & & & public function getIterator() {& & & & & & return $this-&PDOS;& & & & }&& }?&Classes have properties with original PDO and PDOStatement objects, which are providing the functionality to PDOp and PDOpStatement.From outside, PDOp and PDOpStatement look like PDO and PDOStatement, but also are providing wanted info.
If you use $dbh = new PDO('pgsql:host=dbname=test_basic01', $user, $pass); and you get the following error:PHP Fatal error:& Uncaught exception 'PDOException' with message 'SQLSTATE[08006] [7] could not connect to server: Connection refused\n\tIs the server running on host "localhost" and accepting\n\tTCP/IP connections on port 5432?'then as pointed out under pg_connect at:
******you should try to leave the host= and port= parts out of the connection string. This sounds strange, but this is an "option" of Postgre. If you have not activated the TCP/IP port in postgresql.conf then postgresql doesn't accept any incoming requests from an TCP/IP port. If you use host= in your connection string you are going to connect to Postgre via TCP/IP, so that's not going to work. If you leave the host= part out of your connection string you connect to Postgre via the Unix domain sockets, which is faster and more secure, but you can't connect with the database via any other PC as the localhost.******Sincerely,Aouie
I decided to create a singleton wrapper for PDO that ensures only one instance is ever used.
It uses PHP 5.3.0's __callStatic functionality to pass on statically called methods to PDO.
This means you can just call it statically from anywhere without having to initiate or define the object.
Usage examples:
&?php
DB::exec("DELETE FROM Blah");
foreach( DB::query("SELECT * FROM Blah") as $row){
& & & & print_r($row);
}
?&
class DB {
& &
& & private static $objInstance;
& &
& & private function __construct() {}
& & private function __clone() {}
& &
& & public static function getInstance(& ) {
& & & & & &
& & & & if(!self::$objInstance){
& & & & & & self::$objInstance = new PDO(DB_DSN, DB_USER, DB_PASS);
& & & & & & self::$objInstance-&setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
& & & & }
& & & &
& & & & return self::$objInstance;
& &
& & } final public static function __callStatic( $chrMethod, $arrArguments ) {
& & & & & &
& & & & $objInstance = self::getInstance();
& & & &
& & & & return call_user_func_array(array($objInstance, $chrMethod), $arrArguments);
& & & &
& & } }
?&
If you need to get Output variable from MSSQL stored procedure, try this :-- PROCEDURECREATE PROCEDURE spReturn_Int @err int OUTPUT ASSET @err = 11GO$sth = $dbh-&prepare("EXECUTE spReturn_Int ?");$sth-&bindParam(1, $return_value, PDO::PARAM_INT|PDO::PARAM_INPUT_OUTPUT);$sth-&execute();print "procedure returned $return_value\n";
This works to get UTF8 data from MSSQL:&?php$db = new PDO('dblib:host=your_dbname=your_charset=UTF-8', $user, $pass);?&
I use PDO with the ODBC driver to query stored procedures in a MS SQL Server 2005 Database under Windows XP Professional with IIS 5 and PHP 5.1.4. You may have the same problems with a different configuration.I experienced 2 very time consuming errors:1. The first one is when you return the result of a SELECT query, and you get the following clueless message:&&& Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[24000]: Invalid cursor state: 0 [Microsoft][SQL Native Client]Invalid cursor state (SQLFetchScroll[0] at ext\pdo_odbc\odbc_stmt.c:372)' in (YOUR_TRACE_HERE) &&&Your exact message may be different, the part to pay attention to is "Invalid cursor state".-& I found that I had this error because I didn't include "SET NOCOUNT ON" in the *body* of the stored procedure. By default the server returns a special piece of information along with the results, indicating how many rows were affected by the stored procedure, and that's not handled by PDO.2. The second error I had was:&&& Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[22003]: Numeric value out of range: 0 [Microsoft][SQL Native Client]Numeric value out of range (SQLFetchScroll[0] at ext\pdo_odbc\odbc_stmt.c:372)' in (YOUR_TRACE_HERE) &&&Another meaningless error "Numeric value out of range"... -& I was actually returning a date datatype (datetime or smalldatetime) "as is", that is, without converting it to varchar before including it in the result set... I don't know if PDO is responsible for converting it to a PHP datatype, but it doesn't. Convert it before it reaches PHP.
Hi there,because of ZDE 5.0 and other PHP-IDEs do not seem to support PDO from PHP5.1 in code-completion-database yet, I wrote a code-completion alias for the PDO class.NOTE: This Class has no functionality and should be only included to your IDE-Project but NOT(!) to your application.&?phpclass PDO {& & & & & & & & const ERR_ALREADY_EXISTS = 0;& & & & const ERR_CANT_MAP = 0;& & & & const ERR_NOT_FOUND = 0;& & & & const ERR_SYNTAX = 0;& & & & const ERR_CONSTRAINT = 0;& & & & const ERR_MISMATCH = 0;& & & & const ERR_DISCONNECTED = 0;& & & & const ERR_NONE = 0;& & & & const ATTR_ERRMODE = 0;& & & & const ATTR_TIMEOUT = 0;& & & & const ATTR_AUTOCOMMIT = 0;& & & & const ATTR_PERSISTENT = 0;& & & & const ERRMODE_EXCEPTION = 0;& & & & const ERRMODE_WARNING = 0;& & & & const FETCH_ASSOC = 0;& & & & const FETCH_NUM = 0;& & & & const FETCH_OBJ = 0;& & & & & & & & public function __construct($uri, $user, $pass, $optsArr) {& & & & }& & & & & & & & public function prepare ($prepareString) {& & & & }& & & & public function query ($queryString) {& & & & }& & & & public function quote ($input) {& & & & }& & & & public function exec ($statement) {& & & & }& & & & public function lastInsertId() {& & & & }& & & & public function beginTransaction () {& & & & }& & & & public function commit () {& & & & }& & & & public function rollBack () {& & & & }& & & & public function errorCode () {& & & & }& & & & public function errorInfo () {& & & & }& & & & & & }& & & & class PDOStatement {& & & & & & & & public function bindValue ($no, $value) {& & & & }& & & & public function fetch () {& & & & }& & & & public function nextRowset () {& & & & }& & & & public function execute() {& & & & }& & & & public function errorCode () {& & & & }& & & & public function errorInfo () {& & & & }& & & & public function rowCount () {& & & & }& & & & public function setFetchMode ($mode) {& & & & }& & & & public function columnCount () {& & & & }& & }
Watch out for putting spaces in the DSNmysql:host=dbname=test worksmysql: host = dbname=test worksmysql: host = dbname = test doesn't work...
It appears that PDO SQL statements can not make use of /* */ comments. Or at least, when I was trying to use them with mine it was crashing without error and giving me a blank page (even though I surrounded with try catch block).
Not all PDO drivers return a LOB mysql 5 is one example. Therefore when streaming a mime typed object from the database you cannot use fpassthru.The following is a modified example that works with a mysql database. (Tested FreeBSD v 6.2 with mysql 5.0.45 and php 5.2.3) &?phpob_start();$db = new PDO('mysql:host=dbname=&SOMEDB&', '&USERNAME&', 'PASSWORD');$stmt = $db-&prepare("select contenttype, imagedata from images where id=?");$stmt-&execute(array($_GET['id']));$stmt-&bindColumn(1, $type, PDO::PARAM_STR, 256);$stmt-&bindColumn(2, $lob, PDO::PARAM_LOB);$stmt-&fetch(PDO::FETCH_BOUND);ob_clean();header("Content-Type: $type");echo $lob; ob_end_flush();?&Please note the inclusion of buffer control. I only needed this when using 'include','include_once','require', or 'require_once' - my feeling is there is a subtle issue with those options as even an empty include file caused a buffer issue for me. === AND YES, I DID CHECK MY INCLUDE FILES DID NOT HAVE SPURIOUS WHITESPACE ETC OUTSIDE THE &?php ?& DELIMITERS! ===
I have seen a lot of user struggling with calling mysql procedures with in/out/inout parameters using bindParam. There seems to be a bug or missing feature within the mysql C api. This at least I could find out after reading a lot of posts at different places...At the moment I workaround it like below. $con is a PDO object:&?php$proc = $con-&prepare( "call proc_in( @i_param )" );$con-&query( "set @i_param = 'myValue'" );$proc-&execute();$proc = $con-&prepare( "call proc_out( @o_param )" );$proc-&execute();$o_param = $con-&query( "select @o_param" )-&fetchColumn();$proc = $con-&prepare( "call proc_inout( @io_param )" );$con-&query( "set @io_param = 'myValue'" );$proc-&execute();$io_param = $con-&query( "select @io_param" )-&fetchColumn();?&
I found a nice pdo modification written in php called Open Power Driver. It has identical API with the original, but allows you to cache query results:
Example 5: &?phptry {& $dbh = new PDO('odbc:SAMPLE', 'db2inst1', 'ibmdb2',& & & array(PDO::ATTR_PERSISTENT =& true));....... } catch (Exception $e) {& $dbh-&rollBack();& echo "Failed: " . $e-&getMessage();}?& We must change the last two lines to catch the error connecting to the database:} catch (Exception $e) {& echo "Failed: " . $e-&getMessage();& $dbh-&rollBack();}?&
Note this:Won't work:$sth = $dbh-&prepare('SELECT name, colour, calories FROM fruit WHERE ? & ?');THIS WORKS!$sth = $dbh-&prepare('SELECT name, colour, calories FROM fruit WHERE calories & ?');Parameters cannot be applied on column names!!
PDO doesn't return OUTPUT params from mssql stored procedures/* Stored Procedure Create Code: *//*CREATE PROCEDURE p_sel_all_termlength @err INT OUTPUT ASSET @err = 2627*//* PHP Code: */&?php& & $Link = new PDO('mssql:host=dbname=database', 'username','password');& & & & $ErrorCode = 0;& & & & $Stmt = $Link-&prepare('p_sel_all_termlength ?');& & $Stmt-&bindParam(1,$ErrorCode,PDO::PARAM_INT,4);& & $Stmt-&execute();& & echo "Error = " . $ErrorCode . "\n";?&/* PHP Output:Error = 0*/
If you plan on using prepared statements to issue a series of KILLs, think again.& PDO apparently does not support this, and will tell you, assuming you don't put any parameters in the statement (a situation in which it would be pointless to use prepared statements anyway).& If you do specify some ?-mark parameters, it will just spit out an error that doesn't help at all.
Below is an example of extending PDO & PDOStatement classes:&?phpclass Database extends PDO{& & function __construct()& & {& & & & parent::__construct('mysql:dbname=host=localhost', 'root', '');& & & & $this-&setAttribute(PDO::ATTR_STATEMENT_CLASS, array('DBStatement', array($this)));& & }}class DBStatement extends PDOStatement{& & public $dbh;& & protected function __construct($dbh)& & {& & & & $this-&dbh = $dbh;& & & & $this-&setFetchMode(PDO::FETCH_OBJ);& & }& & & & public function foundRows()& & {& & & & $rows = $this-&dbh-&prepare('SELECT found_rows() AS rows', array(PDO::MYSQL_ATTR_USE_BUFFERED_QUERY =& TRUE));& & & & $rows-&execute();& & & & $rowsCount = $rows-&fetch(PDO::FETCH_OBJ)-&rows;& & & & $rows-&closeCursor();& & & & return $rowsCount;& & }}?&
Merge the prepare() and execute() in one function like a sprintf().And like sprintf, I choose to use unnamed args (?) ;)you could still use old insecure query() ( not prepared ) with renamed function :)&?phpclass MyPDO extends PDO{& & const PARAM_host='localhost';& & const PARAM_port='3306';& & const PARAM_db_name='test';& & const PARAM_user='root';& & const PARAM_db_pass='';& & public function __construct($options=null){& & & & parent::__construct('mysql:host='.MyPDO::PARAM_host.';port='.MyPDO::PARAM_port.';dbname='.MyPDO::PARAM_db_name,MyPDO::PARAM_user,MyPDO::PARAM_db_pass,$options);& & }& & public function query($query){ $args = func_get_args();& & & & array_shift($args); $reponse = parent::prepare($query);& & & & $reponse-&execute($args);& & & & return $reponse;& & }& & public function insecureQuery($query){ return parent::query($query);& & }}$db = new MyPDO();$db-&setAttribute(PDO::ATTR_DEFAULT_FETCH_MODE, PDO::FETCH_OBJ);$t1 = isset($_GET["t1"])?$_GET["t1"]:1; $t2 = isset($_GET["t2"])?$_GET["t2"]:2; $t3 = isset($_GET["t3"])?$_GET["t3"]:3; $ret = $db-&query("SELECT * FROM table_test WHERE t1=? AND t2=? AND t3=?",$t1,$t2,$t3);while ($o = $ret-&fetch()){& & echo $o-&nom.PHP_EOL;}?&
I ran into a real annoying bug/feature when using PDO for SQL statements that use SQL user variables.& I was working on some logic for a Geo Proximity Search for an events-venues system (sharing is caring so it's below) and it just wouldn't take and the errors returned were garbage. The SQL was sound as I verified it.& So if you're having this issue, I hope this helps.& What you need to do is break apart the query into two...From:&?php$sql="set @latitude=:set @longitude=:set @radius=20;set @lng_min = @longitude - @radius/abs(cos(radians(@latitude))*69);set @lng_max = @longitude + @radius/abs(cos(radians(@latitude))*69);set @lat_min = @latitude - (@radius/69);set @lat_max = @latitude + (@radius/69);SELECT *,3956 * 2 * ASIN(SQRT(POWER(SIN((@latitude - ABS(venue_lat)) * PI()/180 / 2),2) + COS(@latitude * PI()/180) * COS(ABS(venue_lat) * PI()/180) * POWER(SIN((@longitude - venue_lon) * PI()/180 / 2),2))) AS distanceFROM events LEFT JOIN venues ON venues.venue_id = events.venue_fkWHERE (venue_lon BETWEEN @lng_min AND @lng_max)AND (venue_lat BETWEEN @lat_min and @lat_max)AND events.event_date &= CURDATE()AND events.event_time &= CURTIME()ORDER BY distance DESC;";$stmt = $this-&_db-&prepare($sql);$stmt-&bindParam(':lat', $lat, PDO::PARAM_STR);$stmt-&bindParam(':lon', $lon, PDO::PARAM_STR);$stmt-&bindParam(':offset', $offset, PDO::PARAM_INT); $stmt-&bindParam(':max', $max, PDO::PARAM_INT);$stmt-&execute();?& To:&?php$sql = "SET @latitude=:SET @longitude=:SET @radius=20;SET @lng_min=@longitude - @radius/abs(cos(radians(@latitude))*69);SET @lng_max=@longitude + @radius/abs(cos(radians(@latitude))*69);SET @lat_min=@latitude - (@radius/69);SET @lat_max=@latitude + (@radius/69);"; $this-&_db-&setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_WARNING);$stmt = $this-&_db-&prepare($sql);$stmt-&bindParam(':lat', $lat, PDO::PARAM_STR);$stmt-&bindParam(':lon', $lon, PDO::PARAM_STR);$stmt-&execute();$sql = "SELECT *,(3956 * 2 * ASIN(SQRT(POWER(SIN((@latitude - ABS(venue_lat)) * PI()/180 / 2),2) + COS(@latitude * PI()/180) * COS(ABS(venue_lat) * PI()/180) * POWER(SIN((@longitude - venue_lon) * PI()/180 / 2),2)))) AS distanceFROM events LEFT JOIN venues ON venues.venue_id = events.venue_fkWHERE (venue_lon BETWEEN @lng_min AND @lng_max)AND (venue_lat BETWEEN @lat_min and @lat_max)AND events.event_date &= CURDATE()AND events.event_time &= CURTIME()ORDER BY distance DESCLIMIT :offset,:";& & & & & & && $stmt = $this-&_db-&prepare($sql); $stmt-&bindParam(':offset', $offset, PDO::PARAM_INT); $stmt-&bindParam(':max', $max, PDO::PARAM_INT);$stmt-&execute();?&Hope this helps anyone out there!
Be careful with PDO extends : if you use the smileaf's example, PDO will close the connection only at the end of the script, because of the "array( $this )" parameter used with the setAttribute() method.Instead, I use only this :& & $this-&setAttribute( PDO::ATTR_STATEMENT_CLASS, array( $this-&statementClassName, array() ) );And in prepare() and query() method you can populate the "dbh" if you really need it.
If you will make a OBJ row from PDO you can use this eg.$resKampange = $dbc-&prepare( "SELECT * FROM Table LIMIT 1" );$resKampange-&execute();$rowKampange = $resKampange-&fetch( PDO::FETCH_OB );echo $rowKampange-&felt1;Good lock :0)
There is a book titled "Learning PHP Data Objects" written by Dennis Popel and published by Packt. There is a post with further links (ordering, reviews) at author's blog:
When using persistent connections, pay attention not to leave the database connection in some kind of locked state. This can happen when you start a transaction by hand (i.e. not through the PDO-&beginTransaction() method), possibly even acquire some locks (e.g. with "SELECT ... FOR UPDATE", "LOCK TABLES ..." or in SQLite with "BEGIN EXCLUSIVE TRANSACTION") and then your PHP script ends with a fatal error, unhandled exception or under other circumstances that lead to an unclean exit.To use that database again, it may then be necessary to disable the persistence attribute to get a new database connection or restart the web server. (Persistent connections should not work with a PHP-CGI anyway.) It does not work (tested with PHP 5.2.3/WinXP and SQLite) to close a persistent database connection - it will not actually be closed but instead returned to PDO's connection pool.The only thing you can do to resolve the lock as a regular user (I imagine) is to try and get all of your persistent connections in a single script and unlock the tables resp. end the transactions with the appropriate SQL statements ("UNLOCK TABLES" in MySQL, "ROLLBACK" for transactions). Should they fail, there is no problem, but one or some of them might succeed and thereby resolve your locking problem.
From Oracle example:&?$stmt-&beginTransaction();$stmt-&execute();$stmt-&commit();?&PDOStatement has no beginTransaction(), nor commit(). Please fix documentation.
It seems MySQL doesn't support scrollable cursors. So unfortunately PDO::CURSOR_SCROLL wont work.
If you intend on extending PDOStatement and your using setAttribute(PDO::ATTR_STATEMENT_CLASS, ...)you must override the __construct() of your PDOStatement class.failure to do so will result in an error on any PDO::query() call.Warning: PDO::query() [function.PDO-query]: SQLSTATE[HY000]: General error: user-supplied statement does not accept constructor argumentsHere is a minimum PDO and PDOStatement class&?phpclass Database extends PDO {& & function __construct($dsn, $username="", $password="", $driver_options=array()) {& & & & parent::__construct($dsn,$username,$password, $driver_options);& & & & $this-&setAttribute(PDO::ATTR_STATEMENT_CLASS, array('DBStatement', array($this)));& & }}class DBStatement extends PDOStatement {& & public $dbh;& & protected function __construct($dbh) {& & & & $this-&dbh = $dbh;& & }}?&
Simple example to extends PDO&?phpclass connexion extends PDO{& public $query = null;& public function prepare( $statement, $driver_options = array() )& {& & $this-&query = $statement;& & return parent::prepare( $statement, $driver_options = array() );& }& public function last_query()& {& & return $this-&query;& }}class connexion_statement extends PDOStatement{& protected $pdo;& protected function __construct($pdo)& {& && $this-&pdo = $pdo;& }& public function fetchFirst()& {& & $row = $this-&fetch( PDO::FETCH_NUM );& & return $row[0];& }& public function fetch( $fetch_style = null, $cursor_orientation = null, $cursor_offset = null )& {& & $row = parent::fetch( $fetch_style, $cursor_orientation, $cursor_offset );& & if( is_array($row) )& & & foreach( $row as $key =& $value )& & & & if( strval(intval($value)) === $value )& & & & & $row[$key] = intval($value);& & & & elseif( strval(floatval($value)) === $value )& & & & & $row[$key] = floatval($value);& & return $row;& }& public function execute( $args = null )& {& & if( is_array( $args ) )& & & return parent::execute( $args );& & else& & {& & & $args = func_get_args();& & & return eval( 'return parent::execute( $args );' );& & }& }& public function last_query()& {& & return $this-&pdo-&last_query();& }}$pdo = new connexion( ... );$pdo-&setAttribute( PDO::ATTR_STATEMENT_CLASS, array( 'connexion_statement', array($pdo) ) );?&
If your having problems re-compiling PHP with PDO as shared module try this.--enable-pdo=shared--with-pdo-mysql=shared,/usr/local/mysql--with-sqlite=shared--with-pdo-sqlite=shared1. If PDO is built as a shared modules, all PDO drivers must also bebuilt as shared modules.2. If ext/pdo_sqlite is built as a shared module, ext/sqlite must alsobe built as a shared module.3. In the extensions entries, if ext/pdo_sqlite is built as a sharedmodule, php.ini must specify pdo_sqlite first, followed by sqlite.
Some useful links on PDO:
1. PDO Wiki (
)
2. Introducing PHP Data Objects (
), [226 KB], Wez Furlong,
3. The PHP 5 Data Object (PDO) Abstraction Layer and Oracle (
), [60.85 KB], Wez Furlong,
4. PDO - Why it should not be part of core PHP! (
), Critical review, [38.63 KB], Alan Knowles,
HTH,
R. Rajesh Jeba Anbiah
You may also have to edit /etc/freetds.conf. Make sure the TDS version is recent, e.g., "tds version = 8.0".
Hola, Sólo quiero se?alar que cuando usamos la clase PDO, si hay un error, en el log se mostrará la contrase?a de nuestra base de datos, lo cual sería bastante peligroso, porque la misma queda expuesta.Investigando he encontrado una clase llamada "SafePDO" que impide esto://&?phpClass SafePDO extends PDO {& & & & public static function exception_handler($exception) {& & & & & & die('Uncaught exception: '. $exception-&getMessage());& & & & }& & & & public function __construct($dsn, $username='', $password='', $driver_options=array()) {& & & & & & set_exception_handler(array(__CLASS__, 'exception_handler'));& & & & & & parent::__construct($dsn, $username, $password, $driver_options);& & & & & & restore_exception_handler();& & & & }}?&Para usarla hay que crear un archivo PHP llamado por ejemplo SafePDO con el contenido del archivo citado más arriba.Y en cuando tengamos que conectar a nuestra base de datos:&?php & & include_once('SafePDO.php' );& & $dsn = 'mysql:host='.DB_HOST.';dbname='.DB_NAME.';charset=utf8';& & $opt = array(& & & & PDO::ATTR_ERRMODE& & & & & & =& PDO::ERRMODE_EXCEPTION,& & & & PDO::ATTR_DEFAULT_FETCH_MODE =& PDO::FETCH_ASSOC,& & & & PDO::MYSQL_ATTR_INIT_COMMAND =& 'SET NAMES utf8'& & & & );& & $pdo = new SafePDO($dsn,DB_USER,DB_PASSWORD);?&
When using prepared statements there is no official PDO feature to show you the final query string that is submitted to a database complete with the parameters you passed.Use this simple function for debugging. The values you are passing may not be what you expect.&?php$query = "UPDATE users SET name = :user_name WHERE id = :user_id";$params = [':user_name' =& 'foobear', ':user_id' =& 1001];function build_pdo_query($string, $array) {& & $keys = array_map('strlen', array_keys($array));& & array_multisort($keys, SORT_DESC, $array);& & foreach($array as $k =& $v) {& & & & $replacement = is_numeric($v) ? $v : "'{$v}'";& & & & $string = str_replace($k, $replacement, $string);& & }& & return $string;}echo build_pdo_query($query, $params);& & ?&