1. What is the function of this table ?
2. Can I remove it?
Hi Ger,
absolutely yes! You can drop that table safely.
It's created by the built-in tests present in the XMLDB Editor, so its presence just means that you've executed them in the past.
In fact, you can find up to 3 tables:
* testtable
* anothertest
* newnameforthetable
It seems that we (my fault!) forgot to drop them at the end of the test. I'll fix that ASAP, until then, as said, it's 100% safe to drop them manually.
Ciao
Edited/PS: This issue has been tracked as MDL-20571.
absolutely yes! You can drop that table safely.
It's created by the built-in tests present in the XMLDB Editor, so its presence just means that you've executed them in the past.
In fact, you can find up to 3 tables:
* testtable
* anothertest
* newnameforthetable
It seems that we (my fault!) forgot to drop them at the end of the test. I'll fix that ASAP, until then, as said, it's 100% safe to drop them manually.
Ciao
Edited/PS: This issue has been tracked as MDL-20571.
This is for anyone who might be seeing a 'MySQL Server has gone away' error due to the presence of this table.
It seems that due to either the size of the table, or some characters contained in its 'avatar' column, we gate a 'MySQL Server has gone away' error when we export the database from one site and try to import into another site.
It seems that due to either the size of the table, or some characters contained in its 'avatar' column, we gate a 'MySQL Server has gone away' error when we export the database from one site and try to import into another site.
Hi,
As commented, you can, safely, drop those tables or, alternatively, run the XMLDB editor test again, because since some time ago, the test is dropping the tables properly.
Side note, for 2.0 we are disabling/deleting those XMLDB editor built in tests (see MDL-24116), as far was we have new ones (a few hundreds) running under lib/dml and lib/dml superseding and improving the old ones.
Ciao
As commented, you can, safely, drop those tables or, alternatively, run the XMLDB editor test again, because since some time ago, the test is dropping the tables properly.
Side note, for 2.0 we are disabling/deleting those XMLDB editor built in tests (see MDL-24116), as far was we have new ones (a few hundreds) running under lib/dml and lib/dml superseding and improving the old ones.
Ciao