GeezerVison

TablesNamesFinder threw UnsupportedOperationException for every SET statement except the SQL Server ON/OFF options. A subquery in a value, as in SET @a = (SELECT MAX(id) FROM t1), was never reached. A MySQL trigger whose body is or contains SET, such as CREATE TRIGGER trg BEFORE INSERT ON t1 FOR EACH ROW SET NEW.a = …, failed the same way, although its table is known. The trigger examples in the MySQL manual use this form.

The finder now visits the value expressions of each assignment, as it does for the values of UPDATE … SET. A subquery in a SET value reports its tables, and other SET statements report none. The deliberate UnsupportedOperationException for other statements, such as CREATE SYNONYM, is unchanged.

Public method signatures are retained.

Syntax reference: MySQL 8.4 SET for variables, trigger syntax.

Validation:

• TablesNamesFinderTest adds a SET with a subquery, a SET without tables and two MySQL triggers, one with a SET body and one with SET inside BEGIN … END. Both new tests fail on master c84ad0ebc with UnsupportedOperationException: Finding tables from SetStatement is not supported.
• MySQL 8.4.11 accepts the two triggers and the SET statement.
• Java 17 Gradle check: 12,264 tests, 0 failures, 25 skipped. Grammar ambiguity, formatting (Spotless ratchet against upstream/master), Checkstyle, PMD, SpotBugs and JaCoCo pass. The grammar is unchanged.

AI assistance: prepared with Claude Code.