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
text
CREATE TABLE test(t text); INSERT INTO test(t) VALUES (CONCAT(0x020100, '1234')); SELECT hex(t) FROM test;
CREATE FOREIGN TABLE IF NOT EXISTS test(t text) SERVER mysql OPTIONS (dbname 'db', table_name 'test'); SELECT encode(t::bytea, 'hex') FROM test;
all bytes after 0x00 and itself are removed, but it will be complete fetched when using bytea as field type:
0x00
bytea
CREATE FOREIGN TABLE IF NOT EXISTS test(t bytea) SERVER mysql OPTIONS (dbname 'db', table_name 'test'); SELECT encode(t::bytea, 'hex') FROM test;
It's seems related to confluentinc/kafka-connect-jdbc#1216 as postgresql doesn't support storing 0x00 in text unlike mysql due to c-style NUL-terminated string https://stackoverflow.com/questions/1347646/postgres-error-on-insert-error-invalid-byte-sequence-for-encoding-utf8-0x0 https://postgrespro.com/list/thread-id/1897280
The text was updated successfully, but these errors were encountered:
No branches or pull requests
mysql side
pgsql side
all bytes after
0x00
and itself are removed, but it will be complete fetched when usingbytea
as field type:It's seems related to confluentinc/kafka-connect-jdbc#1216 as postgresql doesn't support storing
0x00
intext
unlike mysql due to c-style NUL-terminated string https://stackoverflow.com/questions/1347646/postgres-error-on-insert-error-invalid-byte-sequence-for-encoding-utf8-0x0 https://postgrespro.com/list/thread-id/1897280The text was updated successfully, but these errors were encountered: