[CORE-237] Cant build timeline when db is postgres Created: 09/Nov/16 Updated: 29/Jun/17 Resolved: 15/Jun/17 |
|
| Status: | Closed |
| Project: | i2b2 Core Software |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.09 |
| Type: | Bug | Priority: | Major |
| Reporter: | Lori Phillips | Assignee: | Janice Donahoe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Affects View/s: |
Timeline View
|
| i2b2 Sponsored Project/s: |
i2b2 Core
|
| Affects Database/s: |
PostgreSQL
|
| Developer Notes: | This was commited along with a much larger commit for OMOP processing ( |
| Participant/s: |
| Description |
|
The sql that is built when a db is postgres is invalid.
The reason for this is that the sql is built in two parts: The first part combines postgres with oracle workflow;' the second combines postgres with sqlserver flow. The result is a query that is half oracle; half sqlserver. The solution is to default postgres sql construction to the oracle flow. |
| Comments |
| Comment by Janice Donahoe [ 15/Jun/17 ] |
|
This issue has been fixed and will be included in release 1.7.09.
|