[ 
https://issues.apache.org/jira/browse/OPENJPA-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18142448#comment-18142448
 ] 

ASF subversion and git services commented on OPENJPA-3074:
----------------------------------------------------------

Commit 3eef052ba8b29b6099309e91e2d5077c3ebd5fd0 in openjpa's branch 
refs/heads/OPENJPA-3074 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=3eef052ba ]

[OPENJPA-3074] Describe the reserved words and the delimiting on MySQL and 
MariaDB in the migration considerations, the release notes and the 
compatibility option

The section on the names that MySQL 8.0 and later reserve now covers MariaDB:
the words taken from the servers, the delimiting that MariaDB gets, what
changes for a schema an earlier release created, including the case of a
delimited table name, what UpdatedMySQLAndMariaDBReservedWords=false restores
on each database, and that the delimiting rule is shared by all persistence
units of the JVM.


> Share the common code of MySQLDictionary and MariaDBDictionary in a 
> superclass and add the MySQL 8 reserved words
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-3074
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-3074
>             Project: OpenJPA
>          Issue Type: Improvement
>            Reporter: Richard Zowalla
>            Assignee: Richard Zowalla
>            Priority: Major
>             Fix For: 4.2.0
>
>
> MySQLDictionary and MariaDBDictionary both extend DBDictionary and duplicate 
> most of their code, as noted in the review of #297 (OPENJPA-2943). Move the 
> shared code into a common abstract superclass and keep the per-database 
> differences and defaults in the two subclasses. All public configuration 
> fields stay as they are.
> MySQLDictionary also lacks the reserved words MySQL 8.0 added, such as RANK, 
> ROW_NUMBER, WINDOW and LATERAL. An entity attribute named rank therefore 
> produces a CREATE TABLE statement that fails on MySQL 8.4 and 9.x.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to