Frontend implementation for Duration Mathesar type

[kgodey]

Requirements

Users should be able to:

• view data in columns that have the Duration Mathesar type
• change data type to and from the associated INTERVAL DB type
• view, set, and change data type options related to the Duration data types
• filter data by Duration-specific filtering options
• group data by Duration-specific grouping options
• use display options to view data in Duration type columns
  • Duration should be formatted according to the format in the display option

Update:

• Grouping will be handled in Frontend implementation for type specific grouping options #1073
• Filtering will be handled in Frontend implementation for type specific filtering options #1072

DB Type Mapping

There is only DB type - INTERVAL so no special mapping rules are necessary.

Implementation

Design

• The Global Data Types spec has the latest version of the UX.
• The Duration Data Type spec has an older version of the UX but more information on user scenarios.

Backend

• /api/v0/tables/ lists the name and DB type of each columns
• /api/v0/tables/<id/columns/ lists column information in more detail
• /api/v0/databases/<id>/types/ maps Mathesar types to DB types and provides a list of filtering and grouping options per-type.
  • These should be used to populate the filter and grouping options dynamically.
• Updates to column types and type options should happen via PATCH requests to /api/v0/tables/<id>/columns/<id>/. These updates include
  • Changes to the data type (type)
  • Changes to the display options (display_options)

Additional Context

• Design for duration data type #241 (design)
• Mapping DB data types to Mathesar data types #269 (concept of Mathesar types)
• Implement showing and changing a column's type #498 (conversation about data types)
• Blocked by backend work:
  • Handle INTERVAL type in the backend #430
  • Implement display options for Duration type #433

[kgodey]

Marking this as ready since filtering and grouping have been moved to other issues and remaining backend work is done.