Schema update

[ariga-bot]

Renamed column in table to , causing potential backward-incompatibility with applications referencing the old column name.

[github-actions]

atlas migrate lint on dirs/ecommerce/migrations

Status	Step	Result
	1 new migration file detected	20241222130915.sql
	ERD and visual diff generated	View Visualization
	Analyze 20241222130915.sql 2 reports were found in analysis	Destructive changes detected Dropping non-virtual column "email" (DS103) Data dependent changes detected Adding a non-nullable "varchar" column "email_address" on table "users" without a default value implicitly sets existing rows with "" (MY101) Adding a unique index "user_name_email_address" on table "users" might fail in case column "user_name" contains duplicate entries (MF101)
Read the full linting report on Atlas Cloud

[github-actions]

Caution

destructive changes detected
Dropping non-virtual column "email" DS103

Add a pre-migration check to ensure column "email" is NULL before dropping it

Suggested change

	-- Modify "users" table
	ALTER TABLE `users` DROP CHECK `users_chk_1`, ADD CONSTRAINT `users_chk_1` CHECK (regexp_like(`email_address`,_utf8mb4'^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+.[a-zA-Z]{2,}$')), DROP COLUMN `email`, ADD COLUMN `email_address` varchar(255) NOT NULL, DROP INDEX `user_name_email`, ADD UNIQUE INDEX `email_address` (`email_address`), ADD UNIQUE INDEX `user_name_email_address` (`user_name`, `email_address`);
	-- atlas:txtar
	-- checks/destructive.sql --
	-- atlas:assert DS103
	SELECT NOT EXISTS (SELECT 1 FROM `users` WHERE `email` IS NOT NULL) AS `is_empty`;
	-- migration.sql --
	-- Modify "users" table
	ALTER TABLE `users` DROP CHECK `users_chk_1`, ADD CONSTRAINT `users_chk_1` CHECK (regexp_like(`email_address`,_utf8mb4'^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+.[a-zA-Z]{2,}$')), DROP COLUMN `email`, ADD COLUMN `email_address` varchar(255) NOT NULL, DROP INDEX `user_name_email`, ADD UNIQUE INDEX `email_address` (`email_address`), ADD UNIQUE INDEX `user_name_email_address` (`user_name`, `email_address`);

Ensure to run atlas migrate hash --dir "file://dirs/ecommerce/migrations" after applying the suggested changes.