You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for this great framework! It works quite well together with TypeORM.
One thing that I couldn't find a solution myself is a way to set the connection charset for MySQL. With Typeorm, I can do the following
// read connection options from ormconfig file (or ENV variables)
const connectionOptions = await getConnectionOptions();
// create a connection using modified connection options
const connection = await createConnection({
...connectionOptions,
charset: 'UTF8MB4_GENERAL_CI',
} as MysqlConnectionOptions);
It's not been loaded from option reader so this seems the only option.
I'm thinking we can either allow passing a connection to Vesper or Vesper reuse the existing default connection automatically (instead of die with AlreadyHasActiveConnectionError).
The text was updated successfully, but these errors were encountered:
I have also tried query set names utf8mb4 after bootstrap. Even if SHOW VARIABLES indicates character_set_client is using utf8mb4 already, Typeorm isn't getting emojis correctly.
Hi Vesper team,
First of all, thanks for this great framework! It works quite well together with TypeORM.
One thing that I couldn't find a solution myself is a way to set the connection
charset
for MySQL. With Typeorm, I can do the followingIt's not been loaded from option reader so this seems the only option.
I'm thinking we can either allow passing a
connection
to Vesper or Vesper reuse the existingdefault
connection automatically (instead of die withAlreadyHasActiveConnectionError
).The text was updated successfully, but these errors were encountered: