Separately identify restrictions by rst_type 39/170639/1
authorNishant Chaprana <n.chaprana@samsung.com>
Wed, 21 Feb 2018 06:25:51 +0000 (11:55 +0530)
committerNishant Chaprana <n.chaprana@samsung.com>
Wed, 21 Feb 2018 06:25:51 +0000 (11:55 +0530)
commit3c752514e81dd233f64ecaf84137b94fc7231c98
treec35453eaccc3b0366614545548cbcad010e1e29c
parentf93b4376f74f2ea907594d826ccf9b5942753d15
Separately identify restrictions by rst_type

Description: This patch adds logic to separately identify restriction
on basis of restriction type (Blocked/Excluded).
Also it stores rst_type inplace of rst_state in restriction table because
rst_state is only to check whether restriction is active or not and
we are not required to store that information to database.

Change-Id: I5f540c5b791634072d58c87e7eceda8e6f653e76
Signed-off-by: Nishant Chaprana <n.chaprana@samsung.com>
data/traffic_db.sql
include/stc-manager.h
packaging/stc-manager.spec
src/database/include/table-restrictions.h
src/database/tables/table-restrictions.c
src/monitor/include/stc-monitor.h
src/monitor/stc-monitor.c
src/stc-restriction.c