[CORE-104] Schema name in db_lookup tables for PostgreSQL incorrectly defined as public Created: 14/May/14  Updated: 08/Feb/17  Resolved: 30/Jan/17

Status: Closed
Project: i2b2 Core Software
Component/s: Data
Affects Version/s: 1.7.00, 1.7.01
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Janice Donahoe Assignee: Mike Mendis
Resolution: Working As Designed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: PostgreSQL

Rank: 0|i000in:
Developer Notes: The PostgreSQL insert_data scripts for the db_lookup tables were updated to reflect the correct schema name in the c_db_fullschema column.
Testing Notes: The running of the data scripts is tested as part of the bamboo install tests.

Bamboo Postgres build #278

Build failed. Reverting changes. Will be fixed in 1.7.03
Participant/s:

 Description   
The PostgreSQL insert_data scripts for the db_lookup tables have the wrong schema name defined in the c_db_fullschema column. Currently these scripts have "public" defined as the schema. The following scripts need to be updated to reflect the correct schema for each of the db_lookup tables.


crc_db_lookup_postgresql_insert_data.sql / c_db_fullschema = i2b2demodata

im_db_lookup_postgresql_insert_data.sql / c_db_fullschema = i2b2imdata

ont_db_lookup_postgresql_insert_data.sql / c_db_fullschema = i2b2metadata

work_db_lookup_postgresql_insert_data.sql / c_db_fullschema = i2b2workdata




 Comments   
Comment by Janice Donahoe [ 09/Jun/14 ]
Issues found in Bamboo testing. Will be addressed in future release
Generated at Thu Apr 25 13:30:38 UTC 2024 using Jira 8.20.11#820011-sha1:0629dd8d260e3954ece49053e565d01dabe11609.