[
https://issues.apache.org/jira/browse/OPENJPA-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745102#action_12745102
]
Michael Dick commented on OPENJPA-1233:
---------------------------------------
Hi Donald, unfortunately (or fortunately I guess) Geronimo isn't the only user
(embedder) of OpenJPA 1.2.x and some of the other user have not moved up to
Derby 1.4, or 1.5.
If these are new reserved words then they could cause existing apps to fail,
given the conservative nature of some of the users I'm not going to make this
change in 1.2.x. Users who move up to newer versions of Derby can manually
update their entities to avoid the new reserved names (not terribly friendly -
but at least they have relief).
> Update DerbyDictionary with new reserved words
> ----------------------------------------------
>
> Key: OPENJPA-1233
> URL: https://issues.apache.org/jira/browse/OPENJPA-1233
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jdbc
> Affects Versions: 1.0.3, 1.1.0, 1.2.1, 1.3.0, 2.0.0-M2
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 1.3.0, 2.0.0-M3
>
> Attachments: OPENJPA-1233.patch
>
>
> Derby 10.4.1.3 [DERBY-3460] added new reserved words:NONE and CURRENT_ROLE.
> Derby 10.5.2.0 [DERBY-4268] added new reserved word: SECURITY.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
