Currently the only way to detect COLSCANs is either to run an explain before or to parse the logs. The only way to disable COLSCANs is on the database level via a flag. If we had an indication on the query result that a COLSCAN occurred, then flexible handling  on a case-by-case basis depending on other metrics would be much easier than having to sift through the logs on a regular basis after the fact. The driver should know that information for each query after execution anyways, why not expose it? Thanks