POST /study/{id}/attach

[PGijsbers]

Successful response looks like:

{"study_attach":{"id":"1","main_entity_type":"task","linked_entities":"102"}}%

[PGijsbers]

🪲 Users who do not own the study can attach (and detach) entities from it. This seems like an oversight (and otherwise I think it is a terrible decision).

[PGijsbers]

The restriction on not attaching to legacy studies already exists in the PHP implementation. In the Python implementation it is propagated by the fact that legacy studies can not be loaded at all.

[PGijsbers]

🐛 Attaching entities to a study that already exists in PHP just gave me the error

{"error":{"code":"1045","message":"Problem attaching entities. Please ensure to only attach entities that exist"}}%

which is incorrect. It seems that this is thrown on any failure while inserting the rows (in this case, it fails because of a duplicate primary key).

[PGijsbers]

#135 made it possible to attach tasks to suites. runs are not supported because they require a test database update.

[PGijsbers]

🪲 Users who do not own the study can attach (and detach) entities from it. This seems like an oversight (and otherwise I think it is a terrible decision).

Confirmed by Jan.

[michaellinhq]

Hi, I reviewed 'POST /study/{id}/attach' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.

[PGijsbers]

work in progress: enh/attach-run-to-study

• remove old references to the individual attach_run and attach_task
• add test for new function