Resolve UI confusion with two separate "Decimal Places" type options

[seancolsen]

Current behavior

• The "Number" UI type has a display option for "Decimal Places" which controls minimum_fraction_digits and maximum_fraction_digits?
• Additionally, within the DB options, when "Number Type" = "Decimal", it will have a DB option for "Decimal Places" to control the Postgres SCALE value.
• The two "Decimal Places" fields do different things, but together they are confusing as presented.

Design questions to answer

• Do we want to allow the user to control the SCALE and PRECISION values?

  Things to consider:

  • The DB may have values set for those parameters outside of Mathesar.
  • There may be valid use cases for setting SCALE. For example, if I'm storing dollar values and I want to ensure that none of my values have fractional cents.

• If so, how do we design the UI to make a clear distinction between SCALE and minimum_fraction_digits/maximum_fraction_digits?

Related issues

• Allow user to configure separate minimum fraction digits from maximum fraction digits #1401

[kgodey]

Do we want to allow the user to control the SCALE and PRECISION values?

We do want to do this for this reason:

The DB may have values set for those parameters outside of Mathesar.

It is not a high priority now, but when we work on making Mathesar work well with existing Postgres databases, we'll need this.