Comments on: Accessing Databases with PDO: A Primer http://www.brandonsavage.net/pdo-primer/ The personal blog of Brandon Savage. Contains entries of a personal and professional nature focusing on PHP, Apple, LAMP, MySQL and Washington, DC. Thu, 29 Jul 2010 11:09:38 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Symen http://www.brandonsavage.net/pdo-primer/#comment-1507 Symen Wed, 07 Oct 2009 09:40:52 +0000 http://www.brandonsavage.net/?p=753#comment-1507 Hi Brandon, Nice post. I recently discovered Doctrine (http://www.doctrine-project.org/), which is an object relational mapper (ORM) for PHP 5.2.3+ that sits on top of a powerful database abstraction layer (DBAL), and it looks promising. Your post reminded me of it. You should check it out. Hi Brandon,

Nice post.
I recently discovered Doctrine (http://www.doctrine-project.org/), which is an object relational mapper (ORM) for PHP 5.2.3+ that sits on top of a powerful database abstraction layer (DBAL), and it looks promising. Your post reminded me of it. You should check it out.

]]> By: Dennis http://www.brandonsavage.net/pdo-primer/#comment-1493 Dennis Mon, 05 Oct 2009 18:26:11 +0000 http://www.brandonsavage.net/?p=753#comment-1493 It's not quite right to state that mysql_ functions do not support transactions; you can always do mysql_query("BEGIN") and mysql_query("COMMIT") or mysql_query("ROLLBACK"); Also, it should be noted, that fro non-supporting engines, the transaction statements will be ignored. There is a book published on PDO: http://www.packtpub.com/Learning-PHP-Data-Objects-Open-Source/book It’s not quite right to state that mysql_ functions do not support transactions; you can always do mysql_query(“BEGIN”) and mysql_query(“COMMIT”) or mysql_query(“ROLLBACK”);

Also, it should be noted, that fro non-supporting engines, the transaction statements will be ignored.

There is a book published on PDO: http://www.packtpub.com/Learning-PHP-Data-Objects-Open-Source/book

]]> By: Les http://www.brandonsavage.net/pdo-primer/#comment-1491 Les Mon, 05 Oct 2009 14:50:58 +0000 http://www.brandonsavage.net/?p=753#comment-1491 Was looking forward to using PDO in the early days but it never did catch on for me. Rolled my own and nothing wrong with that, just as secure in my opinion. Was looking forward to using PDO in the early days but it never did catch on for me.

Rolled my own and nothing wrong with that, just as secure in my opinion.

]]> By: sapphirecat http://www.brandonsavage.net/pdo-primer/#comment-1490 sapphirecat Mon, 05 Oct 2009 14:24:07 +0000 http://www.brandonsavage.net/?p=753#comment-1490 I used PDO in the 5.1.x series for a former employer, and I would rank it as one of the biggest technical mistakes I ever made. It had a tendency to segfault if you tried to subclass it, or if you didn't close the statements before the connection. This last one was extra fun because PHP would apparently free objects at request shutdown in the order they were created, guaranteeing a crash if any statements were still open. I made it work then, with delegates and careful use of closeCursor(), but I would never do it again. Life's too short for rushing headlong into bugs. I used PDO in the 5.1.x series for a former employer, and I would rank it as one of the biggest technical mistakes I ever made. It had a tendency to segfault if you tried to subclass it, or if you didn’t close the statements before the connection. This last one was extra fun because PHP would apparently free objects at request shutdown in the order they were created, guaranteeing a crash if any statements were still open.

I made it work then, with delegates and careful use of closeCursor(), but I would never do it again. Life’s too short for rushing headlong into bugs.

]]>