# `sp_alert_text` (procedure)

> 根据模块sId删除模块（包含子模块）


- **Type:** PROCEDURE
- **Deterministic:** NO
- **SQL data access:** CONTAINS SQL

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | OUT | `sReturn` | `varchar(4000)` |
| 2 | OUT | `sCode` | `int` |

## Body

_Body is not pre-cached. To inspect: `mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURE `sp_alert_text`'`._

## Narrative

**Business context:** DBA schema-migration helper, large-column variant. Catalog header (`根据模块sId删除模块（包含子模块）`) is mis-copied — the actual body widens every nullable column whose `CHARACTER_OCTET_LENGTH > 1000` in the `xlyweberp` schema to `TEXT DEFAULT NULL`, to avoid row-size overflow when many wide varchars coexist on one table.

**What it does:** Counts `information_schema.COLUMNS` matching `table_schema='xlyweberp' AND CHARACTER_OCTET_LENGTH > 1000 AND IS_NULLABLE='YES'`. For each match, cursors through and runs `ALTER TABLE <tbl> CHANGE <col> <col> TEXT DEFAULT NULL` via dynamic SQL. Wraps the loop in a transaction with a savepoint and SQLEXCEPTION handler that rolls back and surfaces a localized error via `SP_Sis_GetConst('SQLEXCEPTION',...)`.

**Invocation:** Status: appears orphaned. Lives in `xly-src/script/大表的过程/sp_alert_text.sql` (DBA "big-table" helpers bundle), not bound to any `gdsmodule` hook, form, or other routine. Run manually by a DBA during schema-widening passes. Candidate for maintainer audit if found in a runtime call path.
