Skip to content

Define setup tasks for systems #2

@c-lliope

Description

@c-lliope

For example, SLIM's README requires people to:

drop table if exists samples;
create table samples (
id text not null,
partNo text not null,
customer text not null,
item text not null,
status text not null,
received_by text not null,
received_at timestamp not null,
released_by text,
released_at timestamp,
primary key(id)
);

drop table if exists results;
create table results (
id serial primary key,
sample_id text not null,
test_name text not null,
result text not null,
entered_by text not null,
entered_at timestamp not null,
pass boolean not null
);

drop table if exists specification;
create table specification (
id serial primary key,
partno text not null,
test_name text not null,
test_method text not null,
criteria text not null,
judgement text not null,
created_by text not null,
created_at timestamp not null
);

This task needs to be run only once, when the slim postgres database is created.

We should make sure this task is handled nicely by the framework, and not put on the end user.

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