Agreed, the cascades are not blocking, but will be good to resolve promptly.


On Thu, Apr 10, 2014 at 10:27 AM, Joshua Shorenstein <
notifications@github.com> wrote:

> In qiita_db/qiita-db.sql:
>
> > +
> > +COMMENT ON TABLE qiita.analysis IS 'hHolds analysis information';
> > +
> > +COMMENT ON COLUMN qiita.analysis.analysis_id IS 'Unique identifier for analysis';
> > +
> > +COMMENT ON COLUMN qiita.analysis.email IS 'Email for user who owns the analysis';
> > +
> > +COMMENT ON COLUMN qiita.analysis.name IS 'Name of the analysis';
> > +
> > +COMMENT ON COLUMN qiita.analysis.pmid IS 'PMID of paper from the analysis';
> > +
> > +CREATE TABLE qiita.analysis_job (
> > +	analysis_id          bigint  NOT NULL,
> > +	job_id               bigint  NOT NULL,
> > +	CONSTRAINT idx_analysis_jobs PRIMARY KEY ( analysis_id, job_id ),
> > +	CONSTRAINT fk_analysis_job_analysis FOREIGN KEY ( analysis_id ) REFERENCES qiita.analysis( analysis_id ) ON DELETE CASCADE ON UPDATE CASCADE,
>
> Yes, although I don't remember setting this up. If we want cascades in
> here, we should probably talk about what needs what for that at a separate
> meeting. For now if we can get the schema in and update those later I think
> that's best.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/biocore/qiita/pull/32/files#r11493340>
> .
>