Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Separate postgresql tables for device, user and shamir recovery invitations #4820

Closed
vxgmichel opened this issue Jul 5, 2023 · 1 comment
Closed

Separate postgresql tables for device, user and shamir recovery invitations #4820

vxgmichel opened this issue Jul 5, 2023 · 1 comment
Labels
A-Server Area: Parsec Server enhancement Improve functionality, potentially changing behavior I-Postgresql Impact: Postgresql issue I-Python Impact: Python-related stuff
Milestone
v3-next

Comments

@vxgmichel
Copy link
Contributor

At the moment all those invitations are stored in the same table.

However, they have differences:

  • user invitations provide a claimer_email (of type string) field
  • shamir invitations provide a claimer (of type UserID) field

It would makes sens to split those invitations into different tables.
@vxgmichel vxgmichel added the enhancement Improve functionality, potentially changing behavior label Jul 5, 2023
@TimeEngineer TimeEngineer changed the title Separate postresql tables for device, user and shamir recovery invitations Separate postgresql tables for device, user and shamir recovery invitations Jul 7, 2023
@FirelightFlagboy FirelightFlagboy added this to the V3 milestone Jul 7, 2023
@touilleMan touilleMan modified the milestones: Parsec V3 Stable, v3.0 Jan 29, 2024
This was referenced Feb 9, 2024
Closed
Closed
@mmmarcos mmmarcos added the I-Postgresql Impact: Postgresql issue label Feb 27, 2024
@mmmarcos mmmarcos added I-Python Impact: Python-related stuff A-Server Area: Parsec Server labels Mar 27, 2024
@mmmarcos mmmarcos modified the milestones: v3.0-beta, v3.0 Mar 27, 2024
@mmmarcos mmmarcos modified the milestones: v3.0, v3-next Apr 22, 2024
@vxgmichel vxgmichel removed their assignment Feb 10, 2025
@vxgmichel
Copy link
Contributor Author

Outdated by #9394

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Server Area: Parsec Server enhancement Improve functionality, potentially changing behavior I-Postgresql Impact: Postgresql issue I-Python Impact: Python-related stuff
Projects
None yet
Milestone
v3-next
Development

No branches or pull requests
4 participants
@mmmarcos @touilleMan @vxgmichel @FirelightFlagboy