#635 Migrator has a charset problem

Reporter Oreolek
Owner Zash
Created
Updated
Stars ★★ (2)  
Tags
  • Status-Fixed
  • Type-Defect
  • Priority-High
  • Component-Migrator
  • Milestone-0.10
  1. Oreolek on

    prosody migrator has a problem with charsets when migrating between internal storage and SQL one. It's the same bug as this: https://groups.google.com/forum/#!topic/prosody-users/FLL9Nb060pQ but only in migrator, not prosody itself

  2. Oreolek on

    One can convert the erroneous charset like this in SQL (modify this to do UPDATE): select convert(binary convert(value using latin1) using utf8) from prosody

  3. MattJ on

    Changes
    • tags Milestone-0.10
    • owner MattJ
  4. Zash on

    Thanks for the report. The prosody issue you mention is #268. We will need to apply the same solution to the migrator.

    Changes
    • tags Status-Accepted
  5. Zash on

    Probably really should fix this before 0.10 is released :)

    Changes
    • tags Priority-High
  6. Zash on

    Changes
    • owner MattJ Zash
  7. Zash on

    Changes
    • tags Status-Started
  8. Zash on

    Ported util.sql in https://hg.prosody.im/0.10/rev/605fa6bfafd1 Added charset check in https://hg.prosody.im/0.10/rev/ffb36d1ae23b If the check does not pass, it will demand the database be updated via prosodyctl. Needs testing.

    Changes
    • tags Status-Fixed
  9. Zash on

    Tested briefly with SQLite3.

  10. Zash on

    Changes
    • tags Component-Migrator

New comment