[CORE-208] qt_privilege primary key Created: 26/May/16  Updated: 17/Oct/16  Resolved: 22/Sep/16

Status: Closed
Project: i2b2 Core Software
Component/s: Data
Affects Version/s: 1.7.07
Fix Version/s: 1.7.08

Type: Bug Priority: Minor
Reporter: dumestier Assignee: Janice Donahoe
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Rank: 0|i002t3:
i2b2 Sponsored Project/s:
i2b2 Core
Affects Database/s:
PostgreSQL
Developer Notes: This was fixed for both PostgreSQL and SQL Server scripts. The oracle script already had the PROTECTION_LABEL_CD defined as the primary key.
Testing Notes: 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


Participant/s:

 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


 Comments   
Comment by Janice Donahoe [ 22/Sep/16 ]
PROTECTION_LABEL_CD is now the primary key for the QT_PRIVILEGE table.
Comment by Janice Donahoe [ 17/Oct/16 ]
This change was included in version 1.7.08, which was released on 10/07/2016.
Generated at Sun Apr 05 15:49:27 UTC 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.