Skip to content

Switch LocationServices to 1:n from n:m #33

Description

@jcavena

Ohana requires 1:n relationship between Location and Services for simplicity and speed. We can use our services table to pull consistent names when adding into a 1:n location_services table.

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