The following sections indicate changes that are incompatible between OpenJPA 2.2.x releases and the 2.3.0 release.
In previous releases, the MappingTool mapped
java.math.BigDecimal fields to the database type
DOUBLE, and as such, ignored
precision values that might have been specified via the
From the 2.3.0 release,
java.math.BigDecimal fields are now mapped to the database type DECIMAL
and it is very likely that you will need to specify
In previous releases, the default value for the property RequiresSearchStringEscapeForLike is true and caused the unexpected escape clause appended to the SQL statement. For example, user created a named query like this:
SELECT o.computerName FROM CompUser o WHERE o.name LIKE ?
At run time the following query is generated:
SELECT t0.computerName FROM CompUser t0 WHERE (t0.name LIKE ? ESCAPE '\')
ESCAPE '\' shouldn't be appended to the query.
From the 2.3.0 release, RequiresSearchStringEscapeForLike property is set to false by default. You can configure RequiresSearchStringEscapeForLike property to be true if the old behavior is desired.