I just tested modifying a table in my PostgreSQL db through DBeaver and it seems to have broken the db when looking at the data from the Hasura (Graphql) console. I simply added a column from Dbeaver. In Hasura I get an error "no such column exists". Anyone have any idea why or how I can fix this?
Asked
Active
Viewed 2,093 times
6
-
Could you show us your SQL statements that altered that table? And why do you think you broke the database? Are there any error messages in your PostgreSQL server log? And Yes, it looks like Hasura is looking for a column that doesn't exist (anymore). You could create that column, if you know what column it is. – Frank Heikens Jan 10 '21 at 13:39
-
Thanks @FrankHeikens. It was a conflict in the meta data in the console. – virtualbis Jan 11 '21 at 00:32
2 Answers
10
Hasura support helped me pinpoint it to the metadata stored in the Graphql console. Hope this helps someone else save a little time.
"If you make DDL changes to your database from outside Hasura, you must manually reload the Hasura metadata so that Hasura knows that something has changed and it adapts to those changes accordingly.You can reload the metadata by clicking on the settings icon on the top right in console."
virtualbis
- 397
- 1
- 14
-
1And don't forget to add permission for new colunns for roles other than "admin" – Alex Yu Jan 14 '21 at 05:33
-
3
2
you have to update the metadata, from the console it would be:
hasura metadata reload
Andmat7
- 196
- 2
- 4