From 9f8c7500848916698b4b1e075652ea59e8f97871 Mon Sep 17 00:00:00 2001 From: sb5356 Date: Tue, 26 Jun 2018 12:55:57 -0400 Subject: Change RANGE_RULE table to support multiple ranges Change-Id: I376b9a5c13d9fb371693fc0ae725353ec468bb59 Issue-ID: CCSDK-316 Signed-off-by: Stan Bonev --- odlsli/src/main/resources/odlsli.dump | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/odlsli/src/main/resources/odlsli.dump b/odlsli/src/main/resources/odlsli.dump index f38494c0..03a3eb7b 100644 --- a/odlsli/src/main/resources/odlsli.dump +++ b/odlsli/src/main/resources/odlsli.dump @@ -723,8 +723,8 @@ CREATE TABLE `RANGE_RULE` ( `service_model` varchar(50) NOT NULL, `end_point_position` varchar(50) NOT NULL, `equipment_level` varchar(50) NOT NULL, - `min_value` int(11) NOT NULL, - `max_value` int(11) NOT NULL, + `equipment_expression` varchar(2000) NOT NULL, + `ranges` varchar(100) NOT NULL PRIMARY KEY (`range_rule_id`) ) ENGINE=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=latin1; /*!40101 SET character_set_client = @saved_cs_client */; -- cgit 1.2.3-korg