cockroachdb

I apologize if this is the wrong venue for this. I can't tell if this behavior is buggy or just not what I expected.

Describe the problem

The disable_full_table_scans option seems so close to what I'm looking for, but not quite right.

My team is building an application atop CockroachDB with the intent of scaling horizontally. Naturally, we want to avoid using queries that require

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.

Everywhere that a panel references another one in configuration (table, graph, and visual transform panels) they use the index of the panel. This is fragile and I can't remember any reason for it to be like this. Instead these panels should reference panel.id, a uuid, instead of the panel index. This way when panels are reordered or added/removed the reference stays constant.