feat: add unscoped tag support for orm struct
#3464
+128
−9
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
|
@fainc Would you please add associated unit testing case for your updates? |
gqcn
changed the title
unscoped tag support for orm struct
|
@fainc Any updates? |
Later, plz. very busy this week |
|
@gqcn Sorry I'm late. |
@gqcn Sorry I'm late. |
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.
Enhance OrmTagForWithUnscoped
Sometimes we need to actively associate "deleted" data instead of excluding it. For example, after deleting an employee, we hope that other data can be associated with the name of the deleted employee to avoid duplication of name data.