[AERIE-1982] feat: add user sequence table

[camargo]

• Tickets addressed: AERIE-1982
• Review: By commit
• Merge strategy: Merge (no squash)

Description

• Add first-draft of user_sequence table for storing user-defined sequences for 0.13.0

Verification

Test the user_sequence table is added to the commanding database

Future work

Possible renaming:

• aerie_commanding database to aerie_sequencing
• sequence table to expansion_sequence

[goetzrrGit]

I was thinking about this for a couple of minutes and I realized we never talked about user-defined sequences with respect to their sequence ID. On the command expansion side, we make those unique but on the user side, they can create multiple sequences for a sequence ID with no sequence ID checking.

Use Case 1:

Create a new sequence with seqID A, save - no issue
I want to update the sequence, save - no issue

Use Case 2:

Create a new sequence with seqID A, save - no issue
I create a new sequence with seqID B, save - no issue

Use Case 3:

Create a new sequence with seqID A, save - no issue
I create a brand new sequence with seqID A, save - Problem: two sequences with the same seqID

This can get more complicated as there can be different states a sequence can be in ( Draft, Accepted, Rejected, etc.)

I am not saying we should address this in this ticket but something we should have a meeting about in the future.

[dyst5422]

I was thinking about this for a couple of minutes and I realized we never talked about user-defined sequences with respect to their sequence ID. On the command expansion side, we make those unique but on the user side, they can create multiple sequences for a sequence ID with no sequence ID checking.

Use Case 1:

Create a new sequence with seqID A, save - no issue I want to update the sequence, save - no issue

Use Case 2:

Create a new sequence with seqID A, save - no issue I create a new sequence with seqID B, save - no issue

Use Case 3:

Create a new sequence with seqID A, save - no issue I create a brand new sequence with seqID A, save - Problem: two sequences with the same seqID

This can get more complicated as there can be different states a sequence can be in ( Draft, Accepted, Rejected, etc.)

I am not saying we should address this in this ticket but something we should have a meeting about in the future.

Sequence IDs are very specifically NOT something we are managing. That is on the missions to determine. The unique ID for sequences we have are disconnected from the seqid and in fact the seqid isn't necessarily part of what is tracked by AERIE at all. I would think the workflow would haver the seqid somewhere in the name field, but ultimately, the seqid is determined by the seqid property on the sequence object in the body of the sequence file.

[goetzrrGit]

I was thinking about this for a couple of minutes and I realized we never talked about user-defined sequences with respect to their sequence ID. On the command expansion side, we make those unique but on the user side, they can create multiple sequences for a sequence ID with no sequence ID checking.
Use Case 1:
Create a new sequence with seqID A, save - no issue I want to update the sequence, save - no issue
Use Case 2:
Create a new sequence with seqID A, save - no issue I create a new sequence with seqID B, save - no issue
Use Case 3:
Create a new sequence with seqID A, save - no issue I create a brand new sequence with seqID A, save - Problem: two sequences with the same seqID
This can get more complicated as there can be different states a sequence can be in ( Draft, Accepted, Rejected, etc.)
I am not saying we should address this in this ticket but something we should have a meeting about in the future.

Sequence IDs are very specifically NOT something we are managing. That is on the missions to determine. The unique ID for sequences we have are disconnected from the seqid and in fact the seqid isn't necessarily part of what is tracked by AERIE at all. I would think the workflow would haver the seqid somewhere in the name field, but ultimately, the seqid is determined by the seqid property on the sequence object in the body of the sequence file.

You are right, I forgot we are not managing sequence ID and that a mission should do that. :P Let me close that can of worms and bury it.

[goetzrrGit]

Nothing much to add besides creating a ticket from Dylan's comment.

[goetzrrGit]

Looks great!!!