https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32719
Emmi Takkinen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Emmi Takkinen <[email protected]> --- If I have understood correctly, while DELETE is performed, deleted rows are still kept in case of a rollback or crash (could be something else, here are some reasons and tips I found: https://mariadb.com/kb/en/big-deletes/). We faced similar problem while archiving our action_logs table. We ended up renaming action_logs as work_action_logs and creating a new action_logs based on it. Then after moving everything in archive table and back to action_logs work_action_logs is dropped. Could something similar work here? Rename sessions table e.g. drop_sessions -> create new sessions table -> drop renamed table -> alter new sessions table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
