You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
root@localhost:26257/defaultdb> PREPARE pselect3 AS SELECT * FROM "test_collate" WHERE (("id", "string_field")) = ANY($1);
PREPARE
Time: 2ms total (execution 1ms / network 1ms)
root@localhost:26257/defaultdb> EXECUTE pselect3(Array[(1, 'str_collate_1')]);
id | string_field
-----+----------------
1 | str_collate_1
(1 row)
However if I send the args in binary format, I will receive:
unsupported comparison: collatedstring{en_us_u_ks_level2} to string"
I write the binary encoding for tuple array myself, and uses oid 25 for collated string. It works for all other cases except collated string. Did I miss anything?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Related question to #117849, but with binary protocol.
I have a table:
And this would work in console
However if I send the args in binary format, I will receive:
I write the binary encoding for tuple array myself, and uses oid 25 for collated string. It works for all other cases except collated string. Did I miss anything?
All reactions