Реструктурированы визиторы для императивного мэппинга #126
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
!!!Not yet working!!! ? Need to verify property mapping with the correct FK specifications ?
and un-commenting test code for multiple toOne relations
For automatic FK passing to property relations.
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.
Предлагается решение тикета #121.
FKeyMapper интегрирован в PropMapper.
Проверка существования ForeignKey перед созданием теперь выполняется с учетом имени ссылочного свойства, для которого создается FK. За счет объединения двух визиторов созданный FK напрямую используется для мэппинга свойств в ORM.
Попутно введена конвенция именования полей для FK, что, как предполагается, решает также тикет #123.