Partitons for empty tables #282
Open
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
This "if" just disturb create partition for empty table and force you to use "if select count (*) = 0 from tablename then create_range_partition(p_count = 0) else create_range_partition(p_=null, let pathman count how many partition need to) And it wery often create partition of empty table in case of liquibase or other db struct maneger
Update range.sql
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 "if" just disturb create partition for empty table and force you to use "if select count (*) = 0 from tablename then create_range_partition(p_count = 0) else create_range_partition(p_=null, let pathman count how many partition need to)
And it very often create partition of empty table in case of liquibase or other db struct maneger