Details
Major Description
Add a new parameter in the crc.properties file that allows a site to use a temp table instead of a 'WITH' clause when running a CRC query. In some environments using a temp table allows the query to run more efficiently and process the request faster.
Parameter Name: edu.harvard.i2b2.crc.setfinderquery.constraintlogic
Located In: crc.properties file
Behavior:
Value = TEMP or TEMPTABLES temp tables will be used when building queries.
Value = "WITH" current query logic is used
If the parameter is missing from the crc.properties file the system will current query logic (WITH clause).
IMPORTANT: This change only affects SQL Server databases. Both PostgreSQL and Oracle do not have the capabilities of using temp tables. They will continue to use the WITH clause.
Parameter Name: edu.harvard.i2b2.crc.setfinderquery.constraintlogic
Located In: crc.properties file
Behavior:
Value = TEMP or TEMPTABLES temp tables will be used when building queries.
Value = "WITH" current query logic is used
If the parameter is missing from the crc.properties file the system will current query logic (WITH clause).
IMPORTANT: This change only affects SQL Server databases. Both PostgreSQL and Oracle do not have the capabilities of using temp tables. They will continue to use the WITH clause.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
Add a new parameter in the crc.properties file that allows a site to use a temp table instead of a 'WITH' clause when running a CRC query. In some environments using a temp table allows the query to run more efficiently and process the request faster.
Parameter Name: edu.harvard.i2b2.crc.setfinderquery.constraintlogic Located In: crc.properties file Behavior: Value = TEMP or TEMPTABLES temp tables will be used when building queries. Value = "WITH" current query logic is used If the parameter is missing from the crc.properties file the system will current query logic (WITH clause). IMPORTANT: This change only affects SQL Server databases. Both PostgreSQL and Oracle do not have the capabilities of using temp tables. They will continue to use the WITH clause. |
Add a new parameter in the crc.properties file that allows a site to use a temp table instead of a 'WITH' clause when running a CRC query. In some environments using a temp table allows the query to run more efficiently and process the request faster.
Parameter Name: edu.harvard.i2b2.crc.setfinderquery.constraintlogic Located In: crc.properties file Behavior: Value = TEMP or TEMPTABLES temp tables will be used when building queries. Value = "WITH" current query logic is used If the parameter is missing from the crc.properties file the system will current query logic (WITH clause). IMPORTANT: This change only affects SQL Server databases. Both PostgreSQL and Oracle do not have the capabilities of using temp tables. They will continue to use the WITH clause. |
| Summary | New parameter to use Temp Table Constraint instead of 'WITH' clause | New parameter to use temp table constraint instead of 'WITH' clause |
| Fix Version/s | 1.7.08 [ 10204 ] | |
| Assignee | Janice Donahoe [ jmd86 ] | |
| i2b2 Sponsored Project/s | i2b2 Core [ 10196 ] | |
| Status | New [ 10000 ] | Open [ 1 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Modifications made by Chris Herrick.
| Status | In Progress [ 3 ] | Ready to Test [ 10001 ] |
| Status | Ready to Test [ 10001 ] | Testing [ 10002 ] |
| Testing Notes | Verified the new parameter has been added to the crc.properties file and is working correctly | |
| Status | Testing [ 10002 ] | Testing [ 10002 ] |
| Resolution | Completed [ 10000 ] | |
| Status | Testing [ 10002 ] | Resolved [ 5 ] |
This change was included in version 1.7.08, which was released on 10/07/2016.
| Status | Resolved [ 5 ] | Closed [ 6 ] |