You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We’ve identified that there is no longer a need to use DB views as a layer above our transaction table. It’s adding problems to our deployments and general complexity.
Remove the creation of committee transaction views and move sql logic back into the base transaction manager
QA Notes
Verify unit test passing, and that there are no new gaps introduced.
original implementation of views: [https://github.com//pull/769/files#diff-d56ea0f167f0f4f4406e7166d1d9e3646ced77d96105c2589f0f40af87024457|https://github.com//pull/769/files#diff-d56ea0f167f0f4f4406e7166d1d9e3646ced77d96105c2589f0f40af87024457|smart-link]
We’ve identified that there is no longer a need to use DB views as a layer above our transaction table. It’s adding problems to our deployments and general complexity.
Remove the creation of committee transaction views and move sql logic back into the base transaction manager
QA Notes
Verify unit test passing, and that there are no new gaps introduced.
original implementation of views: [https://github.com//pull/769/files#diff-d56ea0f167f0f4f4406e7166d1d9e3646ced77d96105c2589f0f40af87024457|https://github.com//pull/769/files#diff-d56ea0f167f0f4f4406e7166d1d9e3646ced77d96105c2589f0f40af87024457|smart-link]
DEV Notes
null
Design
null
See full ticket and images here: FECFILE-1869
The text was updated successfully, but these errors were encountered: