no such column exists for PostgreSQL db in Hasura (Graphql) console when adding column via DBeaver - postgresql

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?

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."

you have to update the metadata, from the console it would be:
hasura metadata reload

Related

Metadata Does Not seem to update correctly

Our company uses Hasura Cloud with a React js front end with gQlApollo.
I recently added a new column "myString" to type "myType" in our database and was able to successfully update our Hasura Cloud instance by resetting the Metadata within settings.
I know this worked because when I use the API on Hasura Cloud I am able to successfully return the new column and its value.
I also see that the graphQl Engine metadata is green as shown here status of graphQl engine metadata
The problem is when I try to query this new column locally it seems that this metadata is not successfully being updated there. I have no local hasura core so the suggestion online to preform a hasura metadata clear does not apply to me.
I have tried:
resetting my browser history
run hasura init and reset the meta data after which did not fix my problem
Any idea how I can accomplish resetting the metadata locally?
Solved my issue! It was because I had not changed the permissions for the newly created column in cloud.hasura.io. Now that I have added that it works without needing to reset the Metadata at all.

'type_cast_required' is undefined messagge in Postgresql

I have created a databse in Postgresql. I am trying to use pgadmin to add new record to a table, however I am getting a messagge: 'type_cast_required' is undefined.
Screen shot:
I have looked across the web for what this message means however I have not found anything.
Any thoughts?
pgAdmin bug. This should have been fixed as of version pgAdmin 4.22. For more details see this issue. You will need a Postgres community account to view issue.

Read only view in DataGrip

I have a local MongoDB instance that I am connecting to in DataGrip. When I open a collection and it loads in DataGrip, I try to edit a value in one of the fields and I am greeted with This view is read-only
I had a look at the following SO question but I can't find the auto commit checkbox so I can't try it. If someone can maybe point out where that would be in DataGrip for MongoDB?
Thanks
At the moment you can't edit values. But it's coming soon.
Follow the issues:
DBE-9645
DBE-9375

RubyMine connect to database

I'm using latest version of RubyMine and when I try to connect to my docker container database, I see the database, but not any of the tables etc.
If I use an external program such as Psequal using the exact same credentials, it works fine so I know I'm using the correct credentials, IP address etc.
I have raised an issue with JetBrains, but can anyone shed any light on why I'm not seeing the tables?
Figured it out. in the data source properties window (either when creating the data source or by right clicking->properties)
Go to options and tick the box "Introspect using JDBC meta data"
Click apply and you see a downloading progress bar
Once completed, the tables and everything else is viewable.

Tablespace error upon creating table

I'm facing this weird issue.
When I want to create a table, it says Tablespace-xxx exist.
But when I want to remove that Tablespace-xxx, it says it is not exist.
I'm using mysql in google cloud, second generation.
Thanks in advance!
Very interesting. Please email the name of your project and database instance to cloud-sql#google.com (along with a link to this post) and we can follow up there.