Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Fix switching to 3.0 from 2.5 #18

Draft
wants to merge 3 commits into
base: develop
Choose a base branch
from
Draft

Conversation

adriendupuis
Copy link
Owner

Add version switcher from 2.5 into 3.0
@adriendupuis adriendupuis changed the base branch from master to release/v3.0.0 April 14, 2020 13:07
adriendupuis referenced this pull request Apr 15, 2020
Should help to fix bugs after switching eZ between v2.5 and v3.0

For example, v3 → v2 needs, at least, `rm -rf config/ public/ .env;`
@adriendupuis adriendupuis changed the base branch from release/v3.0.0 to release/v3.0 April 15, 2020 13:09
Resync version switching fix w/ 3.0.1
@adriendupuis adriendupuis changed the title Fix switching from 2.5 to 3.0 [WIP] Fix switching from 2.5 to 3.0 Apr 15, 2020
@adriendupuis adriendupuis changed the title [WIP] Fix switching from 2.5 to 3.0 [WIP] Fix switching to 3.0 from 2.5 Apr 15, 2020
@adriendupuis
Copy link
Owner Author

When container mariadb already exists when passing from 2.5 to 3.0, the log is full of
[Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade

  • Removing the container before up --build, of course, works.
  • Keeping the container and running docker-compose exec mariadb mysql_upgrade -proot; when is up also works.

@adriendupuis adriendupuis changed the base branch from release/v3.0 to develop May 12, 2020 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant