In order to improve search performance of some resources, the dialaction table should be refactored to follow relational database guidelines … (i.e. foreign keys)
Currently dialaction is the representation of destination for a lot of resource (ex: user, incall, etc..) The relation between dialaction and other resource is done in a wrong way and make search slow and non-optimised
We would like to use foreign keys instead of this pseudo-relation
Things to take care for child issues:
Find a way to migrate progressively marshmallow schema from wazo-confd
Find a way to migrate progressively wazo-agid code
NOTE: this epic is not the best solution to migrate dialaction, it imply only change to improve performance. More refactor/migration should be done to have a nice inheritance DB and nomenclature (ex: )
Medium
In order to improve search performance of some resources, the dialaction table should be refactored to follow relational database guidelines … (i.e. foreign keys)
Currently
dialactionis the representation of destination for a lot of resource (ex: user, incall, etc..)The relation between
dialactionand other resource is done in a wrong way and make search slow and non-optimisedWe would like to use foreign keys instead of this pseudo-relation
Things to take care for child issues:
Find a way to migrate progressively marshmallow schema from wazo-confd
Find a way to migrate progressively wazo-agid code
NOTE: this epic is not the best solution to migrate dialaction, it imply only change to improve performance. More refactor/migration should be done to have a nice inheritance DB and nomenclature (ex: )