<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: PHP MySQLi and Multiple Prepared Statements</title>
	<atom:link href="http://www.ioncannon.net/programming/889/php-mysqli-and-multiple-prepared-statements/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ioncannon.net/programming/889/php-mysqli-and-multiple-prepared-statements/</link>
	<description>Thoughts on Software Development and Engineering</description>
	<lastBuildDate>Thu, 05 Jan 2012 16:35:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Using Cursors with PHP MySQLi and Multiple Prepared Statements</title>
		<link>http://www.ioncannon.net/programming/889/php-mysqli-and-multiple-prepared-statements/comment-page-1/#comment-166554</link>
		<dc:creator>Using Cursors with PHP MySQLi and Multiple Prepared Statements</dc:creator>
		<pubDate>Tue, 30 Mar 2010 11:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ioncannon.net/?p=889#comment-166554</guid>
		<description>[...] my post on using PHP MySQLi and multiple prepared statements at the same time someone commented that using cursors could do the same thing. With that comment I dug some more and [...]</description>
		<content:encoded><![CDATA[<p>[...] my post on using PHP MySQLi and multiple prepared statements at the same time someone commented that using cursors could do the same thing. With that comment I dug some more and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: carson</title>
		<link>http://www.ioncannon.net/programming/889/php-mysqli-and-multiple-prepared-statements/comment-page-1/#comment-163242</link>
		<dc:creator>carson</dc:creator>
		<pubDate>Tue, 16 Feb 2010 03:03:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.ioncannon.net/?p=889#comment-163242</guid>
		<description>@bill I didn&#039;t want to return a ton of duplicated data from the join is all. It feels cleaner to make the second round trip.</description>
		<content:encoded><![CDATA[<p>@bill I didn&#039;t want to return a ton of duplicated data from the join is all. It feels cleaner to make the second round trip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Karwin</title>
		<link>http://www.ioncannon.net/programming/889/php-mysqli-and-multiple-prepared-statements/comment-page-1/#comment-163230</link>
		<dc:creator>Bill Karwin</dc:creator>
		<pubDate>Mon, 15 Feb 2010 21:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.ioncannon.net/?p=889#comment-163230</guid>
		<description>Is this a simplified example?  Why don&#039;t you do this in one query using a join:

select p.id, p.title, c.user_id 
from post p left outer join comment c on p.id = c.post_id
where p.id = 1000;

Granted, that will give return &lt;i&gt;n&lt;/i&gt; rows with repeating values in the post columns, but you won&#039;t have to worry about commands out of sync.</description>
		<content:encoded><![CDATA[<p>Is this a simplified example?  Why don&#039;t you do this in one query using a join:</p>
<p>select p.id, p.title, c.user_id<br />
from post p left outer join comment c on p.id = c.post_id<br />
where p.id = 1000;</p>
<p>Granted, that will give return <i>n</i> rows with repeating values in the post columns, but you won&#039;t have to worry about commands out of sync.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrey</title>
		<link>http://www.ioncannon.net/programming/889/php-mysqli-and-multiple-prepared-statements/comment-page-1/#comment-162992</link>
		<dc:creator>Andrey</dc:creator>
		<pubDate>Tue, 09 Feb 2010 13:47:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.ioncannon.net/?p=889#comment-162992</guid>
		<description>You can also use cursors, with 5.0+ then you don&#039;t need to store the result. Cursors fetch data row by row and every fetch means a round-trip to the server. The data is materialized on the server side. Thus, if the results are big cursors are not recommended.</description>
		<content:encoded><![CDATA[<p>You can also use cursors, with 5.0+ then you don&#039;t need to store the result. Cursors fetch data row by row and every fetch means a round-trip to the server. The data is materialized on the server side. Thus, if the results are big cursors are not recommended.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.446 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-01-17 08:46:25 -->

