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
Selecting the following in the contacts query yields duplicate results for several contacts. In most cases, on one line there is an address and then there are nulls for the address on the next line.
In WA, contact_ids 337, 724, 1209, 1662, 497, 157, 170, 899, 1029, 2186 have this problem.
SELECT DISTINCT
local_student_id,
contact_id,
con.first_name,
con.last_name,
email_address,
cell_phone_number,
contact_type,
physical_address_line_1,
physical_address_line_2,
physical_address_city,
physical_address_state,
physical_address_zip,
mailing_address_line_1,
mailing_address_line_2,
mailing_address_city,
mailing_address_state,
mailing_address_zip
home_phone_number,
work_phone_number,
is_legal,
emergency_contact
FROM public.students stud
LEFT JOIN contact_info_one_row_per_stu_contact_pair AS con USING(student_id)
ORDER BY contact_id;
The text was updated successfully, but these errors were encountered:
It happens regardless when selecting in long form. This is something we should track down and fix, but I don't think that it needs to be done right this instant. I was trying to document this as an improvement.
Selecting the following in the contacts query yields duplicate results for several contacts. In most cases, on one line there is an address and then there are nulls for the address on the next line.
In WA, contact_ids 337, 724, 1209, 1662, 497, 157, 170, 899, 1029, 2186 have this problem.
The text was updated successfully, but these errors were encountered: