mahara-contributors team mailing list archive

[Robert Lyon <1903799@xxxxxxxxxxxxxxxxxx>]

Hi Frank,

Yes I agree the best option would be to have the database itself on the
correct charset/collation then import the tables / data back in - making
sure the SQL dump file creates the tables in correct charset/collation
too.

Another option might be something like
https://stackoverflow.com/questions/5906585/how-to-change-the-character-
set-and-collation-throughout-a-database that you can try on a copy of
the database

Cheers
Robert

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1903799

Title:
  Upgrading to Mahara 20.10 getting error: Please ensure all columns use
  the same collation as the database

Status in Mahara:
  Invalid

Bug description:
  We are upgrading from 19.10 to 20.10 and get the following error when
  running admin/upgrade.php?urlsecret="xxxxxx"

  Mahara: Site Unavailable
  A column of your database is using a collation that is not the same as the database default. Please ensure all columns use the same collation as the database.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1903799/+subscriptions