Skip to content

Add table to record user confirmation of duplicate profiles#12081

Merged
vrajmohan merged 1 commit intomainfrom
vm-add-duplicate-profile-acknowledgements
Apr 22, 2025
Merged

Add table to record user confirmation of duplicate profiles#12081
vrajmohan merged 1 commit intomainfrom
vm-add-duplicate-profile-acknowledgements

Conversation

@vrajmohan
Copy link
Copy Markdown
Contributor

changelog: Upcoming Features, One Account, Add table to record user confirmation of duplicate profiles

create_table :duplicate_profile_confirmations do |t|
t.references :profile, foreign_key: true, null: false
t.timestamp :confirmed_at, null: false
t.json :duplicate_profiles, null: false
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an expected structure for the json column?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes its supposed to be an array of ids.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would an integer array integer[] suffice?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be, but I don't see a real advantage.

The table will be updated using Ruby/Rails code and SQL queries, if any, are likely to be on the other columns.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's preferable to choose a simpler/smaller type, especially one that could be foreign keys. I also think we could also consider normalizing the table with a row for each duplicate to allow for individual updates on a given relationship for each if needed in the future?

For clarity, should the column indicate they are identifiers and be named duplicate_profile_id(s)?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think duplicate_profile_ids makes the most sense.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I considered normalizing the duplicates but didn't think it is worth it - with the current design, the user is acknowledging the set as a whole and it is fine to add a new set if the duplicates change.

I agree that duplicate_profile_ids is better.

The argument of int array vs json is becoming pedantic in my opinion. I still think that JSON upholds the principle of least surprise. I am willing to go with int arrays if that will move this work along.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think integer[] is preferable if we'll only ever be storing a list of integers.

@vrajmohan vrajmohan force-pushed the vm-add-duplicate-profile-acknowledgements branch 2 times, most recently from 125fe48 to 4d132dc Compare April 16, 2025 23:15
@vrajmohan vrajmohan force-pushed the vm-add-duplicate-profile-acknowledgements branch from 4d132dc to 10c943d Compare April 17, 2025 13:13
@vrajmohan vrajmohan marked this pull request as ready for review April 18, 2025 13:32
changelog: Upcoming Features, One Account, Add table to record user confirmation of duplicate profiles
@vrajmohan vrajmohan force-pushed the vm-add-duplicate-profile-acknowledgements branch from c84fe09 to a6bef84 Compare April 22, 2025 16:52
@vrajmohan vrajmohan merged commit 3ea0697 into main Apr 22, 2025
1 check passed
@vrajmohan vrajmohan deleted the vm-add-duplicate-profile-acknowledgements branch April 22, 2025 17:15
MrNagoo pushed a commit that referenced this pull request Apr 28, 2025
changelog: Upcoming Features, One Account, Add table to record user confirmation of duplicate profiles
MrNagoo added a commit that referenced this pull request Aug 12, 2025
update config

update connector

update identity config

LG-15974: Add document_type to in_person_enrollments table (#12096)

Used to pass the type of ID to downstream IPP vendor

Sub-task: LG-16126

[skip changelog]

files

Add table to record user confirmation of duplicate profiles (#12081)

changelog: Upcoming Features, One Account, Add table to record user confirmation of duplicate profiles

LG-15974: Add document_type to in_person_enrollments table (#12096)

Used to pass the type of ID to downstream IPP vendor

Sub-task: LG-16126

[skip changelog]

files

LG-15974: Add document_type to in_person_enrollments table (#12096)

Used to pass the type of ID to downstream IPP vendor

Sub-task: LG-16126

[skip changelog]

config

turn off config

turn off config

update

turn off health check

update config

stop data-warehouse

undo gem

blank model

turn on the WAR HOUSE

gemfile

lock

update typo

turn off warehouse

turn off

remove dw ref

undo adapter

redshift again

update the WARHOUSE

use store

update config

redshift maybe

report house

make instance

update prefix

update configuration hash

ssl mode

root cert, search paths

rm ssl

rm unused controller
MrNagoo added a commit that referenced this pull request Oct 30, 2025
update config

update connector

update identity config

LG-15974: Add document_type to in_person_enrollments table (#12096)

Used to pass the type of ID to downstream IPP vendor

Sub-task: LG-16126

[skip changelog]

files

Add table to record user confirmation of duplicate profiles (#12081)

changelog: Upcoming Features, One Account, Add table to record user confirmation of duplicate profiles

LG-15974: Add document_type to in_person_enrollments table (#12096)

Used to pass the type of ID to downstream IPP vendor

Sub-task: LG-16126

[skip changelog]

files

LG-15974: Add document_type to in_person_enrollments table (#12096)

Used to pass the type of ID to downstream IPP vendor

Sub-task: LG-16126

[skip changelog]

config

turn off config

turn off config

update

turn off health check

update config

stop data-warehouse

undo gem

blank model

turn on the WAR HOUSE

gemfile

lock

update typo

turn off warehouse

turn off

remove dw ref

undo adapter

redshift again

update the WARHOUSE

use store

update config

redshift maybe

report house

make instance

update prefix

update configuration hash

ssl mode

root cert, search paths

rm ssl

rm unused controller
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants