3781823 - Altering an existing database column with a Groovy script

An item type attribute that was originally modelled with a limited column length, for example nvarchar(255), continues to use that same length in the database after its column type is changed to HYBRIS.LONG_STRING and update running system is executed. The wider column definition is not applied. As a result, values longer than the original limit cannot be persisted or imported, and the database rejects them because the underlying column has not actually been widened.

It can be observed that the data model reflects the new column type, while the physical column in the database still reports its original type and length.

SAP Commerce Cloud

SAP Commerce Cloud, HYBRIS.LONG_STRING, column type, columntype, items.xml, nvarchar(255), NVARCHAR(MAX), ALTER TABLE, ALTER COLUMN, database column, column length, widen column, Update Running System, System Update, existing column not altered, HAC, Groovy console, Groovy script, Groovy, script, initialization, reinitialization, tenant data source, INFORMATION_SCHEMA, SQL Server, schema change, data model , KBA , CEC-SCC-PLA-PL , Platform , Problem