试一下 UPDATE aaa SET kk = null WHERE xx != 0

给一下
explain select it_id where (c_type, cat_id) in ((30, 1), (30, 2), (30, 3), (20, 4), (20, 6), (20, 9), (20, 10));
结果？

自己打下脸，好像 (c_type, cat_id) 可以优化

https://dev.mysql.com/doc/refman/8.0/en/range-optimization.html#row-constructor-range-optimization

Only IN() predicates are used, not NOT IN().
On the left side of the IN() predicate, the row constructor contains only column references.
On the right side of the IN() predicate, row constructors contain only runtime constants, which are either literals or local column references that are bound to constants during execution.
On the right side of the IN() predicate, there is more than one row constructor.

https://dev.mysql.com/doc/refman/8.0/en/multiple-column-indexes.html 文档

MySQL can use multiple-column indexes for queries that test all the columns in the index, or queries that test just the first column, the first two columns, the first three columns, and so on. If you specify the columns in the right order in the index definition, a single composite index can speed up several kinds of queries on the same table.

(c_type, cat_id) 是索引的一部分，所以建的索引不能用，慢
where 里面的 col 都不能用索引，慢

@NewConn 不好意思我是妹子。

WITH E AS (
SELECT ID
FROM A
WHERE type = 2
AND DELETE_FLAG = 0
AND uid = 41
UNION
SELECT a.ID
FROM A a, B b, A c
WHERE a.type = 3
AND a.DELETE_FLAG = 0
AND a.uid = 41
AND a.ID = b.ID
AND b.parent_id = c.ID
)

这里面为什么不能先把 a.type in (2,3) and a.delete_flag =0 and a.uid = 41 先选择出来然后再别的操作？这一句的 selectivity 有多少？有多少符合条件的？

ALTER TABLE operations are processed using one of the following algorithms:

COPY: Operations are performed on a copy of the original table, and table data is copied from the original table to the new table row by row. Concurrent DML is not permitted.
不可以并发

INPLACE: Operations avoid copying table data but may rebuild the table in place. An exclusive metadata lock on the table may be taken briefly during preparation and execution phases of the operation. Typically, concurrent DML is supported.
可能加锁，一般可以并发

INSTANT: Operations only modify metadata in the data dictionary. No exclusive metadata locks are taken on the table during preparation and execution, and table data is unaffected, making operations instantaneous. Concurrent DML is permitted. (Introduced in MySQL 8.0.12)
允许并发

https://dev.mysql.com/doc/refman/8.0/en/alter-table.html

@yukiloh 我是学生。工作的时候碰到问题去搜索，其实就是把这个时间转嫁到实际操作的时候学习了。这个本科课程内容也没多少，认真一下，只了解概念，两三周绝对够了。

发现一个 http://sqlfiddle.com/ 就是广告有点明显。。。错误提示比 DB Fiddle 详细。

@gainsurier 有在招聘的。

学习一下 CMU 的数据库课程吧，两个部分，本科的主要是基本概念，研究生的讲前沿研究和思考一些问题。https://15445.courses.cs.cmu.edu/fall2019/ https://15721.courses.cs.cmu.edu/spring2020/
我基本看完了 15-445，收获很大，至少知道有问题应该去找什么样的资料。如果不是急着工作，不建议看动物书，非常应用，并且每个数据库都不一样。先打好基础，多练习一下，在 v 站看别人发的问题学习一下，再看针对某一个数据库的也不迟。

添加 try except，抓 mysql.connector.errors.DatabaseError 错误

@kanepan19 这样的啊，学习了。谢谢回复！

@hauzi `范围查询一般都不走索引的`，这是从经验来的嘛？我看文档 https://dev.mysql.com/doc/refman/5.6/en/range-optimization.html 说的是 indexed key 都会做优化？

不一定需要 `FORCE INDEX`，尝试一下 `USE INDEX`。https://dev.mysql.com/doc/refman/8.0/en/index-hints.html

@zhou451971886 为什么要关闭这个优化？

@XanderChen 付费的也行。叫什么名字？

up ！