Rich-text description columns on webinar_type

FeatureInitializerService
Ya
24 Agosti 2026, 21:19 UTC
Mwandishi
Kamo
Ahadi ya
e9cfef0

Mirrors the shared-lib entity change. Two things the table needs before MediaService maps them. The description column has to be unbounded: it holds a Lexical editor state now, and a varchar ceiling would not truncate, it would reject the whole save with a value-too-long error inside a @Transactional update that then rolls back and leaves nothing to explain it. Check-then-alter rather than a bare ALTER, because the entity has declared TEXT since the table was created — so on every database this platform runs the probe short-circuits and no DDL is issued at all, which matters on YugabyteDB where an unconditional ALTER COLUMN ... TYPE would log a failure on every startup. description_plain is new: the plain-text mirror, nullable with no default, because null is the honest value for every row that predates the editor and is what tells a reader to fall back to description. Verified against the live cluster: description was already text, and both columns are present after the run.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei