http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7957
Paul Poulain <paul.poul...@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul.poul...@biblibre.com --- Comment #9 from Paul Poulain <paul.poul...@biblibre.com> --- (In reply to comment #8) > > Frédéric, in kohastructure.sql, the only table which use MyISAM engine > > is pending_offline_operations. In my databases, subscription and > > borrowers table both use InnoDB, so why they don't in your database? > > Good question. Since it's a library currently using Koha database, I'm > sure this issue will occur in real life for others. It means that your > enhancement won't work at all for some (a lot) of libraries. Maybe this > question could be raised on koha-devel list? pointing to this bug. > > Engine used for all table: > > SELECT TABLE_NAME, ENGINE > FROM information_schema.TABLES > WHERE TABLE_SCHEMA = DATABASE() > > I have a lot of Koha DB mixing MyISAM and InnoDB. Why? I have no clue. Maybe that's because, during the upgrade from 2.x to 3.0, you missed some message speaking of a problem ? Because the update22to30.pl script update all tables to innoDB. # MOVE all tables TO UTF-8 and innoDB $sth = $dbh->prepare("show table status"); $sth->execute; while ( my $table = $sth->fetchrow_hashref ) { next if $table->{Name} eq 'marc_word'; next if $table->{Name} eq 'marc_subfield_table'; next if $table->{Name} eq 'auth_word'; next if $table->{Name} eq 'auth_subfield_table'; if ($table->{Engine} ne 'InnoDB') { print "moving $table->{Name} to InnoDB\n"; $dbh->do("ALTER TABLE $table->{Name} ENGINE = innodb"); } unless ($table->{Collation} =~ /^utf8/) { print "moving $table->{Name} to utf8\n"; $dbh->do("ALTER TABLE $table->{Name} CONVERT TO CHARACTER SET utf8"); $dbh->do("ALTER TABLE $table->{Name} DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci"); # FIXME : maybe a ALTER TABLE tbl_name CONVERT TO CHARACTER SET utf8 would be better, def char set seems to work fine. If any problem encountered, let's try with convert ! } else { } } If you have such problems in your database, the good option is to write a small script in misc/maintenance, that fixes the problem. It's not the responsibility of this patch, imo, to fix it. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/