Maybe it would be a good idea to name the table job_cache or something to
make it a little more clear what the function is (and that it shouldn't be
mis-used as authoritative).


On Mon, May 26, 2014 at 10:14 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,
>
> Yeah, it's essentially a cache and not used to make any scheduling
> decisions. Since flynn-host doesn't care about jobs that are not running,
> we need it to show the CLI and other UIs what is going on with the jobs
> that were requested.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/flynn/flynn-controller/pull/19/files#r13051680>
> .
>



-- 
Jeff Lindsay
http://progrium.com