During the upgrade, the summary field in resource table is migrated into intro + introformat pair and the format of the field may be changed. because the field is defined as SMALLTEXT on MySQL servers, this field size may not be enough to accept the migrated value in the new format (it really happened to me).
I suggest to increase the type of the field to "big" which will create LONGTEXT in MySQL. We should not use smaller sizes anyway IMHO and XMLDB should be fixed so that it always creates big text fields only. Otherwise, conversion from one DB engine to another would be problematic, too, as PostgreSQL for example has single TEXT type.
If I read the upgrade code correctly, the patch is not that hard and the conversion of the field is pretty quick according to my experience.
- will be (partly) resolved by
-
MDL-31985 remove text and binary field size from XMLDB - always use big size
-
- Closed
-