Hi, currently for a Double property, it is mapped as double precision column in postgreSQL. For BigDecimal the expected decimal/numeric(p,s) column is used. It would be nice to be able to map a double to a decimal column, especially when you can define a @Digits validation rule for a double that expresses clearly the intent.
I would suggest for Double property in Studio to keep the BigDecimal front-end where you can define precision and scale. If these are defined for a Double then a @Digit validation rule is generated and we should be able to choose to use decimal/numeric column or double precision (which is faster). If not defined, no validation rule and column is a double precision by default.