Skip to content

Refactor task_type from 1-1 to 1-many #49

Description

@ethanholz

Is your feature request related to a problem? Please describe.
In #46 we added a column for a task type but I find this too restrictive. The column does not allow for a task to be tagged with multiple potential types. For example, if a task could be run on CPU or GPU this is currently not possible.

Describe the solution you'd like
I propose that this should be its own table similar to the dependencies table such that we can match on multiple types in SQL.

Describe alternatives you've considered
The biggest alternative (and abuse) is using a comma-seperated list inside of the task type column. This should not be done and is problematic.

Additional context
n/a

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions