Gabor Hojtsy wrote:

Hi!

Gerhard, how would you enforce myisam on shared hosts? Is is reliably available everywhere?

myisam is the standard table engine for mysql, so I guess it would. If the merge engine is available everywhere is a good question, though. Guess you could try the example here: http://mysql.com/doc/refman/5.0/en/merge-storage-engine.html Cheers, Gerhard

Larry Garfield wrote: NB: I'd really appreciate it if people on this list could quote messages appropriately and not attach the old message at the bottom.

What exactly would be the benefit here? My understanding is that InnoDB is already better for write-heavy tables (while MyISAM is read-optimized), so I'm not sure what the goal is.

First of all, not everybody uses innodb. We can safely assume that myisam is the standard table type that 98% of all Drupal installs use if they use mysql. We actually used to enforce the myisam table type.

And what would this get us that UNION would not?

A merge table is basically a permanent union (Note: I am not a big database expert, if somebody is, please explain it better). You wouldn't need to bother about knowing how many tables you want to get the data from, etc. My idea is to split our accesslog (and watchdog) into accesslog_storage and accesslog_insert, and add both to a merged accesslog table. During cron runs, the content of the _insert table would be added to the _storage table and the _insert table would be emptied, keeping it nice and small. If now somebody wants to collects a _real_ lot of data this way he'd want to split up the accesslog_storage table further. He could do so and simply add the new tables to the merged table as well and would not need to add the tables to some union statement. Cheers, Gerhard

On 8/13/06, karoly@negyesi.net <karoly@negyesi.net> wrote:

Gerhard, go for it. Create an enable merge tables page which simply dies if that facility is not available and if merge is not switched on, show only the insert table on the watchdog page. Everyone gets something...

Yep, that sounds like a good solution -- there are then 2 settings -- 1) for the cron'd clean up (acceslog_insert) and 2) for storage. i.e. (1) keep logs for 3 days, (2) keep logs for 3 months. If merge support doesn't work in some way, just the smaller, accesslog_insert is displayed/handled. There was that watchdog hook looking to do flatfiles or something, too? Other means of dumping data could be done by contrib modules as needed. -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com

I don't like to impose an infrastructure default that may not be available for most users, nor can they enable it if they want to (think shared hosting where Inno or Merge may not be available). hook_accesslog() and hook_watchdog() is the way to go. We can ship default modules that do what is done today, but contributors can write modules that do syslog, SNMP, pager, monit, nagios, ....etc. The possibilities are endless. I may even volunteer to write a contrib syslog module for both hooks if no one else is working on it.

On 13-Aug-06, at 7:27 PM, Khalid B wrote:

I don't like to impose an infrastructure default that may not be available for most users, nor can they enable it if they want to (think shared hosting where Inno or Merge may not be available).

hook_accesslog() and hook_watchdog() is the way to go.

So...yes, agree. We still have to figure out what to support in core. I guess that means leaving accesslog as is, and having a logarchive module that does as Gerhard has proposed. -- Boris