Issue 44250: Invalidate QueryInfo caches after change to NameIdSettings.allowUserSpecifiedNames #669
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
…gs.allowUserSpecifiedNames - the sample type and data class queryInfo details for the name column will set the setShownInInsertView based on this allowUserSpecifiedNames setting so we need to invalidate the client side cache so that the updated information is retrieved for those table/query
|
Just as a heads-up, 21.11 release in biologics is failing a lot |
cnathe
added
TeamCity test review complete
and removed
needs TeamCity test review
labels
labkey-nicka
approved these changes
Nov 10, 2021
This was referenced Nov 13, 2021
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.
Rationale
https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=44250
The sample type and data class queryInfo details for the name column will set the setShownInInsertView based on this allowUserSpecifiedNames setting so we need to invalidate the client side cache so that the updated information is retrieved for those table/query in the apps.
Related Pull Requests
Changes