[
https://issues.apache.org/jira/browse/OPENJPA-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Solodovnik resolved OPENJPA-3060.
---------------------------------------
Resolution: Fixed
> MariaDB: StoreCharsAsNumbers still defaults to true
> ---------------------------------------------------
>
> Key: OPENJPA-3060
> URL: https://issues.apache.org/jira/browse/OPENJPA-3060
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Reporter: Richard Zowalla
> Assignee: Richard Zowalla
> Priority: Major
> Fix For: 4.2.0
>
>
> OPENJPA-3001 turned {{StoreCharsAsNumbers}} off by default for MySQL, so
> {{char}}/{{Character}} attributes are stored in {{CHAR(1)}} columns.
> {{MariaDBDictionary}} does not extend {{MySQLDictionary}} and did not get the
> change, so on MariaDB these attributes are still stored as {{INTEGER}} code
> points and a pre-existing {{CHAR(1)}} column (as in the Jakarta Persistence
> TCK schema) does not work.
> The 4.2 migration note "char attributes are stored as CHAR(1)" lists MySQL
> but not MariaDB.
> Also two tests check for {{MySQLDictionary}} only and skip MariaDB:
> {{AbstractLobTest}} and the fractional timestamp branch of
> {{TestJDBCEscapeDate}}.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
