wkb encoding/decoder for working with mysql/mariadb queries#85
Closed
wkb encoding/decoder for working with mysql/mariadb queries#85
Conversation
paulmach
force-pushed
the
encoding-mysql
branch
from
2d49b3c to
2c751ad
Compare
Owner
Author
|
This is superseded by #88 The helper is now ewkb.ScannerPrefixSRID |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Addresses issues seen with #79 and #61
Basically, mysql/mariadb prefix the 4 byte srid. This PR adds helpers to deal with that.
For Insert you need to use WKT or prefix your binary data with that 4 bytes.
wkb.MySQLValue(orb.Point{1, 1}, optionalSRID)helps with that.For reading you can
ST_asBinaryor use thewkb.MySQLScanner(p)See the readme updates in the PR for more details.