Add the ability to change a table name to AliasableSqlTable #572
Conversation
This file contains hidden or 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
This mapper doesn't include the typed inserts, so it can easily be used without a class that matches a table row.
This is to more easily support sharding - we can create multiple new table objects with differing names, but other attributes the same. Or, we can create a table object with a supplier function that will change the table name at render time. This capability is NOT thread safe.
Name supplier creates an effectively mutable object and this is against the principles of the library.
A supplier creates an effectively mutable object and this is against the principles of the library. The AliasableSqlTable object provides support for changing the table name and should be used instead.
# Conflicts: # src/main/java/org/mybatis/dynamic/sql/util/mybatis3/CommonGeneralInsertMapper.java
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.
This creates a new instance of the table and all it's enclosed fields. This is useful for sharded databases.
Resolves #563