Support for mysql POINT data type #221
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
dresende
added a commit
that referenced
this pull request
Jul 7, 2013
|
I'm going to merge this locally. I'm just making it work on the other drivers. |
dresende
added a commit
that referenced
this pull request
Jul 8, 2013
Changes unknown property type error to throw a well defined code
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 adds support at both the DDL and property level. Also includes 2 new tests. Hope you don't mind these being stuffed in the existing test files. I can move them to a new test if need be. This pattern should be applicable for any of the geospatial types (Geometry/Curve/Polygon/etc.). I didn't have a current need for those types so I didn't add them.