<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: A first look at the Zend Framework</title>
	<link>http://www.phpit.net/article/first-look-zend-framework/</link>
	<description>PHPit has dozens of PHP articles, codesnippets and FAQ's.</description>
	<pubDate>Fri, 16 May 2008 05:05:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Lee Doolan</title>
		<link>http://www.phpit.net/article/first-look-zend-framework/#comment-10256</link>
		<pubDate>Sun, 06 Aug 2006 18:35:48 +0000</pubDate>
		<guid>http://www.phpit.net/article/first-look-zend-framework/#comment-10256</guid>
					<description>Ok, so the argument to fetchAll is a string.  So, like,
    $result = $db-&#62;fetchAll("SELECT * FROM round_table WHERE noble_title = 'Sir' ORDER BY first_name limit 10,20")

does what you want, right?</description>
		<content:encoded><![CDATA[<p>Ok, so the argument to fetchAll is a string.  So, like,<br />
    $result = $db-&gt;fetchAll(&#8221;SELECT * FROM round_table WHERE noble_title = &#8216;Sir&#8217; ORDER BY first_name limit 10,20&#8243;)</p>
<p>does what you want, right?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: zbijowski::marcin</title>
		<link>http://www.phpit.net/article/first-look-zend-framework/#comment-696</link>
		<pubDate>Wed, 08 Mar 2006 18:46:07 +0000</pubDate>
		<guid>http://www.phpit.net/article/first-look-zend-framework/#comment-696</guid>
					<description>&lt;strong&gt;Zend Framework - wejście smoka&lt;/strong&gt;

Kilka dni temu została opublikowana pierwsza wersja zapowiadanego od dluższego czasu Zend Framework oznaczona numerkiem 0.1.1. Podszedłem do tego dość sceptycznie i z dystansem, bo publikacja tak wczesnej wersji mogła okazać się niewypałem, a ...</description>
		<content:encoded><![CDATA[<p><strong>Zend Framework - wejście smoka</strong></p>
<p>Kilka dni temu została opublikowana pierwsza wersja zapowiadanego od dluższego czasu Zend Framework oznaczona numerkiem 0.1.1. Podszedłem do tego dość sceptycznie i z dystansem, bo publikacja tak wczesnej wersji mogła okazać się niewypałem, a &#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Matthijs</title>
		<link>http://www.phpit.net/article/first-look-zend-framework/#comment-674</link>
		<pubDate>Mon, 06 Mar 2006 18:19:18 +0000</pubDate>
		<guid>http://www.phpit.net/article/first-look-zend-framework/#comment-674</guid>
					<description>Indeed it will be very interesting to see where this framework will go. I also like the input filtering approach in which the access to the raw data is removed. Marco Tabini wrote about this (or a similar) concept in the feb issue of PHP architect, calling it poka-yoke, which is Japanese for “fail-safe mechanism.”</description>
		<content:encoded><![CDATA[<p>Indeed it will be very interesting to see where this framework will go. I also like the input filtering approach in which the access to the raw data is removed. Marco Tabini wrote about this (or a similar) concept in the feb issue of PHP architect, calling it poka-yoke, which is Japanese for “fail-safe mechanism.”
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: tim</title>
		<link>http://www.phpit.net/article/first-look-zend-framework/#comment-673</link>
		<pubDate>Mon, 06 Mar 2006 16:27:44 +0000</pubDate>
		<guid>http://www.phpit.net/article/first-look-zend-framework/#comment-673</guid>
					<description>So, compare these four lines:

$select-&#62;from('round_table', '*');
$select-&#62;where('noble_title = ?', 'Sir');
$select-&#62;order('first_name');
$select-&#62;limit(10,20);

"SELECT * FROM round_table WHERE noble_title = 'Sir' ORDER BY first_name limit 10,20"

How is the 4 line object statement (copied below) "so much easier" than a single line SQL statement?

The SQL can be formatted however the user wishes, remaining readable, and happily including variables.

  SELECT * FROM round_table 
  WHERE noble_title = 'Sir' 
  ORDER BY first_name 
  LIMIT 10,20

The SQL-way has less typing, reads as an English sentence, both enhancing creation and maintenance. Importantly, the SQL select statement can be made in one string, so errors where a piece of the object has not been updated since a previous call, but the SQL still executes, are not possible.

For getting the job done, bog-standard PHP still seems to rule for me. My prediction is that the X on X fad will maintain a noisy list of supporters, but the 80% apps that make money, help us discover things, and change the world, are going to remain, like php, simple enough to get the job done, and leave SQL alone to do its lovely specialism.

I think Andy is right: Scaffolding saves 5 minutes once. Php saves you those minutes every hour for the rest of your coding. It stays out of your way while you work, understanding that no one can do the work for you, least of all a dumb language. Work remains a product of mass acceleration and distance: that makes it fundamentally hard.</description>
		<content:encoded><![CDATA[<p>So, compare these four lines:</p>
<p>$select-&gt;from(&#8217;round_table&#8217;, &#8216;*&#8217;);<br />
$select-&gt;where(&#8217;noble_title = ?&#8217;, &#8216;Sir&#8217;);<br />
$select-&gt;order(&#8217;first_name&#8217;);<br />
$select-&gt;limit(10,20);</p>
<p>&#8220;SELECT * FROM round_table WHERE noble_title = &#8216;Sir&#8217; ORDER BY first_name limit 10,20&#8243;</p>
<p>How is the 4 line object statement (copied below) &#8220;so much easier&#8221; than a single line SQL statement?</p>
<p>The SQL can be formatted however the user wishes, remaining readable, and happily including variables.</p>
<p>  SELECT * FROM round_table<br />
  WHERE noble_title = &#8216;Sir&#8217;<br />
  ORDER BY first_name<br />
  LIMIT 10,20</p>
<p>The SQL-way has less typing, reads as an English sentence, both enhancing creation and maintenance. Importantly, the SQL select statement can be made in one string, so errors where a piece of the object has not been updated since a previous call, but the SQL still executes, are not possible.</p>
<p>For getting the job done, bog-standard PHP still seems to rule for me. My prediction is that the X on X fad will maintain a noisy list of supporters, but the 80% apps that make money, help us discover things, and change the world, are going to remain, like php, simple enough to get the job done, and leave SQL alone to do its lovely specialism.</p>
<p>I think Andy is right: Scaffolding saves 5 minutes once. Php saves you those minutes every hour for the rest of your coding. It stays out of your way while you work, understanding that no one can do the work for you, least of all a dumb language. Work remains a product of mass acceleration and distance: that makes it fundamentally hard.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
