LIKE without an ESCAPE clause
A LIKE pattern with no ESCAPE clause now has no escape character on any database, as Jakarta Persistence requires: only % and \_ are special and a backslash in the pattern matches a backslash.
On H2, MySQL, MariaDB and PostgreSQL, whose LIKE defaults to a backslash escape, OpenJPA now emits an explicit ESCAPE clause to say so, and H2Dictionary sets RequiresSearchStringEscapeForLike to true for that reason.
The clause holds the new SearchStringNoEscape expression, by default the empty string literal '', a non-standard spelling of "no escape character" which H2 and PostgreSQL accept.
MySQL rejects that literal when sql_mode contains NO_BACKSLASH_ESCAPES and MariaDB ignores it altogether and keeps its backslash escape, so both use CHAR(0), an escape character which cannot occur in a pattern unless the pattern contains a NUL character.
A pattern which relied on the implicit backslash escape, such as foo\_bar meant to match a literal underscore, now matches a backslash followed by any character and must add an explicit ESCAPE '\' clause to the query.
On MySQL and MariaDB such a clause is rendered from SearchStringEscape as a doubled backslash, which those servers only accept while sql_mode contains no NO_BACKSLASH_ESCAPES; with that mode they fail the statement with ERROR 1210, so a query which has to run against it should name an escape character other than a backslash.
SearchStringEscape is now only the SQL literal rendering of a backslash escape character supplied by the query; it never gives a pattern character an escape meaning, so configuring it to another character no longer makes that character escape inside a pattern.
For dictionary subclasses: JDBCExpressionFactory no longer injects the dictionary escape character into the matches() expression, so the escape of a query without an ESCAPE clause stays null.