[Koha-bugs] [Bug 11136] action_logs should be a MyISAM table, not InnoDB

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11136

M. Tompsett <mtompset at hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22426|0                           |1
        is obsolete|                            |

--- Comment #5 from M. Tompsett <mtompset at hotmail.com> ---
Created attachment 24210
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=24210&action=edit
[SIGNED OFF] Bug 11136 - action_logs should be a MyISAM table, not InnoDB

The table action_logs is written too at a higher rate than practically
any other table. Additionally, action_logs has no foreign key
constraints. It seems that this would be a somewhat unique situation
where using MyISAM would provide quite a performance boost for large
sites with many transactions that use the Action Logs.

TEST PLAN
---------

NOTE: These instructions toast the database, so backup as needed!

1) open mysql client
2) use the koha database
3) show create table action_logs;
-- This should currently be InnoDB listed as the engine.
4) close mysql client
5) apply patch
6) ./installer/data/mysql/updatedatabase.pl
-- This should apply the update.
7) open mysql client
8) use the koha database
9) show create table action_logs;
-- The engine should now be MyISAM.
10) drop the koha database
11) create the koha database
12) close mysql client
13) go to the staff client and do the web installation
14) open mysql client
15) use the koha database
16) show create table action_logs;
-- The engine should now be MyISAM.
   Also, the AUTO_INCREMENT won't be shown, since the log file
    is currently empty.

Signed-off-by: Mark Tompsett <mtompset at hotmail.com>

-- 
You are receiving this mail because:
You are watching all bug changes.