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
materialize=> select 'foo'::string < 5::int; ?column? ---------- f (1 row)
vs.
postgres=# select 'foo'::text < 5::int; ERROR: operator does not exist: text < integer
@sploiselle tells me his ongoing work should eventually address this!
The text was updated successfully, but these errors were encountered:
Found another instance of this:
The following two queries work in Materialize but fail in PG:
Query:
(VALUES ( 1 < ANY(SELECT * FROM (VALUES (1)) s WHERE false), 1 < ANY(VALUES (0)), 1 < ANY(VALUES (1)), 1 < ANY(VALUES (2)), 1 < ANY(VALUES (NULL)), 1 < ANY(VALUES (0), (NULL)), 1 < ANY(VALUES (1), (NULL)), 1 < ANY(VALUES (2), (NULL)), NULL < ANY(SELECT * FROM (VALUES (1)) s WHERE false), NULL < ANY(VALUES (0)), NULL < ANY(VALUES (1)), NULL < ANY(VALUES (2)), NULL < ANY(VALUES (NULL)), NULL < ANY(VALUES (0), (NULL)), NULL < ANY(VALUES (1), (NULL)), NULL < ANY(VALUES (2), (NULL)) ))
PG:
ERROR: operator does not exist: integer < text LINE 6: 1 < ANY(VALUES (NULL)),
MZ in test/sqllogictest/subquery.slt
test/sqllogictest/subquery.slt
column1 | column2 | column3 | column4 | column5 | column6 | column7 | column8 | column9 | column10 | column11 | column12 | column13 | column14 | column15 | column16 ---------+---------+---------+---------+---------+---------+---------+---------+---------+----------+----------+----------+----------+----------+----------+---------- t | f | f | t | | f | f | | | | | | | | |
Sorry, something went wrong.
sploiselle
Successfully merging a pull request may close this issue.
vs.
@sploiselle tells me his ongoing work should eventually address this!
The text was updated successfully, but these errors were encountered: