feat: support spatial functions of MySQL 8+ #4794
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
|
Can you please fix conflicts? thanks :) |
* add `legacySpatialSupport` option for replacing dropped functions to new ones * use srid column option like PostgreSQL Close typeorm#3702
jeiea
force-pushed
the
mysql-new-spatial
branch
from
81352bd
to
21ce4f9
Compare
|
Fixed. Thanks for the reply. |
|
Please let me know if any consideration or elaboration is needed. |
|
Sorry for waiting and thanks for your great efforts! |
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.
Add
legacySpatialSupportoption for replacingdropped functions to new ones
Use srid column option like PostgreSQL
Implemented the OP's suggestion naively.
Close #3702