[Koha] Truncating the nozebra table in koha DB

[LAURENT Henri-Damien]

Le 02/09/2011 21:58, Robin Sheat a écrit :
> Op zaterdag 3 september 2011 01:35:42 schreef LAURENT Henri-Damien:
>> check that the table is MyISAM and not innodb, unless you want to keep a
>> huge innodb file......
> 
> Alternately, use innodb_file_per_table
> 
> http://dev.mysql.com/doc/refman/5.5/en/innodb-multiple-tablespaces.html
Well, even with Innodb_file_per_table, the innodb data files are not
resized on truncation. For instance, if your session or zebraqueue file
grow to 1 Million entries, and taking up to 1 G for data, then
truncating would not change that file size. This can be considered as a
problem.
Since zebraqueue or sessions are tables without external constraints, I
would consider it safer to have them in MyIsam.
innodb_file_per_table is also very nice to tune your mysql access. But
those tables sessions and zebraqueue are to be considered apart from any
other.
-- 
Henri-Damien LAURENT