EPrints Technical Mailing List Archive
Message: #08729
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] enlarging of text field fails?
- To: eprints-tech@ecs.soton.ac.uk
- Subject: Re: [EP-tech] enlarging of text field fails?
- From: Yuri <yurj@alfa.it>
- Date: Fri, 10 Sep 2021 14:07:41 +0200
CAUTION: This e-mail originated outside the University of Southampton. Is there a plan to switch from a classic metadata model to an rdf based one? This would also help in using subjects using ontologies, and it would really simplify the information management. So instead of a table with eprintid | title | abstract | ... you have triples eprintid cdterms:title "a title" (you can represent it in sql as a title table with eprintid | title but this is a detail because there are already a lot of exinsting implementations) these are examples for dublin core: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dublincore.org%2Fspecifications%2Fdublin-core%2Fdcq-rdf-xml%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C48c19c54ff5a4877081308d97453979e%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726271092181%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=zZTXijHbzatI4aIDvR3p%2BKjREVIHtUqWLNNjyfDjMRk%3D&reserved=0 https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dublincore.org%2Fspecifications%2Fdublin-core%2Fdc-rdf%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C48c19c54ff5a4877081308d97453979e%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726271092181%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=a%2BAms4EuYmDzkbzVwvk6GtpIAIAUV1NYLlA5OPBkTpM%3D&reserved=0 Il 10/09/21 13:49, Alex Ball via Eprints-tech ha scritto:
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%7C48c19c54ff5a4877081308d97453979e%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726271092181%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=WAuY%2ByEKOrT5mhOtpgzh8FcSqUBjDOvWW4Z%2Fb1%2Fd9fg%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%7C48c19c54ff5a4877081308d97453979e%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726271092181%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=cE%2FnenbE9Pa28bub052VrKhpKmhJZay1o3xqpvIvgjI%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%7C48c19c54ff5a4877081308d97453979e%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726271092181%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=TpU%2BqNc%2F7p%2Fq4zPc8zryBavdF68tlBO64GqXPzTbTF8%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%7C48c19c54ff5a4877081308d97453979e%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637668726271092181%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=34KSSgeLcTVD2yp8yAp5uTNC2uRqce%2BlUvT0%2FguQkAE%3D&reserved=0
- Follow-Ups:
- Re: [EP-tech] enlarging of text field fails?
- From: Yuri <yurj@alfa.it>
- Re: [EP-tech] enlarging of text field fails?
- References:
- Re: [EP-tech] enlarging of text field fails?
- From: th.lauke@arcor.de
- Re: [EP-tech] enlarging of text field fails?
- From: David R Newman <drn@ecs.soton.ac.uk>
- Re: [EP-tech] enlarging of text field fails?
- From: Alex Ball <ab318@bath.ac.uk>
- Re: [EP-tech] enlarging of text field fails?
- From: Yuri <yurj@alfa.it>
- Re: [EP-tech] enlarging of text field fails?
- Prev by Date: Re: [EP-tech] enlarging of text field fails?
- Next by Date: Re: [EP-tech] enlarging of text field fails?
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):