PRC-507: Address phones bug on get organisation. #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a bug where all addresses included the phone numbers for all other addresses in this organisation.
The mapping between organisation address phones and organisation phones was not quite strict enough.
I am now thinking that the simpler, and clearer, solution for address-phones is to hold them separately (for both contacts and organisations) from global phones. So we'd have
organisation-global-phones
andorganisation-address-phones
as distinct tables, each containing the phone-type, phone-number and ext-number, plus the audit columns. The problem at the moment is that there is no simple way to get JUST the global phone numbers, as to do so, we need to get all phone numbers and then filter out the address-specific phone numbers, which leads to complexity and lack of clarity in the code, which I think is unnecessary.