When CAVaT is left idle for a long period of time, MySQL times out its
connection, and we see something like:
cavat> corpus list
# Listing available databases for 'corpus use'
! Query failed.
! SQL was: SHOW DATABASES LIKE "timebank%"
! SQL error: (2006, 'MySQL server has gone away')
cavat>
Automatic re-connection, or at least a more user-friendly explanation of the
error, is required.
Original issue reported on code.google.com by leonderczynski on 3 Mar 2010 at 2:59
Original issue reported on code.google.com by
leonderczynski
on 3 Mar 2010 at 2:59