Change Details

As discussed in today's engineering meeting, we would like to simplify the ce_organizers table so that certain operations like limit, count, and pagination are easier. ===Rough proposal=== We currently store tuples of (event, user, role), so there can be multiple rows for the same event+user combination, one for each role. The new proposal is that we make the "roles" column a bit set, and store all roles in a single row. The motivations for this are: - Limit, count, and pagination would be much easier - We don't need timestamps (created_at, deleted_at) for each role **Details TBD**

As discussed in today's engineering meeting, we would like to simplify the ce_organizers table so that certain operations like limit, count, and pagination are easier. ===Rough proposal=== We currently store tuples of (event, user, role), so there can be multiple rows for the same event+user combination, one for each role. The new proposal is that we make the "roles" column a bit set, and store all roles in a single row. The motivations for this are: - Limit, count, and pagination would be much easier - We don't need timestamps (created_at, deleted_at) for each role ===AC=== - Rename the column - Remove it from the index - Adjust logic in OrganizersStore

As discussed in today's engineering meeting, we would like to simplify the ce_organizers table so that certain operations like limit, count, and pagination are easier. ===Rough proposal=== We currently store tuples of (event, user, role), so there can be multiple rows for the same event+user combination, one for each role. The new proposal is that we make the "roles" column a bit set, and store all roles in a single row. The motivations for this are: - Limit, count, and pagination would be much easier - We don't need timestamps (created_at, deleted_at) for each role **Details TBD**===AC=== - Rename the column - Remove it from the index - Adjust logic in OrganizersStore