migrator: addColumnOptionsSpec text-default DEFAULT clause still fails on MySQL (follow-up to #2661)

[bpamiri]

Describe the bug

#2661 patched the addColumnOptionsSpec DEFAULT-clause substring assertions for CockroachDB and Postgres, but the same spec still fails on MySQL across all three actively-tested engines (Lucee 6, Lucee 7, BoxLang).

Failing spec

wheels.migrator.addColumnOptionsSpec :: text with a real default (non-empty) still emits DEFAULT

Assertion message:

The needle [DEFAULT] was not found in [ NULL]

The emitted SQL contains NULL instead of DEFAULT '<value>' on MySQL. Either the migrator emits a different DEFAULT clause for MySQL text columns, or the assertion's substring check needs the same MySQL-aware branch that #2661 added for CockroachDB / Postgres.

Reproduction

tools/test-matrix.sh lucee7 mysql
# or
curl 'http://localhost:60007/wheels/core/tests?db=mysql&format=json&directory=tests.specs.migrator'

Evidence

Compat-matrix run 25978222394 (develop, 2026-05-17):

• lucee6/mysql: 1 fail (this spec)
• lucee7/mysql: 1 fail (this spec)
• boxlang/mysql: 2 fail (this spec + a separate boxlang-only locking issue)

Expected behavior

Spec passes on MySQL with the same fix shape used in #2661 for CockroachDB and Postgres.

Related

• Parent: Core test suite has high failure/error rate on BoxLang (35 failures, 125 errors, 3526 passing) #2649 (BoxLang compat rollup)
• Predecessor: migrator: addColumnOptionsSpec DEFAULT-clause substring assertions fail on CockroachDB + Postgres #2661 (closed, partial fix)

[wheels-bot]

Wheels Bot — Triage

Classified as bug.

Suspected layer

migrator — test spec lives at vendor/wheels/tests/specs/migrator/addColumnOptionsSpec.cfc, adapter behavior in vendor/wheels/databaseAdapters/MySQL/MySQLMigrator.cfc.

Fix sketch

The MySQL adapter intentionally suppresses the DEFAULT clause for text, mediumtext, longtext, and float columns — see MySQLMigrator.cfc:70-73 (optionsIncludeDefault returns false for those types because MySQL forbids DEFAULT on TEXT/BLOB columns pre-8.0.13). This is intentional adapter behavior, parallel to how Postgres/CockroachDB emit DEFAULT '' for empty strings. The spec at addColumnOptionsSpec.cfc:89-93 ("text with a real default (non-empty) still emits DEFAULT") doesn't account for it. Mirror the isPostgresFamily pattern already in beforeAll (line 39): add variables.isMySQLFamily = (name == "MySQL") and split the text-with-real-default assertion so MySQL asserts notToInclude("DEFAULT") while other Abstract-based adapters still assert toInclude("DEFAULT") + toInclude("'long body'"). Pure test edit, same shape as #2661.

Confidence: medium

Fix shape is mechanical and the adapter root cause is identified, but the migrator subsystem auto-downgrade rule applies; also worth confirming whether the char and string text-default specs need parallel MySQL carve-outs.

<!-- wheels-bot:triage:2742 -->
<!-- wheels-bot:triage-class:bug -->
<!-- wheels-bot:triage-confidence:medium -->

[wheels-bot]

Wheels Bot — Fix proposed

Draft PR: #2748

Spec: vendor/wheels/tests/specs/migrator/addColumnOptionsSpec.cfc — adapter-aware MySQL carve-out added (mirrors the existing isPostgresFamily pattern)
Implementation: vendor/wheels/databaseAdapters/MySQL/MySQLMigrator.cfc — doc-comment expanded to document the contract and rationale

Same shape as #2669 (which closed parent #2661). Pure test + doc-comment change; no production behavior delta. Full local SQLite core-test run shows 0 failures both before and after; CI compat-matrix will validate the MySQL legs.

A human review is required before merge. Reviewer A and Reviewer B will weigh in shortly. Doc updates (MDX guides, .ai/wheels/, CLAUDE.md) are handled separately by bot-update-docs.yml.