Non-Mathesar Data Types¶
Context¶
Non-Mathesar types are database types that don’t have any special functionality within Mathesar. This could be because that functionality is not implemented, yet it’s a standard Postgres type (Other), or because it’s a custom data type and not included in standard Postgres data types (Custom).
Limited Functionality¶
‘Non-Mathesar’ data type can be edited or added, but there are no particular data input or display features.
Prototype¶
Non-Mathesar Data Type Prototype
User Experience¶
Scenarios¶
User sets a column to ‘Non-Mathesar’ data type¶
Users cannot set ‘Non-Mathesar’ data types. Mathesar can only add these by connecting to an existing database.
User enters a new ‘Non-Mathesar’ data type value¶
Users can edit the existing values of a ‘Non-Mathesar’ data type column as they would with text string types.
User filters a ‘Non-Mathesar’ data type column¶
Users can filter the existing values of a ‘Non-Mathesar’ data type column as they would with text string types.
User groups a ‘Non-Mathesar’ data type column¶
Users can group the existing values of a ‘Non-Mathesar’ data type column as they would with text string types.
Review Notes¶
Adjust size of cells based on content length¶
As part of the implementation of data types, we need to consider how the table will display content such as a JSON document or other longer content formats.