<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Use one DB connection on your custom wordpress install</title>
	<atom:link href="http://pureform.wordpress.com/2008/05/11/use-one-db-connection-on-your-custom-wordpress-install/feed/" rel="self" type="application/rss+xml" />
	<link>http://pureform.wordpress.com/2008/05/11/use-one-db-connection-on-your-custom-wordpress-install/</link>
	<description>Adventures in PHP / DHTML / CSS and MySQL</description>
	<lastBuildDate>Thu, 12 Nov 2009 09:41:53 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: pureform</title>
		<link>http://pureform.wordpress.com/2008/05/11/use-one-db-connection-on-your-custom-wordpress-install/#comment-29</link>
		<dc:creator>pureform</dc:creator>
		<pubDate>Mon, 12 May 2008 19:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://pureform.wordpress.com/?p=12#comment-29</guid>
		<description>Hmmm ... I had no idea :-) ... makes a lot more sense for update purposes. My whole experience has been, &quot;here&#039;s WordPress, make it work in two days&quot;, and I don&#039;t know much about it&#039;s internal workings.

I&#039;ve had the 20 lbs. sledge approach where I search for functions and rewrite them to suit my needs instead of working &lt;em&gt;with&lt;/em&gt; the code.

Thanks for the tip :-)</description>
		<content:encoded><![CDATA[<p>Hmmm &#8230; I had no idea :-) &#8230; makes a lot more sense for update purposes. My whole experience has been, &#8220;here&#8217;s WordPress, make it work in two days&#8221;, and I don&#8217;t know much about it&#8217;s internal workings.</p>
<p>I&#8217;ve had the 20 lbs. sledge approach where I search for functions and rewrite them to suit my needs instead of working <em>with</em> the code.</p>
<p>Thanks for the tip :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ozh</title>
		<link>http://pureform.wordpress.com/2008/05/11/use-one-db-connection-on-your-custom-wordpress-install/#comment-28</link>
		<dc:creator>Ozh</dc:creator>
		<pubDate>Mon, 12 May 2008 19:15:10 +0000</pubDate>
		<guid isPermaLink="false">http://pureform.wordpress.com/?p=12#comment-28</guid>
		<description>That&#039;s a cool hack indeed, but it gets overwritten each time you upgrade WP.
I think a better solution might be possible.

wp-includes/wp-db.php is included by function require_wp_db() in wp-includes/functions.php, which first checks if wp-content/db.php exists, and if not, includes wp-db.php

So, basically, I think you could simply replicate most of wp-db.php in your own wp-content/db.php (which would not get overwritten) and always be able to upgrade WP without minding about having to hack core files.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a cool hack indeed, but it gets overwritten each time you upgrade WP.<br />
I think a better solution might be possible.</p>
<p>wp-includes/wp-db.php is included by function require_wp_db() in wp-includes/functions.php, which first checks if wp-content/db.php exists, and if not, includes wp-db.php</p>
<p>So, basically, I think you could simply replicate most of wp-db.php in your own wp-content/db.php (which would not get overwritten) and always be able to upgrade WP without minding about having to hack core files.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
