[
https://issues.apache.org/jira/browse/OPENJPA-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18142852#comment-18142852
]
ASF subversion and git services commented on OPENJPA-3075:
----------------------------------------------------------
Commit bf0b024b34e944e1c580449f5307ae5f95d8c806 in openjpa's branch
refs/heads/OPENJPA-3075 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=bf0b024b3 ]
[OPENJPA-3075] Make the default sequence names valid that Derby rejects
A sequence generator that names no sequence uses its generator name as the
database sequence name, which was never checked against the dictionary, so a
generator named Window, Order or User gave a CREATE SEQUENCE Derby rejects.
The metadata now records that the sequence name is the default one, and the
mapping configures the sequence with that name made valid by the dictionary,
under the same conditions as default table names: only a name that is one of
the words the database rejects, and not delimited, is changed, without making
it unique. Derby 10.16 rejects all of its invalid table words as unquoted
sequence names as well; other dictionaries have no such words, so their
sequence names do not change, and names given in sequenceName are kept.
> DerbyDictionary does not know WINDOW and other words Derby reserves
> --------------------------------------------------------------------
>
> Key: OPENJPA-3075
> URL: https://issues.apache.org/jira/browse/OPENJPA-3075
> Project: OpenJPA
> Issue Type: Bug
> Reporter: Richard Zowalla
> Priority: Major
> Fix For: 4.2.0
>
>
> DerbyDictionary's reserved words are missing words that Derby rejects as
> unquoted identifiers, such as WINDOW. An entity named Window therefore
> produces CREATE TABLE Window, which fails on Derby. Add the missing words,
> taken from Derby itself.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
