Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anaylze schema report should issue a warning on tables without primary keys #1388

Open
ssherwood opened this issue Mar 27, 2024 · 0 comments
Labels
triage Needs to be triaged

Comments

@ssherwood
Copy link

ssherwood commented Mar 27, 2024

In general, we recommend that all tables have primary keys in YugabyteDB.

It would be useful if the analyze-schema report would highlight any tables in the migration that do not have a primary key so it can be evaluated and triaged prior to migration.

e.g.

create table baz(
  id int default null,
  created_on datetime default null,
  created_by varchar(40)
)
@github-actions github-actions bot added the triage Needs to be triaged label Mar 27, 2024
@ssherwood ssherwood changed the title Anaylze Schema should issue a warning on tables without primary keys Anaylze schema report should issue a warning on tables without primary keys Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs to be triaged
Projects
None yet
Development

No branches or pull requests

1 participant