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

Deleting CRUD auto screens can fail on Postgres #6326

Closed
melohagan opened this issue Jun 15, 2022 Discussed in #6325 · 2 comments
Closed

Deleting CRUD auto screens can fail on Postgres #6326

melohagan opened this issue Jun 15, 2022 Discussed in #6325 · 2 comments
Labels
bug Something isn't working stale

Comments

@melohagan
Copy link
Collaborator

melohagan commented Jun 15, 2022

Discussed in #6325

Originally posted by NicolasFabre81 June 15, 2022

  1. From a postgreSQL table named base_article, I created the auto CRUD screens.
  2. Then I deleted them.
  3. Now if I re-generate the CRUD screens, the :id screen is called /base_article-2/:id instead of /base_article/:id
  4. If i try to rename it, I get an error saying screen /base_article/:id already exists.

So I think that the deleting did not work properly, and some system objects with the name /base_article/:id remain somewhere...

I believe I've seen this happen with the Internal DB as well.

@melohagan melohagan added bug Something isn't working sev3 labels Jun 15, 2022
@stale
Copy link

stale bot commented Aug 16, 2022

This issue has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the stale label Aug 16, 2022
@melohagan
Copy link
Collaborator Author

I haven't seen this in a while. I believe work had been done to improve deleting of the screens since this issue was raised.
Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

1 participant