I am running 3.6.0 on an Amazon RDS with mySQL 5.7. Amazon is requiring
me to move to mySQL 8.0 next week. I did a test migration a while back
and JAMES crashed and burned. So I backed out the change. I know I
should move up to the latest JAMES. But I'm out of runway and I haven't
even had time to research how much work it's going to be to migrate to
3.8. Before I head down that path, am I right in interpreting all of
the errors to mean that is understood that JAMES 3.6.0 simply cannot
work with mySQL 8.0? Or could there be something else that happened
with a simple fix such that I can keep my same install and upgrade mySQL
and keep going at least to take a little pressure off of fixing it or
all mail stops next week due to the Amazon change? Just looking at my
alternatives. I guess a 2nd question is... how painful/painless will it
be to migrate an existing 3.6 to 3.8?
Thanks.
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org