[development] mysql merge tables and partitioning

[Walt Daniels]

This sounds like a good case for an abstraction. 

-----Original Message-----
From: development-bounces at drupal.org [mailto:development-bounces at drupal.org]
On Behalf Of Rowan Kerr
Sent: Thursday, February 01, 2007 10:30 AM
To: development at drupal.org
Subject: Re: [development] mysql merge tables and partitioning

What about using ARCHIVE table instead of MERGE. It's basically optimized
for watchdog style data.

http://dev.mysql.com/doc/refman/5.1/en/archive-storage-engine.html

To me, it doesn't make sense to spend time making the db schema more
complicated and relying on a table type that is already deprecated (and
implemented only by one database). (Didn't people want a cleaner db design
for the next release?). If you really want this type of behaviour for large
log tables, think about working on it from a partitioning point of view
which is supported by more db's (and will be more future-proof).

-Rowan



--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.19/663 - Release Date: 2/1/2007
2:28 PM