Metadata Does Not seem to update correctly - metadata

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.

Related

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

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

Security Exception when loading the site after Kentico upgrade from v9 to v10

After upgrading the existing v9 site to Kentico 10 I'm getting a security exception error when loading the site. The CMS admin however loads fine. I already added the FULL trust setting in web.config but it did not work. Any idea?
Problem, based on part that I can see and exception type would be in new SQL parser which was added in one of the hotfixes for v9 and thus it is part of v10.
You seem to be using one of the properties in a web part and than passing incomplete query via ##WHERE## macro. If a where condition is like {%CurrentDocument.DocumentID%} it is not a valid WHERE and whole property has to be complete SQL statement on its own, so it could be like DocumentID = {%CurrentDocument.DocumentID%}.
You can find a bit more in this thread:
https://devnet.kentico.com/questions/invalid-sql-query-error-on-a-page
Try load the template in the Admin UI pages application, then check the event log application, you should see the detail information about the SQL error. Most likely you have a SQL call that is trying to get some data from a column that's no longer there (through upgrade).

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.

Invalid Argument error is shown on Google Cloud Storage files

I am using the web interface, I am trying to make public files that were uploaded and each time I click the checkbox I immediately get the error "Invalid Argument" and the box unchecks.
This also happens while trying to uncheck files already uploaded and public.
I'm not certain if something happened to my account or if this is a service problem for the site but we're in a major jame because of this. Essentially Cloud storage is unusable at this stage.
There was an issue with the web user interface and the JSON interface affecting setting ACLs on objects. That problem has been resolved, and all interfaces should be working correctly now.

EF Code First not working on deploy hosting

I've an application using MVC and Code First for persistence.
Everything works fine in my development, but when I'm uploading to server, it doesnt work.
In any place i try to create a database, but it keeps me returning the following error: CREATE DATABASE permission denied in database 'master'.
The only thing that i do is override the OnModelCreating method just to map my app.
Anyone has this error?
Thanks
For a tutorial series that shows how to publish your Code First database and prevent Code First from trying to re-create the database in production, see
http://www.asp.net/mvc/tutorials/deployment-to-a-hosting-provider
The third tutorial in the series shows how to set up the Web.config file. The second shows how to deploy if you are using SQL Server Compact, the tenth shows how to deploy to full SQL Server.
You'll need to publish your database out to your hosting provider. Visual Studio has an easy way of doing this. In the server explorer tab, you can navigate to your database, right click and choose publish to provider. By doing this, you will not only export the scheme of your database, but you can also export out all data, stored procs, views etc.
You will need to adjust your code so that you are no longer trying to create a database on code run. Typically this approach is used for development, and you are no longer in development if you're moving to a hosting company. The changes may be in your global.asax, the dbcontext of your solution and any other place where you modified it to create the scheme for the database.
Hope this helps you some, and good luck on your project.