force little endian byte order #20
Open
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
force geometry WKB to be generated little endian byte order since mysql seems to have a bug: https://dev.mysql.com/worklog/task/?id=1076 Quote: http://postgis.refractions.net/pipermail/postgis-users/2003-June/002651.html * The MySQL code contains an assumption in the WKB handling that all WBK will be little endian. If you run MySQL spatial on a big endian machine (Sparc, PowerPC, PA-RISC) you will find things go amiss when you try to send WKB to little endian machines (x86), because your big endian machine will be creating invalid data (big endian data incorrectly flagged as little endian).
Contributor
|
Missed this one for some reason. I'll review soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Tested on MySQL 5.7.11 on OSX
force geometry WKB to be generated little endian byte order since mysql seems to have a bug:
https://dev.mysql.com/worklog/task/?id=1076
Quote:
http://postgis.refractions.net/pipermail/postgis-users/2003-June/002651.html
will be little endian. If you run MySQL spatial on a big endian machine
(Sparc, PowerPC, PA-RISC) you will find things go amiss when you try to
send WKB to little endian machines (x86), because your big endian
machine will be creating invalid data (big endian data incorrectly
flagged as little endian).