<?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, 23 May 2013 09:21:06 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lukas Smith's Blog: LiveUser installer and MDB2_Schema magic]]></title>
      <guid>http://www.phpdeveloper.org/news/4818</guid>
      <link>http://www.phpdeveloper.org/news/4818</link>
      <description><![CDATA[<i>Lukas Smith</i>, in his <a href="http://pooteeweet.org/blog/312">latest blog entry</a> spotlights a feature added a while back to the MDB2 database package he develops - the ability to disable the execution of SQL queries.
<p>
<quote>
<i>
A long while ago I added a seemingly idiotic feature to MDB2: The ability to disable the execution of queries.
<p>
The idea was that with the combination of a debug handler it would be possible for people to create a dump of SQL queries generated by MDB2_Schema during the installation or updating of a schema. All you would need to do is write up a debug handler for MDB2. Finally you would set the "disable_query" parameter when calling MDB2_Schema::updateDatabase() to true.
</i>
</quote>
<p>
He also <a href="http://pooteeweet.org/blog/312">includes some brief code</a> and some notes about the further development of the idea and its inclusion into other apps (LiveUser). There's also some <a href="http://pooteeweet.org/LiveUser/dump.sql">sample</a> <a href="http://pooteeweet.org/LiveUser/dump_auto.sql">output</a> from one of his scripts to give you an idea of what the end result will be.]]></description>
      <pubDate>Thu, 09 Feb 2006 06:41:59 -0600</pubDate>
    </item>
  </channel>
</rss>
