Design for working with schemas

[kgodey]

Problem

Users may want to create a new schema, edit the name of a schema and delete a schema. We should allow this through the UI

Proposed solution

We need a design for how users can accomplish this, including error states if a schema is unable to be edited or deleted, or if a user might need to perform additional actions before a schema is deleted (such as removing references to it from other places).

During this design process, we should be guiding users towards using schemas in a way that's consistent with good database practices. Schemas should be thought of as similar to Airtable's "Base" concept or Dabble DB's "Application" concept – they contain a group of related tables. We should incentivize users to think of schemas in the same way.

Additional context

• We'll know more about what error states a user might encounter after Function to handle renaming schemas #165 and Function to handle deleting schemas #167 are implemented.
• Some reading that could be helpful during the design process:
  • PostgreSQL Schemas — Usage Scenario/Case (Stack Overflow)
  • PostgreSQL Schema Management Basics

[ghislaineguerin]

Finalized spec can be found here: https://wiki.mathesar.org/en/design/specs/schemas