Originally reported by: gkunter (Bitbucket: gkunter, GitHub: gkunter)
Sometimes, MySQL database connections don't get closed correctly (probably if exceptions occur during corpus installations or queries, but that's not clear as yet). If the corpus using that database is requested to be removed by the corpus manager, the GUI freezes, because the MySQL connection that tries to drop the database is waiting for table metadata lock.
Care should be taken that there are no open connections
MySQL connections should time-out
If the connection that tries to drop the database doesn't succeed after a specific amout of time, an exception should be raised.
Originally reported by: gkunter (Bitbucket: gkunter, GitHub: gkunter)
Sometimes, MySQL database connections don't get closed correctly (probably if exceptions occur during corpus installations or queries, but that's not clear as yet). If the corpus using that database is requested to be removed by the corpus manager, the GUI freezes, because the MySQL connection that tries to drop the database is
waiting for table metadata lock
.