Skip to content

The encoding/charset is hard coded to 'utf8' #74

@wywywywy

Description

@wywywywy

The encoding is hard coded to 'utf8', which can cause a ER_COLLATION_CHARSET_MISMATCH error.

As 'utf8' is not compatible with a number of collations, e.g. the utf8mb4 variants, some of the functions will not work.

What it should do, is to use the one in config.knex.connection.charset if specified, alternatively we can have a new entry config.dbManager.charset.

I am speaking in the context of MySQL because I'm not too familiar with Postgres, but I guess it's probably the same.

Example -

return self._masterQuery("CREATE DATABASE ?? DEFAULT CHARACTER SET utf8 DEFAULT COLLATE ?", [databaseName, locale]);

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions