-
Notifications
You must be signed in to change notification settings - Fork 148
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
Admin 'looses' table schema #133
Comments
I have exactly the same issue. My setup: Once the error appears, only restarting the container would momentarily fix the issue. Could it be that multiple schemas are poorly supported? I leave some details that maybe helps to identify the issue. Response: |
I've tables in 3 different schemas in PostgreSQL database (not in public).
After restart MotorAdmin sees all the tables/resources, and I can work with them, but after few operations (2-4) it seems to somehow 'loose' tables schema (I presume), and tries to access the the tables without it, what results in failure.
Updating the table, that worked few seconds before results in
PG::UndefinedTable: ERROR: relation "metadata_entity_property" does not exist LINE 1: UPDATE "metadata_entity_property" SET "options" = '{}', "in_... ^
After this error, I can't see any resources on main page. Restarting container fixes this again for a short while.
Example logs:
I'm using:
Motor Admin v0.4.21 in Docker
PostgreSQL server 16.2 (Debian 16.2-1.pgdg120+2) in Docker
The text was updated successfully, but these errors were encountered: