Postgres Decimal division returns double precision

[GregoryTravis]

Decimal/Decimal returns double precision because the / operator always casts to double precision. This cast is presumably there so that integer division will be done as floating point division.

Instead of always casting to double precision, we should only do this if both arguments are integer types.

[enso-bot]

Greg Travis reports a new STANDUP for yesterday (2024-07-02):

Progress: in-memory and database backend arithmetic return types It should be finished by 2024-07-05.

Next Day: test failures

[enso-bot]

Greg Travis reports a new STANDUP for today (2024-07-03):

Progress: discussing plan for arithmetic value/type consistency across backends; decimal division return types It should be finished by 2024-07-05.

Next Day: test failures

[enso-bot]

Greg Travis reports a new 🔴 DELAY for today (2024-07-05):

Summary: There is 3 days delay in implementation of the Postgres Decimal division returns double precision (#10418) task.
It will cause 0 days delay for the delivery of this weekly plan.

Delay Cause: backend differences

[enso-bot]

Greg Travis reports a new STANDUP for today (2024-07-05):

Progress: separating decimal tests into common and backend-specific, because of different handling of repeating decimals It should be finished by 2024-07-08.

Next Day: test failures