DATAMONGO-1236 - Update does not include type hint correctly. #301
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
Prepare issue branch.
We now use property type information when mapping fields affected by an update in case we do not have proper entity information within the context. This allows more precise type resolution required for determining the need to write type hints for a given property.
christophstrobl
added a commit
that referenced
this pull request
Jun 24, 2015
We now quote the original criteria before actually wrapping it inside of an regular expression for case insensitive search. This happens not only to case insensitive is, startsWith, endsWith criteria but also to those using like. In that case we quote the part between leading and trailing wildcard if required. Original pull request: #301.
christophstrobl
added a commit
that referenced
this pull request
Jun 24, 2015
We now quote the original criteria before actually wrapping it inside of an regular expression for case insensitive search. This happens not only to case insensitive is, startsWith, endsWith criteria but also to those using like. In that case we quote the part between leading and trailing wildcard if required. Original pull request: #301.
christophstrobl
added a commit
that referenced
this pull request
Jun 24, 2015
We now quote the original criteria before actually wrapping it inside of an regular expression for case insensitive search. This happens not only to case insensitive is, startsWith, endsWith criteria but also to those using like. In that case we quote the part between leading and trailing wildcard if required. Original pull request: #301.
christophstrobl
added a commit
that referenced
this pull request
Jun 24, 2015
We now quote the original criteria before actually wrapping it inside of an regular expression for case insensitive search. This happens not only to case insensitive is, startsWith, endsWith criteria but also to those using like. In that case we quote the part between leading and trailing wildcard if required. Original pull request: #301.
christophstrobl
added a commit
that referenced
this pull request
Jun 30, 2015
We now use property type information when mapping fields affected by an update in case we do not have proper entity information within the context. This allows more precise type resolution required for determining the need to write type hints for a given property. Original pull request: #301.
odrotbohm
added a commit
that referenced
this pull request
Jun 30, 2015
Removed the creation of a BasicMongoPersistentEntity in favor of always handing ClassTypeInformation.OBJECT into the converter in case not entity can be found. This makes sure type information is written for updates on properties of type Object (which essentially leads to no PersistentEntity being available). Original pull request: #301.
christophstrobl
added a commit
that referenced
this pull request
Jun 30, 2015
We now use property type information when mapping fields affected by an update in case we do not have proper entity information within the context. This allows more precise type resolution required for determining the need to write type hints for a given property. Original pull request: #301.
odrotbohm
added a commit
that referenced
this pull request
Jun 30, 2015
Removed the creation of a BasicMongoPersistentEntity in favor of always handing ClassTypeInformation.OBJECT into the converter in case not entity can be found. This makes sure type information is written for updates on properties of type Object (which essentially leads to no PersistentEntity being available). Original pull request: #301.
christophstrobl
added a commit
that referenced
this pull request
Jun 30, 2015
We now use property type information when mapping fields affected by an update in case we do not have proper entity information within the context. This allows more precise type resolution required for determining the need to write type hints for a given property. Original pull request: #301.
odrotbohm
added a commit
that referenced
this pull request
Jun 30, 2015
Removed the creation of a BasicMongoPersistentEntity in favor of always handing ClassTypeInformation.OBJECT into the converter in case not entity can be found. This makes sure type information is written for updates on properties of type Object (which essentially leads to no PersistentEntity being available). Original pull request: #301.
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.
We now use property type information when mapping fields affected by an update in case we do not have proper entity information within the context. This allows more precise type resolution required for determining the need to write type hints for a given property.