<?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: Post Meta</title>
	<atom:link href="http://dougal.gunters.org/blog/2004/02/26/post-meta/feed/" rel="self" type="application/rss+xml" />
	<link>http://dougal.gunters.org/blog/2004/02/26/post-meta/</link>
	<description>WordPress, web development, and world domination.</description>
	<lastBuildDate>Sat, 11 Feb 2012 20:29:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19719</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Dougal</title>
		<link>http://dougal.gunters.org/blog/2004/02/26/post-meta/#comment-397</link>
		<dc:creator>Dougal</dc:creator>
		<pubDate>Mon, 01 Mar 2004 19:28:18 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-397</guid>
		<description>Yeah, I almost started to do a join, but I quickly saw that it was going go get really messy trying to do it that way. That&#039;s why I switched to just building a &#039;cache&#039; variable with the metadata for the currently selected set of posts.

It&#039;s only one extra query per page load, so it shouldn&#039;t be a big deal. I just have to wonder how well optimized MySQL&#039;s IN clause is when the $post_id_list gets big.</description>
		<content:encoded><![CDATA[<p>Yeah, I almost started to do a join, but I quickly saw that it was going go get really messy trying to do it that way. That&#8217;s why I switched to just building a &#8216;cache&#8217; variable with the metadata for the currently selected set of posts.</p>
<p>It&#8217;s only one extra query per page load, so it shouldn&#8217;t be a big deal. I just have to wonder how well optimized MySQL&#8217;s IN clause is when the $post_id_list gets big.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://dougal.gunters.org/blog/2004/02/26/post-meta/#comment-391</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sat, 28 Feb 2004 16:59:49 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-391</guid>
		<description>Oops, sorry was still stuck in my serialized thought process, a JOIN probably wouldn&#039;t work well since there is a one to many relationship there.</description>
		<content:encoded><![CDATA[<p>Oops, sorry was still stuck in my serialized thought process, a JOIN probably wouldn&#8217;t work well since there is a one to many relationship there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://dougal.gunters.org/blog/2004/02/26/post-meta/#comment-389</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Fri, 27 Feb 2004 23:26:42 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-389</guid>
		<description>Was there a reason you decided not get it in the same query with a LEFT JOIN?</description>
		<content:encoded><![CDATA[<p>Was there a reason you decided not get it in the same query with a LEFT JOIN?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dougal</title>
		<link>http://dougal.gunters.org/blog/2004/02/26/post-meta/#comment-388</link>
		<dc:creator>Dougal</dc:creator>
		<pubDate>Fri, 27 Feb 2004 13:54:26 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-388</guid>
		<description>I&#039;ve added a new wp_postmeta database table. The structure is simple, just four fields: &lt;code&gt;meta_id, post_id, meta_key, meta_value&lt;/code&gt;. The tricky part was converting that flat structure into a hierarchical struct. I build a $post_meta_cache object in wp-blog-header.php which contains the metadata for the currently selected set of posts. That way, each page view only requires one extra query to fetch the metadata.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve added a new wp_postmeta database table. The structure is simple, just four fields: <code>meta_id, post_id, meta_key, meta_value</code>. The tricky part was converting that flat structure into a hierarchical struct. I build a $post_meta_cache object in wp-blog-header.php which contains the metadata for the currently selected set of posts. That way, each page view only requires one extra query to fetch the metadata.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://dougal.gunters.org/blog/2004/02/26/post-meta/#comment-386</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Thu, 26 Feb 2004 22:52:45 +0000</pubDate>
		<guid isPermaLink="false">//?p=#comment-386</guid>
		<description>Dougal, are you using a serialized array/object for the meta?</description>
		<content:encoded><![CDATA[<p>Dougal, are you using a serialized array/object for the meta?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: dougal.gunters.org @ 2012-02-11 20:22:23 by W3 Total Cache -->
