-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Data Persistence following Subject Table Interactions #663
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
for more information, see https://pre-commit.ci
garrettmflynn
changed the title
Improve subject interaction with results
Data Persistence following Subject Table Interactions
Mar 12, 2024
Good catch. Thanks! I've made it so that the table revalidates when any |
@garrettmflynn Conflict now |
CodyCBakerPhD
approved these changes
Mar 13, 2024
CodyCBakerPhD
approved these changes
Mar 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While using the Subject Table with the generate test datasets, it became somewhat annoying to lose the associated source data + metadata results (forever...) when changing the subject name.
To address this, this PR improves the persistence of data when you update the subject table:
subject_id
values and maintaining the samesession_id
will result in data persistence on the samesubject_id
session_id
, the data will persist on the newsubject_id
I'm open to suggestions regarding further rules, changes to these, and any bugs you notice!