[FEAT] Adds support for constraints in relationships. [FIX] Replacing .yml in filenames. #2
Open
ghosthi wants to merge 2 commits into
Open
[FEAT] Adds support for constraints in relationships. [FIX] Replacing .yml in filenames. #2ghosthi wants to merge 2 commits into
ghosthi wants to merge 2 commits into
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
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.
What kind of change does this PR introduce? (pls check at least one)
Description
This PR fixes the replace on .yml file titles on migrations that used to be replaced with rtrim, which can lead to unexpected behaviour on Schemas with names ending with characters "y", "m" or "l".
This PR also introduces the feature of allowing the use of constraints in Schema Relationships without changing the previous behaviour.
Using the previous format on schema files like so
Will allow creation of relationship columns as usual.
With this PR, using it like this:
Will allow constrained relationships (with foreign key referenced) in the database.
Does this PR introduce a breaking change? (check one)
Related Issue