Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 1.7.07
    • 1.7.08
    • Data
    • None
    • i2b2 Core
    • PostgreSQL
    • This was fixed for both PostgreSQL and SQL Server scripts. The oracle script already had the PROTECTION_LABEL_CD defined as the primary key.
    • Hide
      Verified via Bamboo that the following scripts ran without errors and the primary key was set correctly.

               crc_create_query_oracle.sql
               crc_create_query_postgresql.sql
               crc_create_query_sqlserver.sql


      Show
      Verified via Bamboo that the following scripts ran without errors and the primary key was set correctly.          crc_create_query_oracle.sql          crc_create_query_postgresql.sql          crc_create_query_sqlserver.sql

    Description

      The table qt_privilege in the crc schema doesn’t have primary key. However, in the document, it’s asserted that the ‘PROTECTION_LABEL_CD’ is the primary key. It’s a little error, but it could give some hard times (when the ant command is used too many time, duplicate appears, and error pops up in the webclient). Not a big issue, but worth being noted

      Attachments

        Activity

          PROTECTION_LABEL_CD is now the primary key for the QT_PRIVILEGE table.
          jmd86 Janice Donahoe added a comment - PROTECTION_LABEL_CD is now the primary key for the QT_PRIVILEGE table.
          This change was included in version 1.7.08, which was released on 10/07/2016.
          jmd86 Janice Donahoe added a comment - This change was included in version 1.7.08, which was released on 10/07/2016.

          People

            jmd86 Janice Donahoe
            dumestier dumestier
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: