[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] enlarging of text field fails?



CAUTION: This e-mail originated outside the University of Southampton.

Hi David,

While you are collecting MySQL issues, I have just run into one that I
think is a bug in MySQL:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.mysql.com%2Fbug.php%3Fid%3D79941&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C5a603d9c53d7445ba92708d974511686%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668713876298618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nxrQNiP0xjgsQgpgrS0z%2BP%2FaW7Kgvs3lUWaMwoZSB9o%3D&reserved=0

While adding a new field, I ran into the "Row size too large" error on
the `eprint__ordervalues_en` table rather than the main `eprint` table.
It seems that (under MySQL 5.7 and using DYNAMIC tables at least) there
is a limit of 196 LONGTEXT columns and similar despite this being way
under what you might calculate from dividing 8126B by 12B.

It turns we had a whole stack of fields lingering there that we had
taken out after the database was first initialised, so manually
dropping those columns has brought us back down under the limit.

Best wishes,
Alex.

On Wed, 2021-08-11 at 01:03 +0100, David R Newman via Eprints-tech
wrote:
> I am going to create a wiki page to explain about this issue and others
> that I have encountered that directly relate to issues with EPrints
> working with MySQL.

--
Alex Ball
Research Data Librarian (Systems)
University of Bath, Bath BA2 7AY, UK
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.bath.ac.uk%2Flibrary%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C5a603d9c53d7445ba92708d974511686%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668713876298618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=s11nSa1pjx4TeBYqoWnmPDFr5DqOaDz5CmTWVbSJNyo%3D&reserved=0