EPrints Technical Mailing List Archive
Message: #09316
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] upgrading from MySQL 5.7
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>, Yuri <yurj@alfa.it>
- Subject: Re: [EP-tech] upgrading from MySQL 5.7
- From: Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- Date: Tue, 23 May 2023 13:43:01 +0000
CAUTION: This e-mail originated outside the University of Southampton.
Thank you, Yuri, that is useful to know MariaDB 10.3 is working well.
Is anyone running EPrints with MySQL 8?
Tomasz
From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of Yuri via Eprints-tech <eprints-tech@ecs.soton.ac.uk>
Sent: Monday, May 22, 2023 2:56 AM To: eprints-tech@ecs.soton.ac.uk <eprints-tech@ecs.soton.ac.uk> Subject: Re: [EP-tech] upgrading from MySQL 5.7 Attention This email originates from outside the concordia.ca domain. // Ce courriel provient de l'extérieur du domaine de concordia.ca
CAUTION: This e-mail originated outside the University of Southampton.
Hi! we are using MariaDB 10.3 from the beginning (Debian default to MariaDB instead of MySQL) and we had no issues. The simpler method is to sql dump the database and reload it in the new installation. Il 19/05/23 22:38, Tomasz Neugebauer via Eprints-tech ha scritto:
|
- Follow-Ups:
- Re: [EP-tech] upgrading from MySQL 5.7
- From: Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- Re: [EP-tech] upgrading from MySQL 5.7
- References:
- [EP-tech] upgrading from MySQL 5.7
- From: Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- Re: [EP-tech] upgrading from MySQL 5.7
- From: Yuri <yurj@alfa.it>
- Re: [EP-tech] upgrading from MySQL 5.7
- From: Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- [EP-tech] upgrading from MySQL 5.7
- Prev by Date: Re: [EP-tech] upgrading from MySQL 5.7
- Next by Date: Re: [EP-tech] upgrading from MySQL 5.7
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):