| Summary: | Add CI job Koha_Main_MariaDB_update but with lowest MariaDB version (10.3) | ||
|---|---|---|---|
| Product: | Project Infrastructure | Reporter: | Victor Grousset/tuxayo <victor> |
| Component: | Continuous Integration | Assignee: | Tomás Cohen Arazi (tcohen) <tomascohen> |
| Status: | NEW --- | QA Contact: | |
| Severity: | critical | ||
| Priority: | P5 - low | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40292 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40297 |
||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Victor Grousset/tuxayo
2025-07-02 16:33:39 UTC
Is there a large enough risk for needing also mariadb latest ? I though I had found a case but it was about something in kohastructure.sql (offset became a reserved keyword and before 21.05 we had an unquoted declaration of a column named offset) but kohastructure.sql is always ran so it's not a relevant example. Could there be a risk with the db revs on recent MariaDB versions warranting a CI job? |