We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should add a GuidFormat connector option that specifies how the Guid type is read/written.
GuidFormat
Guid
Char36
CHAR(36)
Char32
CHAR(32)
Binary16
BINARY(16)
UUID_TO_BIN(x)
TimeSwapBinary16
UUID_TO_BIN(x,1)
OldBinary16
OldGuids=True
None
The text was updated successfully, but these errors were encountered:
Work in progress: master...ejball:guids
Sorry, something went wrong.
11dadc2
Added in 0.41.0.
No branches or pull requests
We should add a
GuidFormat
connector option that specifies how theGuid
type is read/written.Char36
CHAR(36)
are read/written asGuid
using lowercase hex and hyphens. (Current default behavior.)Char32
CHAR(32)
are read/written asGuid
using lowercase hex without hyphens.Binary16
BINARY(16)
are read/written asGuid
using big-endian byte order. MatchesUUID_TO_BIN(x)
.TimeSwapBinary16
BINARY(16)
are read/written asGuid
using big-endian byte order with time parts swapped. MatchesUUID_TO_BIN(x,1)
.OldBinary16
BINARY(16)
are read/written asGuid
using little-endian byte order. (Current behavior whenOldGuids=True
.)None
Guid
is not supported.CHAR(36)
andCHAR(32)
are read/written as strings;BINARY(16)
is read/written as a byte array.The text was updated successfully, but these errors were encountered: