teklu tesfaye

reverted [OLMIS-6004] add sortable parameter to program search api

[OLMIS-6004] add sortable parameter to program search api

[OLMIS-5853] [OLMIS-5853] change native query

[OLMIS-5853] [OLMIS-5853] add test to find supervisory nodes by name and code

[OLMIS-6004] fix contract test error

[OLMIS-6004] fix contract test error

[revert][OLMIS-6004] add sortable parameter to program search api

[OLMIS-6004] add sortable parameter to program search api

[OLMIS-5852] [OLMIS-5853] overhaul the validation for supervisory node unique constraint

[OLMIS-5853] add case insensetive unique name index constraint for supervisory node

    • -0
    • +2
    /src/main/resources/db/migration/20190311133135739__unq_case_insensetive_supervisory_node_name.sql
[OLMIS-5852] add case insensetive unique code index constraint for supervisory node

    • -0
    • +2
    /src/main/resources/db/migration/20190311133120939__unq_supervisory_node_case_insesetive_code.sql
[OLMIS-5852] [OLMIS-5853]update test data for supervisory nodes name to avoid duplicate

actually, there was no decision about it, I implement it contemplating the above considerations. Hence I can change my implementation like you suggested and will remove the additional codes in the ...

actually, there was no decision about it, I implement it contemplating the above considerations. Hence I can change my implementation like you suggested and will remove the additional codes in the validation and repository.

It is also possible to add a constraint on the database as you said. But it will create an error on migration as there might be non-unique rows in the database already. Though I thought to delete n...

It is also possible to add a constraint on the database as you said. But it will create an error on migration as there might be non-unique rows in the database already. Though I thought to delete nonunique rows exist, still it will create an exception as they might be assigned as a foreign key for possible external related tables.

OLMIS-5853 tweak the supervisory node validation sequence

change supervisory node edit validation sequence fix functional test error

add message for key referenceData.error.supervisoryNode.name.mustBeUnique

[OLMIS-5852] add case insesetive unique code && [OLMIS-5853] add unique name constraint for supervisory Node
[OLMIS-5852] add case insesetive unique code && [OLMIS-5853] add unique name constraint for supervisory Node
* [OLMIS-5852] add case insesetive unique code && [OLMIS-5853] add unique name constraint for supervisory Node