This question already has answers here:
Dialect needs to be explicitly supplied as of v4.0.0
(19 answers)
Closed 3 years ago.
I am using node, express and sequelize where when i run sequelize db:migrate am getting the following issue,
Sequelize CLI [Node: 13.2.0, CLI: 5.5.1, ORM: 5.21.2]
Loaded configuration file "server/config/config.json".
ERROR: Dialect needs to be explicitly supplied as of v4.0.0
Config file for db authentication is,
{
"dev": {
"username": "user_1",
"password": "pass",
"database": "todos_dev",
"host": "127.0.0.1",
"dialect": "postgres",
"operatorsAliases": false
},
"test": {
"username": "root",
"password": null,
"database": "database_test",
"host": "127.0.0.1",
"dialect": "postgres",
"operatorsAliases": false,
"dialectOptions": {
"bigNumberStrings": true
}
},
"production": {
"username": "root",
"password": null,
"database": "database_production",
"host": "127.0.0.1",
"dialect": "postgres",
"operatorsAliases": false
}
}
sequlize is not able to get NODE_ENV means it is not able to decide which authentication detail it should use, you need to define that using
export NODE_ENV=development
or when you do config for DB connection you can check it as -
const env = process.env.NODE_ENV || 'development';
This will solve the issue.
I develop a Nodejs app with sequelize used. I have been using 9.6 and just installed 10.6 and also copied the database to the new version (so right now I have 2 copies of it, one for each server/version).
However, my app still uses the old one. I am not sure how to change that. Is it via code or should I just stop somehow the old server running and start the new one? I use pgAdmin by the way.
This is my config.json that sequelize uses:
{
"development": {
"username": "postgres",
"password": "364200",
"database": "userbase",
"host": "127.0.0.1",
"port": 5433, // was 5432
"dialect": "postgres"
},
"test": {
"username": "postgres",
"password": "364200",
"database": "userbase",
"host": "127.0.0.1",
"port": 5433, // was 5432
"dialect": "postgres"
},
"production": {
"username": "postgres",
"password": "364200",
"database": "userbase",
"host": "127.0.0.1",
"port": 5433, // was 5432
"dialect": "postgres"
}
}
index.js (sequelize)
sequelize = new Sequelize('userbase', 'postgres', '364200', {
host: '127.0.0.1',
port: '5433' // <--- ADD THIS HERE
dialect: 'postgres',
});
EDIT: Fixed it with #Chiller's help in comments
I exported NODE_ENV=local and defined my mongo datasource as follows in datasources.local.json
"mongo": {
"host": "localhost",
"port": 27017,
"url": "mongodb://localhost:27017/mydb",
"database": "mydb",
"password": "",
"name": "mongo",
"user": "",
"connector": "mongodb"
},
But the database name is getting created as 'test'.I also tried in datasources.json but it's still the same. I need the database name to be 'mydb'. Please help
What fixed the problem for me was to set the name of the object to "db" and not "mongo" or "mongods".
"db": {
"host": "localhost",
"port": 27017,
"url": "mongodb://localhost:27017/mydb",
"database": "mydb",
"password": "",
"name": "mongo",
"user": "",
"connector": "mongodb"
},
I want to use a separate database for running tests. So I tried to configure TypeORM for multiple environments (dev and test) but it's not working. It only use the 'dev' configuration.
This is my npm scripts:
"scripts": {
"start": "NODE_ENV=dev node dist/index.js",
"test": "NODE_ENV=test mocha --reporter spec --compilers ts:ts-node/register 'test/**/*.test.ts'"
}
If I console.log(process.env.NODE_ENV) I get the correct results ("dev" / "test").
This is my ormconfig.json
[
{
"environment": "dev",
"name": "default",
"driver": {
"type": "mysql",
"host": "localhost",
"port": 3306,
"username": "root",
"password": "",
"database": "api"
},
"entities": [ "dist/model/*.js" ],
"autoSchemaSync": true
},
{
"environment": "test",
"name": "default",
"driver": {
"type": "mysql",
"host": "localhost",
"port": 3306,
"username": "root",
"password": "",
"database": "api_test"
},
"entities": [ "dist/model/*.js" ],
"autoSchemaSync": true
}
]
I connect with createConnection();. I manually created both databases api and api_test beforehand.
Why is TypeORM not using the "test" configuration when I set NODE_ENV=test?
You could change your ormconfig.json to a js file then do something similar to this:
require('dotenv/config');
const database = {
development: "dev-db",
production: 'prod-db',
test: 'test-db'
}
module.exports = {
type: 'postgres',
host: 'localhost',
port: 5432,
username: 'ur-username',
password: 'password',
database: database[process.env.NODE_ENV],
entities: ['dist/**/*.entity{.ts,.js}'],
synchronize: true,
migrationsTableName: 'migration',
migrations: ['migration/*.js'],
cli: {
migrationsDir: 'migration',
},
};
Then when running your tests, don't forget to set the appropriate environment. NODE_ENV=test should do.
I had a similar problem. I got this to work by using different 'name' fields for each connection. For my run-time connection, I kept name=default, and for my test connection I used name=test. So:
[
{
"environment": "dev",
"name": "default",
"driver": {
"type": "mysql",
"host": "localhost",
"port": 3306,
"username": "root",
"password": "",
"database": "api"
},
"entities": [ "dist/model/*.js" ],
"autoSchemaSync": true
},
{
"environment": "test",
"name": "test", //// CHANGED
"driver": {
"type": "mysql",
"host": "localhost",
"port": 3306,
"username": "root",
"password": "",
"database": "api_test"
},
"entities": [ "dist/model/*.js" ],
"autoSchemaSync": true
}
]
In my application, I would simply use createConnection(), which would automatically use the connection with name=default.
For my tests, I used typeorm's createConnections() (notice the s). This loads all connections. Once loaded, I would immediately after use getConnection('test'), which would get the test connection. My beforeAll in my tests looked like this in typescript:
beforeAll(async () => {
await createConnections();
getConnection('test');
});
In javascript, it would probably look something like:
beforeAll(() => {
createConnections().then(() => {
getConnection('test');
});
});
Then my tests started to pass. Hope that helps.
I had the same problem and I solved it by installing cross-env and the dotenv-flow package.
My typeorm script looked like this:
"typeorm": "cross-env NODE_ENV=development ts-node -r tsconfig-paths/register ./node_modules/typeorm/cli -d src/core/database/ormconfig.ts",
And I created an ormconfig.ts file, where I define the database connection variables through process.env, and all I had to do was add the "require" related to "dotenv-flow".
My ormconfig.ts
import { DataSource } from "typeorm";
require('dotenv-flow').config();
export const AppDataSource = new DataSource({
type: 'postgres',
host: process.env.DB_HOST,
port: parseInt(process.env.DB_PORT) || 5432,
username: process.env.DB_USER,
password: process.env.DB_PASS,
database: process.env.DB_NAME,
entities: [
],
migrations: [
],
migrationsRun: false,
migrationsTableName: 'history'
});
This option is no longer available.
You can see the pull request that removed it from the TypeORM docs, in Aug, 2017, here:
https://github.com/typeorm/typeorm.github.io/pull/13/files
The functionality itself seems to have been removed in a commit with other changes to fix another (unrelated?) issue. It is not immediately clear what the intent was in removing it.
Sequlize throws an error while applying migrations.
# sequelize --config config/config.js -m
Loaded configuration file "config/config.js".
Loaded configuration file "config/config.js".
Unable to connect to database: Error: Failed to authenticate for MySQL. Please double check your settings.
Config.js
"db": {
"development": {
"username": "imvgm_dev",
"password": "imvgm_dev",
"database": "imvgm_development",
"host": "localhost"
},
"production": {
"username": "imvgm_production",
"password": "imvgm_production",
"database": "imvgm_production",
"host": "localhost"
},
"testing": {
"username": "imvgm_testing",
"password": "imvgm_testing",
"database": "imvgm_testing",
"host": "localhost"
}
I can easily connect to db through
mysql --host=localhost --user=imvgm_dev --password=imvgm_dev imvgm_development
any thoughts?
I think you need to add "port" to your config.js.
And you need not specify config.js in the command line. This should work:
# sequelize -m