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
int8recv
substring(bytea)
In PG, we use the following:
SELECT BIT_XOR(('x'||SUBSTR(MD5(%s), 17, 16))::bit(64)::bigint) FROM %s
to compare the results of two queries.
However, since RW hasn't supported the bit data type, we are unable to convert the hexadecimal varchar into a bigint.
bit
bigint
@xiangjinwu gives the solution that:
int8recv(bytea) -> bigint
i64::from_be_bytes
Once we have these two supported, we write the following instead:
int8recv(SUBSTR(decode(MD5(%s), 'hex'), 9, 8)) int8recv(SUBSTR(sha256(%s), 9, 8))
cc: @cyliu0
The text was updated successfully, but these errors were encountered:
int8send
xiangjinwu
Successfully merging a pull request may close this issue.
In PG, we use the following:
to compare the results of two queries.
However, since RW hasn't supported the
bit
data type, we are unable to convert the hexadecimal varchar into abigint
.@xiangjinwu gives the solution that:
int8recv(bytea) -> bigint
, which is already supported as an internal functioni64::from_be_bytes
. Expose it to user.substring(bytea)
.Once we have these two supported, we write the following instead:
cc: @cyliu0
The text was updated successfully, but these errors were encountered: