This seems to go against our keep-edge-state-at-the-edge pattern. Is the
jobs table a non-authoritative cache of actual state? Just looking for
context.


On Mon, May 26, 2014 at 9:56 AM, Jonathan Rudenberg <
notifications@github.com> wrote:

> In schema.go:
>
> > @@ -133,6 +133,16 @@ $$ LANGUAGE plpgsql`,
> >      PRIMARY KEY (app_id, resource_id)
> >  )`,
> >  		`CREATE INDEX ON app_resources (resource_id)`,
> > +
> > +		`CREATE TABLE jobs (
> > +    job_id uuid PRIMARY KEY DEFAULT uuid_generate_v4(),
> > +    app_id uuid NOT NULL REFERENCES apps (app_id),
> > +    release_id uuid NOT NULL REFERENCES releases (release_id),
> > +    state text NOT NULL,
>
> Make this an enum:
>
> CREATE TYPE job_state AS ENUM ('starting', 'up', 'down', 'crashed');
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/flynn/flynn-controller/pull/19/files#r13051276>
> .
>



-- 
Jeff Lindsay
http://progrium.com