D/rebase

[giautm]

No description provided.

[datdao]

atlas migrate lint on sqlite-wrong-sum

Status	Step	Result
	1 new migration file detected	atlas.sum
	ERD and visual diff generated	View Visualization
	Migration Integrity Check File atlas.sum is invalid	checksum mismatch
Read the full linting report on Atlas Cloud

[datdao]

atlas migrate lint on migrations

Status	Step	Result
	No migration files detected
	ERD and visual diff generated	View Visualization
	No issues found	View Report
Read the full linting report on Atlas Cloud

[datdao]

Atlas detected changes to the desired schema

Migration Plan (View on Atlas Cloud)

-- Create "t1" table
CREATE TABLE "public"."t1" (
  "c1" integer NOT NULL,
  "c2" integer NOT NULL
);
-- Set comment to table: "t1"
COMMENT ON TABLE "public"."t1" IS '881a0f7a305fed2b7139159de085fdd589361a94';

Atlas lint results

Status	Step	Result
	Detect schema changes	2 new statements detected
	No issues found

---

📝 Steps to edit this migration plan

1. Run the following command to pull the generated plan to your local workstation:

atlas schema plan pull --url "atlas://circleci-schema-test/plans/881a0f7a305fed2b7139159de085fdd589361a94" > 881a0f7a305fed2b7139159de085fdd589361a94.plan.hcl

2. Open 881a0f7a305fed2b7139159de085fdd589361a94 in your editor and modify it as needed. Note that the result of the plan should align
the database with the desired state. Otherwise, Atlas will report a schema drift.

3. Push the updated plan to the registry using the following command:

atlas schema plan push --pending --file 881a0f7a305fed2b7139159de085fdd589361a94.plan.hcl

[datdao]

Atlas detected changes to the desired schema

Migration Plan (View on Atlas Cloud)

-- Create "t1" table
CREATE TABLE "public"."t1" (
  "c1" integer NOT NULL,
  "c2" integer NOT NULL
);
-- Set comment to table: "t1"
COMMENT ON TABLE "public"."t1" IS '06247056566b1fa7bfbe1ff8acb9dbac3bff43ac';

Atlas lint results

Status	Step	Result
	Detect schema changes	2 new statements detected
	No issues found

---

📝 Steps to edit this migration plan

1. Run the following command to pull the generated plan to your local workstation:

atlas schema plan pull --url "atlas://circleci-schema-test/plans/06247056566b1fa7bfbe1ff8acb9dbac3bff43ac" > 06247056566b1fa7bfbe1ff8acb9dbac3bff43ac.plan.hcl

2. Open 06247056566b1fa7bfbe1ff8acb9dbac3bff43ac in your editor and modify it as needed. Note that the result of the plan should align
the database with the desired state. Otherwise, Atlas will report a schema drift.

3. Push the updated plan to the registry using the following command:

atlas schema plan push --pending --file 06247056566b1fa7bfbe1ff8acb9dbac3bff43ac.plan.hcl

[datdao]

Atlas detected changes to the desired schema

Migration Plan (View on Atlas Cloud)

-- Create "t1" table
CREATE TABLE "public"."t1" (
  "c1" integer NOT NULL,
  "c2" integer NOT NULL
);
-- Set comment to table: "t1"
COMMENT ON TABLE "public"."t1" IS '466b97f12abf228e62453f0d7c2eca5c56c11ecb';

Atlas lint results

Status	Step	Result
	Detect schema changes	2 new statements detected
	No issues found

---

📝 Steps to edit this migration plan

1. Run the following command to pull the generated plan to your local workstation:

atlas schema plan pull --url "atlas://circleci-schema-test/plans/466b97f12abf228e62453f0d7c2eca5c56c11ecb" > 466b97f12abf228e62453f0d7c2eca5c56c11ecb.plan.hcl

2. Open 466b97f12abf228e62453f0d7c2eca5c56c11ecb in your editor and modify it as needed. Note that the result of the plan should align
the database with the desired state. Otherwise, Atlas will report a schema drift.

3. Push the updated plan to the registry using the following command:

atlas schema plan push --pending --file 466b97f12abf228e62453f0d7c2eca5c56c11ecb.plan.hcl