|
Monday, September 19. 2005Big PDO Change
Today I've had the distinct pleasure of breaking nearly every single PDO based script in existence (my own code included), feels good
 . The break is the result of something that we, the PDO developers forgot to do. This being making PDO constants be class constants rather the polluting the main constant space. After much discussion on the topic at PHP|Works we've decided we need to fix this before it is too late (5.1 final release). So a bit of a pain at this time, should provide for a more robust and flexible interface. What does this mean in terms of your code? Well whenever you've used a PDO constant for example PDO_FETCH_NUM you'd now use PDO class constant PDO::FETCH_NUM. To simplify the conversion I offer the following Perl scriptlet: perl -p -i -e 's/PDO_/PDO::/g' [list of files] Trackbacks
Trackback specific URI for this entry
Comments
Display comments as
(Linear | Threaded)
Louis-Philippe Huberdeau on :
I guess this is one of those moments I'm glad I told my boss not to upgrade PHP before I left. I can already imagine the phone call.
Don't worry about security issues, it's an intranet. Örjan Persson on :
First look at PDO made me pretty confused! Upon creating a PDO object, if the connection to the RDBM was unsuccessfull it would raise an exception. But not on query errors etc. Would be nice to know why this is so?
Ilia Alshanetsky on :
By default PDO is silent of query errors, however you can change that by setting the error mode so that either warnings or exceptions are raised. In this respect PDO has by far the most flexible error handler in all of PHP.
Lukas on :
Also note that this kind of behaviour will likely become somewhat standard for PHP extensions. That is failures in the constructor will lead to an exception being thrown, but errors during operation will only throw an exception if you specifically enable this has the preferred error handling.
Örjan Persson on :
That's just awesome! PDO is a really nice piece of software. I've tried to find this information elsewhere and I'm glad that the only thing I didn't like about PDO now is gone.
Another good thing is that I didn't finish my own layer ontop of PDO which threw exceptions more often and can now just delete it.  For others looking for this information, check out the attribute PDO::ATTR_ERRMODE. PDO's design is just brilliant. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||
