Uploaded image for project: 'EJBCA'
  1. EJBCA
  2. ECA-7772

Avoid foreign key constraints creation for obsolete AccessRulesData and AdminEntityData

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: EJBCA 7.0.0
    • Fix Version/s: EJBCA 7.0.1
    • Component/s: None
    • Labels:
    • Issue discovered during:
      Review
    • Sprint:
      EJBCA Team Bob - 2019 w6

      Description

      Foreign key constraints should not be created for AccessRulesData and AdminEntityData (from AdminGroupData). These tables are no longer used (except for reading data to upgrade), so they will be empty. Hence it does not make sense to create foregin key contraints on them. Note that you get the error even with empty tables

      Figure out why Hibernate is creating foreign key constraints on these tables and disable this, without breaking backwards compatibility and preferably in a standard JPA way.

      The motivation for fixing this is that Hibernate is showing a lot of "alter table X add constraint Y" error messages when running an import with the DB CLI.

      Note: Currently the error message is disabled in the log4j-cli.xml file. See ECA-7773

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                johan Johan Eklund
                Reporter:
                samuel Samuel Lidén Borell
                Verified by:
                Tomas Gustavsson
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: