You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part 1 Create a new materialised view
Currently we have a view for type=person, but there can be multiple "person" types now (eg: "chw", "supervisor", etc) and they are named arbitrarily so we can't create hardcoded views based on the contact_type.
Create a new materialised view that has a column for type which is coalesced the same way we do in CHT Core, eg: SELECT COALESCE (contact_type, type) AS contact_type.
Part 2 Deprecate broken view
This will mean the contactview_person_fields view is broken so we should:
Deprecate it.
Keep it around for backwards compatibility.
Recommend people migrate to the new view.
The text was updated successfully, but these errors were encountered:
Hi @mrsarm, This is a bit different from the work in that PR and still to be developed.
The current view (raw_contacts) doesn't consider records with type = "chw", "supervisor", etc.
See this comment.
This ticket consists of 2 parts:
Part 1 Create a new materialised view
Currently we have a view for type=person, but there can be multiple "person" types now (eg: "chw", "supervisor", etc) and they are named arbitrarily so we can't create hardcoded views based on the contact_type.
SELECT COALESCE (contact_type, type) AS contact_type
.Part 2 Deprecate broken view
This will mean the
contactview_person_fields
view is broken so we should:The text was updated successfully, but these errors were encountered: