Numeric Field as Column with precision -> "pq: numeric field overflow"

[nabl13]

Is there an existing issue for this?

• I have searched the existing issues

Version of Corteza

2023.9.8

Current Behavior

I have a Numeric field with configured precision of 2.
When i configure this Field to be saved as a Column instead of JSON in PostgreSQL, the column will be created as follows:

CREATE TABLE "compose_record_modulename" (
	...
	"sekunden" NUMERIC(2,0) NULL DEFAULT NULL,
        ...

This is wrong, when i try to insert any number bigger then 2 digts (f.e. 100) it will raise an error: "pq: numeric field overflow"

According to the psql Doc: https://www.postgresql.org/docs/current/datatype-numeric.html

the first value defines the total length of the value and the second one the decimal places.

so NUMERIC(2,0) accepts 0-99
when i change it to NUMERIC() it just works with whatever is configured in Corteza.

Expected Behavior

Numeric fields should be defined correctly in postgreSQL if saved as column.
I think it would be just fine to leave the check logic to corteza and store the column as simple NUMERIC()

Steps To Reproduce

1. create module
2. create Numeric field with defined precision
3. change the storage of the field to "Column" instead of "JSON"
4. try to save any value bigger then the defined precision (precision:2 -> try save 100)

Environment and versions

Anything else?

No response