InnoDB on selected tables

[lekkereten]

e.g.

atcommandlog
charlog
chatlog
global_reg_value
inventory
loginlog
picklog
sc_data
skill
storage

I'm not a expert to know all the InnoDB advantages vs MyISAM, I only heard it performs better for tables that rely too much on alter/delete/insert/update/select

discuss.

[Panallox]

Correct, it's useful for tables which harbour large amounts of data, and are read from/written to frequently. The major advantage, or usage, of converting the tables to InnoDB is for when external applications attempt to access the tables at the same time as the server executables are active.

Otherwise, because the executables are non-threaded and all commands are executed linearly, there's not much reason to convert them to InnoDB by default since our executables don't require them to be so (there's not really any instances where table-level locking interferes with the flow of the executables, without external applications accessing the data.)

It's recommended for when a server is accessing the logs frequently (control panels, custom administration searches etc.) but not much benefit for the executables alone.

[lekkereten]

I see. Thanks for clarifying this out.

[lekkereten]

I just started my Database class and we're using InnoDB in everything.

Correct me if I'm wrong but, wouldn't it be better to use some keys to automate the process of deletion of data e.g. in delete_char_sql?

[JayPee]

I think in MyISAM transaction does not work while in InnoDB it works