refactor: association types #187
Merged
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
- one_to_one - one_to_many - many_to_one - many_to_many refactor: add "implementation" field to the association definition to be on of: - sql_cross_table - generic - foreignkey
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR implements a change in the zendro domain specific language to define data models, specifically their associations between each other.
Changes
With this PR there are 4 types of possible association types:
one_to_onemany_to_oneone_to_manymany_to_manyAdditionally two additional fields were added.
implementation. Can be one offoreignkeys,generic,sql_cross_table. Describes the implementation on the model levelreverseAssociation. Name of the reverse association. Can be omitted for codgen of the server. Needed in the SPA.The field
reverseAssocitionTypeformany_to_manyvia foreign key arrays was removed. If an association is of typemany_to_manyand the implementation isforeignkeysit will be done via foreignkey arrays.The fields
keyInin andkeysInwere unified to fieldkeysIn