[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[EP-tech] enlarging of text field fails?
Hi Alex,
I will add this as a possible resolution to this bug.? We are keen to
get rid of these associated tables for indexing / order values, as
modern versions of MySQL / MariaDB are much better a doing these tasks
than the halfway house solutions that were originally implemented for
EPrints probably over a decade ago. This will be quite an overhaul and
therefore is something for the next major release of EPrints (3.5), as
it will enforce a minimum version of MySQL / MariaDB.
Regards
David Newman
On 10/09/2021 12:49, Alex Ball via Eprints-tech wrote:
> 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%7Cd4e4bbd4be104902afcc08d97453eb24%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726036092912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=O%2FVarP%2F7L6lJO4FbEKiDxD8y3JrU4Ubte3hPzBnHC20%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%7Cd4e4bbd4be104902afcc08d97453eb24%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726036092912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XrkdkudPtXgsz0gWbSdOXRmDt%2BZazxvczQQN3ppX8Hs%3D&reserved=0
>
>
>
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd4e4bbd4be104902afcc08d97453eb24%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726036092912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BXoWiiYBdyVZd%2FA22jdQ%2FNU7AWm6Yk6MYH2WQZ3eGCw%3D&reserved=0
> *** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd4e4bbd4be104902afcc08d97453eb24%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726036092912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qtyJ6%2FkILLMcvxzdkS0A21MtK%2BrN8dZUObbCoMFxZ7g%3D&reserved=0
--
This email has been checked for viruses by AVG.
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avg.com%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cd4e4bbd4be104902afcc08d97453eb24%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726036092912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VI8RYXzR96jKzp1qbgZ6z%2FkjTnkuERhbYXconaDvOlw%3D&reserved=0