Fix infinite loop that occurs when an data\Entity class is used as data\Entity::_model.
#782
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
…`data\Entity::_model`.
nateabele
added a commit
that referenced
this pull request
Jan 11, 2013
Fix infinite loop that occurs when an `data\Entity` class is used as `data\Entity::_model`.
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 may bug occurs when using external ORM which are not based on core
data\Model.I'm not sure for this one because at first glance it looks like
data\Entity::_modelshouldn't be filled with something which is not a coredata\Modelsubclass.However if it makes sense, maybe a:
would here be better than a:
for fixing this issue ?