<?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: So much for good database design&#8230;</title> <atom:link href="http://www.brandonchecketts.com/archives/so-much-for-good-database-design/feed" rel="self" type="application/rss+xml" /><link>http://www.brandonchecketts.com/archives/so-much-for-good-database-design</link> <description>Web Programming, Linux System Administation, and other geeky stuff</description> <lastBuildDate>Thu, 05 Jan 2012 11:11:59 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Brandon</title><link>http://www.brandonchecketts.com/archives/so-much-for-good-database-design/comment-page-1#comment-14</link> <dc:creator>Brandon</dc:creator> <pubDate>Fri, 19 Jan 2007 17:31:03 +0000</pubDate> <guid
isPermaLink="false">http://www.brandonchecketts.com/blog/archives/5#comment-14</guid> <description>Instead of having a bunch of separate tables, I&#039;d generalize each of the tables, add add a &#039;blog_id&#039; column that would associate a particular comment/user/etc, to a specific blog.With that being said, the way theirs currently works does actually scale well with hundreds of thousands of users spread across multiple database servers.  If you were to do it the &#039;traditional&#039; way, you&#039;d end up needing a very hefty database server because it would would be searching through tens of millions of rows sometimes.</description> <content:encoded><![CDATA[<p>Instead of having a bunch of separate tables, I&#8217;d generalize each of the tables, add add a &#8216;blog_id&#8217; column that would associate a particular comment/user/etc, to a specific blog.</p><p>With that being said, the way theirs currently works does actually scale well with hundreds of thousands of users spread across multiple database servers.  If you were to do it the &#8216;traditional&#8217; way, you&#8217;d end up needing a very hefty database server because it would would be searching through tens of millions of rows sometimes.</p> ]]></content:encoded> </item> <item><title>By: Aoleon</title><link>http://www.brandonchecketts.com/archives/so-much-for-good-database-design/comment-page-1#comment-13</link> <dc:creator>Aoleon</dc:creator> <pubDate>Fri, 19 Jan 2007 17:24:57 +0000</pubDate> <guid
isPermaLink="false">http://www.brandonchecketts.com/blog/archives/5#comment-13</guid> <description>Hi,I recently installed WP Mu on my site and had the exact same thoughts when I saw the DB design.  However, I am not a DB programmer.  I would love to know  your thoughts on what WOULD be a good design for WP Mu.  And how it might work!Thanks!Aoleon.</description> <content:encoded><![CDATA[<p>Hi,</p><p>I recently installed WP Mu on my site and had the exact same thoughts when I saw the DB design.  However, I am not a DB programmer.  I would love to know  your thoughts on what WOULD be a good design for WP Mu.  And how it might work!</p><p>Thanks!</p><p>Aoleon.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 4/14 queries in 0.004 seconds using disk

Served from: www.brandonchecketts.com @ 2012-02-04 03:22:15 -->
