waltz
waltz copied to clipboard
Flow Classification Rules: allow multiple rules of differing directions
Description
Currently we have a unique index:
create unique index idx_fcr_scope_dt_app
on flow_classification_rule (parent_kind, parent_id, subject_entity_id, data_type_id)
go
However, this prevents two classifications which differ by direction.
Suggest we add direction to the flow_classification_rule
table and alter the flow_classification
table to make it's direction field a restriction on the usage of that classification (e.g. 'OUTBOUND'|'INBOUND'|'INBOUND_AND_OUTBOUND'
).
Note: we do not want the classification id in the classification_rule
uniqueness index as we explicitly don't want ambiguous situations where two classification rules have the same match characteristics.
Resourcing
We intend to contribute this feature