The _id and _lastUpdated attributes are stored as first-class columns in the _logical_resources and _resources tables. Therefore, we should not store these attributes in the name-value pair pivoted _values tables, and search queries should be written to use the columns directly, which is more efficient (and logical).
Steps
- Investigate Schema Status
- Investigate Persistence Layer changes and Search changes
- Implement change to support and use _id and _lastUpdated uniquely
- Confirm common ids don't collide on the the Search (e.g. Practioner/1 doesn't collide with Patient/1)
Related to:
- Global Search Performance
Original Issue: _id and _lastUpdated should not be stored as pivoted name-value pair values #324
The _id and _lastUpdated attributes are stored as first-class columns in the _logical_resources and _resources tables. Therefore, we should not store these attributes in the name-value pair pivoted _values tables, and search queries should be written to use the columns directly, which is more efficient (and logical).
Steps
Related to:
Original Issue:
_id and _lastUpdated should not be stored as pivoted name-value pair values #324