On Wed, Jan 6, 2010 at 10:48 PM, Greg Donald <[email protected]> wrote: > On Mon, Jan 4, 2010 at 7:22 PM, Steven S. Critchfield > <[email protected]> wrote: >> Now that depends. I would agree for first rev of a project. But when >> you start to see bottlenecks, you can custom write the query for that >> section. > > In a high load environment it is preferable to break the table into > more tables with less fields so you simply don't have to write the > custom query. That's the idea behind vertical databases and database > partitioning in general.
Just be careful that you don't end up with a schema like Magento's EAV mess. http://www.magentocommerce.com/wiki/development/magento_database_diagram Another approach is to shard the database http://www.jurriaanpersyn.com/archives/2009/02/12/database-sharding-at-netlog-with-mysql-and-php/ Admittedly at this point unless you must use MySQL why not use something else like bigtable for instance. > > On the topic of bottlenecks, standards features having any potential > for causing bottlenecks are mostly optional under MySQL. If you're a > standards nazi and use MySQL, you'll be happy to know the --ansi > option is documented here: > > http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html > There is still no substitute for knowing in MySQL when to use which db engine. Sure, MySQL can scale and grow and support as many queries as one may want to have it respond to. The trouble is, at a certain point it is just less resistance to use something else unless you are forced to use MySQL due to legacy, compatibility, or (office) political reasons. Of course the original point of this thread was over a petition to "save" MySQL. MySQL appears to be safe enough already as there are already active forks. http://drizzle.org/wiki/Main_Page Andrew McElroy > > -- > Greg Donald > http://destiney.com/
-- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
