<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 24 May 2012 05:14:07 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chad Lung's Blog: A quick intro to using PHP PDO with MySQL]]></title>
      <guid>http://www.phpdeveloper.org/news/16059</guid>
      <link>http://www.phpdeveloper.org/news/16059</link>
      <description><![CDATA[<p>
<i>Chad Lung</i> has <a href="http://www.giantflyingsaucer.com/blog/?p=2478">posted an introduction to PDO</a>, PHP Data Objects, in a simple PHP script:
</p>
<blockquote>
<a href="http://www.php.net/manual/book.pdo.php">PHP PDO</a> (PHP Data Objects) ship with PHP 5.1 and above and is very easy to work with. Today I'm going to show you one way of performing CRUD actions on a <a href="http://www.mysql.com/">MySQL</a> database using PDO. Keep in mind what I'll show you is only one way of doing things and just a fraction of what <a href="http://www.php.net/manual/intro.pdo.php">PDO</a> can do.
</blockquote>
<p>
He shows how to connect it to your MySQL database (via the connect string) and, based on his sample "pdo-demo.users" table, use prepared statements to insert and select data into/out of the table. There's a full code listing at the end showing a comprehensive view of each of the types - select, insert, update and delete.
</p>]]></description>
      <pubDate>Thu, 17 Mar 2011 09:52:55 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Lukas Smith's Blog: Let's think PDO!]]></title>
      <guid>http://www.phpdeveloper.org/news/13429</guid>
      <link>http://www.phpdeveloper.org/news/13429</link>
      <description><![CDATA[<p>
<i>Lukas Smith</i> has <a href="http://pooteeweet.org/blog/1565/p/1">formally kicked off</a> a restart of the PDO (PHP Data Objects) abstraction layer, trying to get interest back into this part of the PHP project and get developers back into patching and creating more features on it as a whole.
</p>
<blockquote>
The problem with PDO's current state is that there are just so many bugs open that it seems like a maintain. Plus the original creator(s) are busy with other things, which means the learning curve is steep. Which makes it all the more important that we both have new guys as well as experienced core developers on this. I think for too long we have waited for RDBMS vendors to bring in the momentum. However since we decided to not play according to <a href="http://news.php.net/php.pdo/1">the "rules" they have proposed</a>, its obviously our job and not theirs.
</blockquote>
<p>
He asks that all that are interested in closing out those bugs and really getting the development of PDO back on track <a href="http://news.php.net/php.pdo">sign up for the mailing list</a> and check out <a href="http://wiki.php.net/internals/pdo/brainstorming">the brainstorming page</a> on the PHP wiki on general ideas and thoughts on where the project should be headed.
</p>]]></description>
      <pubDate>Mon, 26 Oct 2009 10:32:03 -0500</pubDate>
    </item>
  </channel>
</rss>

