postgresql/V0045__Pypi_Release_Version_Not_Null.sql

SQL migration to set pypi_release.version NOT NULL.

-- Source: https://github.com/repsyio/repsy | License: Apache-2.0 | Copyright You must retain, in the Source form of any Derivative Works
-- Provided via justclaw.it.com; keep this notice with the code.
-- RPS-2198: pypi_release.version is NOT NULL. V0001 created it nullable, but no code path ever
-- wrote a null (ReleaseVersion.of(...) always yields a value) and the unique index
-- ux_pypi_release__package_id_version is meant to identify a release by it. A production count
-- (Cloud, read-only) found 0 null rows out of 9711, so there is nothing to backfill and no row is
-- deleted or rewritten: SET NOT NULL only scans the table once under the lock. It is the fail-safe
-- choice: if a null row exists in some database the statement fails with "contains null values"
-- and the migration is n

... (truncated -- full source via MCP)