Skip to content

Backend : Projects & Members Tables #5

@LinnierGames

Description

@LinnierGames

scroll down to the -> outline <- or resources

This one may be tricky. This schema requires three tables and a fourth table to be a table to connect two tables with each other. First, the Projects table must have title description and whatever is listed in the schema. Then, the AreaRequests table must reference this table, as in a one-to-many relation. A project can have MANY area requests but a single area request can only belong to one project. Then it's the attributes of an AreaRequest. Next, are the Members table and that one is easy. just follow the schema listed below. The last part is connecting members with multiple projects. Since a member can belong to more than one project and a project can have multiple members, another table is needed to connect a member with a project.

Issue's Outline

  • projects table
  • members table
  • projects_members table
  • Comply with the outline on this schema

Resources

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions