Seeders state in database with using url option

Open
#1,455 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, postgres
Domain
cli, database

Research direction

Start by reproducing the db:seed:all command with --url and compare it with the supplied config/options.json, especially the seederStorage setting. Trace how the CLI handles --url and seeder storage; done means clarifying or correcting whether seeder state is persisted without a configuration file.

Written by the indexing model from the issue text.

Description

Hi. Could you help me. Why sequalize doesn't save seeders state into database?

I'm using next command

sequelize-cli --env=test db:seed:all --config=config/options.json --url=postgres://$POSTGRES_USER:$POSTGRES_PASSWORD@$DB_HOST:$DB_PORT/$POSTGRES_DB

file config/options.json

{
  "test": {
    "seederStorage": "sequelize"
  }
}

This command works at first run only

How can I save seedres state into database without using any config files?

Dominant language
JavaScript
Stars
2.6k
Forks
524
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sequelize/cli

All issues in sequelize/cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.