-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
recover previous workaround for problem with MySQL char(n) type
This is needed to remain compatible with schemas we produced in the past, even though we're nor preferring varchar(1) for storing Java char. Signed-off-by: Gavin King <[email protected]>
- Loading branch information
Showing
3 changed files
with
39 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@gavinking In my opinion
stripsTrailingSpacesFromChar -> true
should also be implemented byMySQLLegacyDialect
as we are observing the newCoercionException( "value does not contain a character: '" + string + "'" );
when using Hibernate 7 Beta3, MySQLLegacyDialect, MySQL 5.Let me know if you need an issue or any additional input regarding this.