This repository has been archived by the owner on Jul 25, 2022. It is now read-only.
Feature/has one relation to nonexistant item #703
Merged
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
DarkSide666
added a commit
that referenced
this pull request
Mar 3, 2016
…tant-item Feature/has one relation to nonexistant item
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
(same as #698 but uses develop and not master)
currently hasOne of a no-sql model can reference any other model. When loading the row it will attempt to also load that related record and fetch the name. If this record does not exist or fails to load, then the loading operation with throw exception.
It is however a tolerable occurence when nosql is pointing to a non-existing element (non-relational database), and this should be handled gracefully.