UpgradeOptions::$allowTruncate should still apply other field changes #40

New issue

Open

opened 2026-09-05 10:37:10 +02:00 by c.fahner · 0 comments

c.fahner commented

2026-09-05 10:37:10 +02:00

Owner

Currently the UpgradeOptions::$allowTruncate does not specify what should happen to the other field schema changes after the truncation is ignored. It should be explicitly documented that the modification should still go through, except for the truncation.

Edit: the documentation should also be changed to not emit warnings about potential data loss, as the intended use case does not require it (see #40).

Currently the `UpgradeOptions::$allowTruncate` does not specify what should happen to the other field schema changes after the truncation is ignored. It should be explicitly documented that the modification should still go through, except for the truncation. Edit: the documentation should also be changed to not emit warnings about potential data loss, as the intended use case does not require it (see #40).

c.fahner added this to the v0.2 milestone

2026-09-05 10:37:10 +02:00

c.fahner added the

Kind/Documentation

label

2026-09-05 10:37:10 +02:00

c.fahner referenced this issue from slendium/ocd-conformance-tests

2026-09-05 11:57:58 +02:00

Test schema upgrade that ignores truncation #4

c.fahner referenced this issue

2026-09-06 08:56:50 +02:00

Don't distinguish between truncate and drop during schema upgrades #41