cockroachdb

Currently, tree.NotExpr is implemented natively in the vectorized engine, so we have to fallback to the older row-by-row engine to evaluate it. We should, instead, vectorize NotExpr.

I think the implementation will be quite similar to how tree.IsNullExpr implemented, and I think we will want to implement two version of NotExpr operator:

• one for projections, which populates a `coldata

It would be great to implement test case reduction strategies in SQLancer itself. The advantage of doing this in SQLancer, rather than an external tool like C-Reduce, is that we have all the information on whether a specific bug is still triggered (e.g., that two queries should yield the same result) and that the reduction can likely go further than when having an external interestingness test (e.

Right now this will just generate a stack trace. If instead all these errors are caught with an error registered in here then in the UI it will show up as just a message in a warning box not a stacktrace in an error box.

Hopefully, this can be easily integration tested in desktop/panel/program.test.js by running t