You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/04/01 19:22:00 UTC

[jira] [Commented] (OPENJPA-2855) primary keys do no respect naming rules

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

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

Commit 2a3fc7386182ce7e4a6ace5b8f5a926766e53041 in openjpa's branch refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=2a3fc73 ]

OPENJPA-2855 revert PK name handling

Seems this got broken as side effect of dd9bce0cc909bd96d706a9438bdc2a58111c481f
which was for OPENJPA-2816. We need to check HerdDB again


> primary keys do no respect naming rules 
> ----------------------------------------
>
>                 Key: OPENJPA-2855
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2855
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 3.1.3
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Major
>             Fix For: 3.1.3
>
>
> Seems we broke primary key column naming when adding support for HerdDB.
> https://github.com/apache/openjpa/commit/dd9bce0cc909bd96d706a9438bdc2a58111c481f#r49002420
> Now all PK are delimited, which is not always what people want. Likely an unwanted side effect.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)