Schema update

[ariga-bot]

Renamed the column 'user_name' to 'username' in the 'users' table to demonstrate a backward-incompatible change.

[github-actions]

atlas migrate lint on dirs/ecommerce/migrations

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

[github-actions]

Caution

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

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

Suggested change

	-- Modify "users" table
	ALTER TABLE `users` DROP COLUMN `user_name`, ADD COLUMN `username` varchar(255) NOT NULL COMMENT "The username of the user, must be unique", ADD UNIQUE INDEX `username` (`username`);
	-- atlas:txtar
	-- checks/destructive.sql --
	-- atlas:assert DS103
	SELECT NOT EXISTS (SELECT 1 FROM `users` WHERE `user_name` IS NOT NULL) AS `is_empty`;
	-- migration.sql --
	-- Modify "users" table
	ALTER TABLE `users` DROP COLUMN `user_name`, ADD COLUMN `username` varchar(255) NOT NULL COMMENT "The username of the user, must be unique", ADD UNIQUE INDEX `username` (`username`);

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