Two same named sql table models should throw a migration error

say I've a model A:

A sql=same_name
  Id UUID
  myText Text

and a model B with the same sql name as A

B sql=same_name
  Id UUID

this will first tell me to:

ALTER TABLE "same_name" ADD COLUMN "my_text" VARCHAR NOT NULL;

and then once I do that, it will tell me to:

ALTER TABLE "same_name" DROP "my_text";

which is a cute little dance,
but in this case i'd expect persistent to tell me we shouldn't doubly map a model to the same sql backend.

The issue provides no file or test entry point; start by reproducing the two models with the shared SQL name and trace the migration-generation path. Done means the migration process reports a duplicate model-to-table mapping error instead of proposing alternating ADD and DROP statements.