Clean up whitespace issues, only (FINERACT-1188)

2020-10-10 11:33:09 +02:00
parent d98b23a86d
commit 504eeed431
28 changed files with 178 additions and 180 deletions
@@ -6,4 +6,4 @@ This demo database contains:
 - DDL of latest schema
 - Minimum reference data required for deployment of platform
 - Customisatons for CEDA on m_code/m_code_value tables, extra datatables for client and loan data capture
- Extra reports over and beyond core reports customisation for CEDA operations
+- Extra reports over and beyond core reports customisation for CEDA operations
@@ -264,7 +264,7 @@ from x_registered_table r;

 -- ==== Chart of Accounts =====
 truncate `acc_gl_account`;
-INSERT INTO `acc_gl_account` VALUES 
+INSERT INTO `acc_gl_account` VALUES
 (1,'Petty Cash Balances',NULL,'11100',0,1,2,1,NULL),
 (2,'Cash in Valut 1',NULL,'11101',0,1,1,1,NULL),
 (3,'Bank Balances',NULL,'11200',0,1,2,1,NULL),
@@ -360,4 +360,4 @@ INSERT INTO `acc_gl_account` VALUES
 (94,'Modem',NULL,'42902',0,1,1,5,NULL),
 (95,'Meals',NULL,'42903',0,1,1,5,NULL),
 (96,'Transportation',NULL,'42904',0,1,1,5,NULL),
-(97,'Miscellaneous',NULL,'42905',0,1,1,5,NULL);
+(97,'Miscellaneous',NULL,'42905',0,1,1,5,NULL);
@@ -46,7 +46,7 @@ INSERT INTO `m_appuser`
 `nonexpired_credentials`,
 `enabled`)
 VALUES
-(0, 1, 'keithwoodlock', 'Keith', 'Woodlock', 
+(0, 1, 'keithwoodlock', 'Keith', 'Woodlock',
 '4f607e9b6cffbe7d3db92d4bfa3391c7aa751727b4ea29d08fddf9dd72e6e7e3', 'keithwoodlock@gmail.com', 0, 1, 1, 1, 1);

 INSERT INTO `m_appuser_role`
@@ -61,7 +61,7 @@ INSERT INTO `m_office`
 `external_id`,
 `name`,
 `opening_date`)
-VALUES 
+VALUES
 (1, '.2.', 2, 'Uganda (Kampala)', '2009-01-01');


@@ -114,10 +114,10 @@ INSERT INTO `m_product_loan`
 `accounting_type`,
 `loan_transaction_strategy_id`)
 VALUES
-('UGX', 2, 1000000.000000, 0, 1000000000000.000000, null , 'Kampala Product (with cash accounting)', 
-'Typical Kampala loan product with cash accounting enabled for testing.', null , 
+('UGX', 2, 1000000.000000, 0, 1000000000000.000000, null , 'Kampala Product (with cash accounting)',
+'Typical Kampala loan product with cash accounting enabled for testing.', null ,
 24.000000, 3, 24.000000, 1, 1, 1, 2, 12, 1, 2, 2);

 -- mapping of that loan product to GL Accounts
-INSERT INTO `acc_product_mapping` 
-VALUES (1,4,1,1,1),(2,8,1,1,2),(3,34,1,1,3),(4,37,1,1,4),(5,35,1,1,5),(6,97,1,1,6);
+INSERT INTO `acc_product_mapping`
+VALUES (1,4,1,1,1),(2,8,1,1,2),(3,34,1,1,3),(4,37,1,1,4),(5,35,1,1,5),(6,97,1,1,6);
@@ -12,4 +12,4 @@ This demo database contains:
  -  Its mandatory to have at least one role when creating new users so we have one role created by default called 'Super user' which has the special permission 'Full Authorisation'. Any user with this role can do anything in the system.
  -  Its required to have at least one application user setup so remaining setup can be done through ui so we have on application user created by default with username 'quipo' with a password of 'quipo'. Application users must be associated with an office and a role so this user is associated with 'Latam HO' and 'Super user' role allowing this user to do any operation in any office(branch).

-Minimum amount of data to support api-docs interaction.
+Minimum amount of data to support api-docs interaction.
@@ -44,8 +44,8 @@ join m_code_value mv on mv.code_id = mc.id
 where mc.`code_name` = "YesNo";

 INSERT INTO `m_code`
-(`code_name`, `is_system_defined`) 
-VALUES 
+(`code_name`, `is_system_defined`)
+VALUES
 ('Education',1);

 INSERT INTO `m_code_value`(`code_id`,`code_value`,`order_position`)
@@ -141,7 +141,7 @@ from x_registered_table r;

 -- ==== Chart of Accounts =====
 truncate `acc_gl_account`;
-INSERT INTO `acc_gl_account` VALUES 
+INSERT INTO `acc_gl_account` VALUES
 (1,'Petty Cash Balances',NULL,'11100',0,1,2,1,NULL),
 (2,'Cash in Valut 1',NULL,'11101',0,1,1,1,NULL),
 (3,'Bank Balances',NULL,'11200',0,1,2,1,NULL),
@@ -237,4 +237,4 @@ INSERT INTO `acc_gl_account` VALUES
 (94,'Modem',NULL,'42902',0,1,1,5,NULL),
 (95,'Meals',NULL,'42903',0,1,1,5,NULL),
 (96,'Transportation',NULL,'42904',0,1,1,5,NULL),
-(97,'Miscellaneous',NULL,'42905',0,1,1,5,NULL);
+(97,'Miscellaneous',NULL,'42905',0,1,1,5,NULL);
@@ -55,4 +55,4 @@ CREATE TABLE `risk_analysis` (
  `fi_repayment_capacity` decimal(19,6) DEFAULT NULL,
  PRIMARY KEY (`client_id`),
  CONSTRAINT `FK_risk_analysis_1` FOREIGN KEY (`client_id`) REFERENCES `m_client` (`id`)
-) ENGINE=InnoDB DEFAULT CHARSET=UTF8MB4;
+) ENGINE=InnoDB DEFAULT CHARSET=UTF8MB4;
@@ -13,4 +13,4 @@ This demo database contains:
 - Configuration
  - No 'additional data' through the 'datatables' approach is setup
  - One 'code' is setup called 'Client Identifier' with default values of {'Passport number'} - (required for Client Identity Document functionalty)
-  - Enable/Disable configuration has one entry named 'maker-checker' to allow people to enable disable this feature at global level. It is off or disabled by default.
+  - Enable/Disable configuration has one entry named 'maker-checker' to allow people to enable disable this feature at global level. It is off or disabled by default.
@@ -65,4 +65,4 @@ INSERT INTO `mifostenant-latam`.`m_code_value` (`code_id`, `code_value`, `order_


 INSERT INTO `mifostenant-latam`.`m_code` (`code_name`, `is_system_defined`) VALUES ('Education', 1);
-INSERT INTO `mifostenant-latam`.`m_code_value` (`code_id`, `code_value`, `order_position`) VALUES (3, 'Primary', 1); INSERT INTO `mifostenant-latam`.`m_code_value` (`code_id`, `code_value`, `order_position`) VALUES (3, 'Secondary', 2); INSERT INTO `mifostenant-latam`.`m_code_value` (`code_id`, `code_value`, `order_position`) VALUES (3, 'University', 3);
+INSERT INTO `mifostenant-latam`.`m_code_value` (`code_id`, `code_value`, `order_position`) VALUES (3, 'Primary', 1); INSERT INTO `mifostenant-latam`.`m_code_value` (`code_id`, `code_value`, `order_position`) VALUES (3, 'Secondary', 2); INSERT INTO `mifostenant-latam`.`m_code_value` (`code_id`, `code_value`, `order_position`) VALUES (3, 'University', 3);