Panic with `LITERAL != COLUMN`

[jscheid]

Describe the problem

psql> CREATE CACHE FROM SELECT SUM(val) FROM m WHERE 123 != foo_id;
server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.

To Reproduce

See above. I don't think any special table layout is necessary to reproduce but let me know if you need more information.

Expected behavior

Should work as foo_id != 123 does, or as 123 = foo_id does.

Additional data / screenshots

See full backtrace

Environment

• ReadySet version [e.g., beta-2022-11-02]: stable-240919
• ReadySet deployment method [e.g, local orchestrator, Helm chart, binaries]: binary built from source
• Upstream database and version [e.g., Postgres 14]: Postgres 14
• Client app [e.g., psql, mysql, SQLAlchemy, TypeORM]: psql

Additional context

Famous last words? 😺

[gvsg-rs]

We did not in fact check 'op.is_ordering_comparison()' in this code path. Thank you for the report!

[vassili-zarouba]

The issue has been fixed and merged into main branch.