Frontend implementation of Number Mathesar type

[kgodey]

Requirements

Users should be able to:

• view data in columns that have the Number Mathesar type
• change data type to and from the associated DB types based on options selected
  • NUMERIC
  • SMALLINT
  • INTEGER
  • BIGINT
  • DECIMAL
  • REAL
  • DOUBLE PRECISION
• view, set, and change data type options related to the Number data types
• filter data by Number-specific filtering options
• group data by Number-specific grouping options
• use display options to view data in Number type columns
  • Numbers should be formatted according to the locale in the display option
  • If the percentage option is enabled, numbers should be shown as a percentage.
• see Number data shown in a monospace font or using tabular figures (see design spec)

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

• New columns of UI type Number and converting existing columns to UI type Number will use NUMERIC
• Applying database options will change DB type in the following ways:
  • Setting "Number Type" to Integer will update the DB type to INTEGER and will set "Integer data size" to 32 bits
    • Updating "Integer data size" to 64 bits will change DB type to BIGINT
    • Updating "Integer data size" to 16 bits will change DB type to SMALLINT
  • Setting "Number Type" to Decimal will leave the DB type as-is (it could be NUMERIC or DECIMAL)
    • Setting decimal place and max digits will set the precision and scale type options.
  • Setting "Number Type" to Float will change the DB type to DOUBLE PRECISION and will set "Floating Point Type" to "15 digits precision"
    • Updating "Floating Point Type" to "6 digits precision" will change DB type to REAL
• Existing columns of the given types should automatically set the correct database options according to the logic above.
• DECIMAL columns should be treated the same as NUMERIC columns.

Implementation

Design

• The Global Data Types spec has the latest version of the UX.
• The Number 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 data type options (type_options)
  • Changes to the display options (display_options)

Additional Context

• Design for Number data types #238 (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 NUMERIC data type in the backend. #377
  • Handle SMALLINT data type in the backend. #378
  • Handle INTEGER data type in the backend. #379
  • Handle BIGINT data type in the backend. #380
  • Handle DECIMAL data type in the backend. #381
  • Handle REAL data type in the backend. #382
  • Handle DOUBLE PRECISION data type in the backend. #383
  • Implement display options for Number types. #386

[kgodey]

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

[seancolsen]

I'm closing this in favor of more specific tickets and outstanding PRs:

• Allow user to display numbers as percentages #1340
• After saving, the cell should display the saved value from Postgres instead of the user input #1337
• Fix bug with locale number formatting #1339
• Number scale not persisting #1300