Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Added a db dataset for our reference data:
data:
sources:
orders: { type: db, table: td_demo_shop_orders, envColumn: env }Works on local, fails on staging:
✖ DB_REQUIRED: Dataset table "td_demo_shop_orders" needs env.db in envs/staging.yaml.We already have a database configured — DATABASE_URL is set in CI and sdods db status is happy. So which database does the dataset want, and why is the environment file involved when the other one is not?
Accepted answer
They are two different databases and the naming does not help.
DB_DRIVER / DATABASE_URL / SQLITE_PATH configure the platform database — runs, scenarios, steps, heal events, proposals. It is where results go.
env.db configures the test-data database for that environment: the one holding your td_<slug>_<name> tables. It lives in the environment file because staging's fixture data is not local's fixture data, and it is legitimate for one environment to have one and another not to.
db:
driver: postgres
url: '${TEST_DATA_DATABASE_URL}'Then load the table for that environment:
sdods data import orders ./seed/orders.csv -p demo-shop -e staging --to table --truncate--truncate replaces the rows scoped to that environment rather than appending, which is what you want on a re-seed. The envColumn in your source spec is the column that scoping is written to, and it is stripped from the rows the steps see.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.