Database Migration Meta Issue

[PGijsbers]

This is a collection of proposed database changes:

• GET /study/{id} #51: remove the benchmark_suite column from the study table as it is not used in production.
• GET /study/{id} #51: migrate legacy studies over to new-style studies.

[PGijsbers]

The flow (implementation) server logic treats (name, external_version) as a unique tuple, but this is not enforced at the database level.

[PGijsbers]

The flow (implementation) table has an uploadDate that does not have a default. I imagine that other tables also have this. I do not know why this is not default at the database level.

[rohansen856]

Hi @PGijsbers I would like to solve the issue with the following approach:

Removing benchmark_suite column from study table

• Drop the column from study table: ALTER TABLE study DROP COLUMN benchmark_suite;
• Update CreateStudy schema to remove the benchmark_suite field (src/schemas/study.py)
• Update database.studies.create() function to remove benchmark_suite parameter (src/database/studies.py)

Legacy studies are already properly handled, they return HTTP 410 (GONE) with the message "Legacy studies are no longer supported" as documented in the migration guide.

The changes maintain backward compatibility while removing the unused column. All syntax checks pass.

I would like to raise a PR solving the issue. Thanks!

[PGijsbers]

I had missed this comment, sorry about that. This issue is currently only for documentation purposes. We will not modify the database schema for now, and most likely will not until the PHP API is no longer in use.