Re: [DISCUSS] next up 3.1.3 or 3.2.0?

Le dim. 25 avr. 2021 à 14:31, Mark Struberg a écrit : > broken before, broken afterward. Sorry that is not a use case which > justifies tons of effort on our side. > Tons as stashing a line? ;) Im fine if we do the 3.1.3 and 3.2.0 at the same time, does not require more efforts if done this way

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

broken before, broken afterward. Sorry that is not a use case which justifies tons of effort on our side. LieGrue, strub > Am 25.04.2021 um 14:08 schrieb Romain Manni-Bucau : > > Le dim. 25 avr. 2021 à 13:47, Mark Struberg > a > écrit : > >> No, not a change.

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

Le dim. 25 avr. 2021 à 13:47, Mark Struberg a écrit : > No, not a change. > > If an Entity had a 'double' field it was mapped to NUMERIC. Which has no > fraction digits at all > > 7.23456789d would be stored as 3. > So we can rather safely assume that people worked around this by using > float, B

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

No, not a change. If an Entity had a 'double' field it was mapped to NUMERIC. Which has no fraction digits at all 7.23456789d would be stored as 3. So we can rather safely assume that people worked around this by using float, BigDecimal, etc. Thus no change for existing projects. LieGrue, str

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

AFAIK org.apache.openjpa.jdbc.meta.MappingInfo#mergeColumn will use getJDBCType and in case of HSQLDB it will move from NUMERIC to BIGINTEGER which is a breaking change for existing apps - detail in https://issues.apache.org/jira/browse/OPENJPA-2648. This kind of change is fine for 3.2 but not 3.1.

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

No, the DDL remains the same. We just switched to using java.time types in Oracle natively on the JDBC level. But the type names stood the same. LieGrue, strub > Am 24.04.2021 um 22:41 schrieb Romain Manni-Bucau : > > Le sam. 24 avr. 2021 à 22:08, Mark Struberg