Compatibility between atom (2.6.0) and MariaDB

[Seb Muller]

Hello,

I would like to know if an update of last atom version (2.6.0) is scheduled in the future to have a compatibility with MariaDB ?

Thanks for information

[Dan Gillean]

Hi Seb, 

That is going to depend on the MariaDB community, not on work to be done in AtoM. 

In the 2.6 release, we moved to MySQL 8.0 because it brings with it new features (such as support for Common Table Expressions) that have allowed us to significantly optimize slow-running operations - particularly those that previously relied on a Nested set model to deal with hierarchical relations.

MariaDB is a community-maintained fork of MySQL, and so far they have not released a version that is fully compatible with MySQL8. See for example: 

• https://mariadb.com/kb/en/incompatibilities-and-feature-differences-between-mariadb-105-and-mysql-80/
  
• https://mariadb.com/kb/en/function-differences-between-mariadb-105-and-mysql-80/
  

I do believe that the latest version of MariaDB supports CTE, but there are other features, such as the authentication plugins and the collation formats, that differ enough to prevent full compatibility with AtoM at present.   

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

he / him

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/6d1bd5f8-d5e1-486a-9fa1-be5232206fe3n%40googlegroups.com.

[Seb Muller]

Hello Dan, thank you very much for your response and this informations.

Cordially

Seb Muller

[Grant Forrest]

Can I add that at this time, AtoM 2.6 is incompatible with MariaDB. The collation  utf8mb4_0900_ai_ci is missing from MariaDB 10.x and no mention of it being added in forthcoming releases. 

[sunny...@gmail.com]

Hi all, 

We recently tested AtoM 2.6.1 installation with MariaDB and successfully deployed it to our production environment(https://discoverarchives.library.utoronto.ca/).

I'd like to share the steps our talented network services administrator, Chris Crebolder suggested. 

1. Update MariaDB to 10.5 (Our version is 10.5.8).

2. Patch the mysql8 default charset with something more universal in AtoM 2.6.1. (See the attached patch)

• In line 391 of this code:
  https://github.com/artefactual/atom/blob/v2.6.1/lib/task/migrate/migrations/arMigration0178.class.php#L391
• Change this:
  'CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci'
• To this:
  'CHARACTER SET utf8 COLLATE utf8_unicode_ci'

3. Run the upgrade task following the AtoM's instructions

    https://www.accesstomemory.org/en/docs/2.6/admin-manual/installation/upgrading/#run-the-upgrade-task

    php -d memory_limit=-1 symfony tools:upgrade-sql

4. Run other necessary tasks 

• Rebuild search index and clear cache (https://www.accesstomemory.org/en/docs/2.6/admin-manual/installation/upgrading/#rebuild-search-index-and-clear-cache)
• Restart services (https://www.accesstomemory.org/en/docs/2.6/admin-manual/installation/upgrading/#restart-services)

We haven't identified any critical issues with this installation so far but we will share if anything comes up.

Hope this will be helpful.

Take care,

Sunny Lee

Digital Initiatives Application Programmer Analyst | University of Toronto Libraries | Information Technology Services

She/her

[Dan Gillean]

Hi Sunny, 

Thanks so much for sharing this! Please keep us updated over time if you do run into issues that you think result from this change. 

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

he / him

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/dc9f457c-783e-4219-a8fe-9192e1f949dcn%40googlegroups.com.