Uploaded image for project: 'OpenJPA'
  1. OpenJPA
  2. OPENJPA-2855

primary keys do no respect naming rules

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.2.0
    • 3.2.0
    • None
    • None

    Description

      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.

      Attachments

        Activity

          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

          jira-bot ASF subversion and git services added a comment - 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
          struberg Mark Struberg added a comment -

          shipped with OpenJPA-3.2.0

          struberg Mark Struberg added a comment - shipped with OpenJPA-3.2.0

          People

            struberg Mark Struberg
            struberg Mark Struberg
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: