Hasura lets you connect postgres views to your graph, so if you really wanted to you can probably keep your db schema the same but make a view that reflects however you want to represent your graphql schema, and just expose the view to the end user. The Hasura GraphQL Engine is a blazing-fast GraphQL server that gives you instant, realtime GraphQL APIs over Azure SQL, with webhook triggers on database events, and remote schemas for business logic. You can also use row and column-level permissions to hide any fields you don't want exposed to the user. The schema generated by Hasura is pretty tightly coupled to your database schema, but you can rename/alias anything you want, including relationships between models. When setting up an action you create a new return type which can be connected to your graph however you like via hasura's relations. I am specialized in designing databases in Firebase Firestore. I can model your data for you or you can bring your own data and I will get you a graphql api. Hasura is a instance graphql backend for you sql database. They can utilize your Hasura api themselves for fetching data (likely with different permissions than a regular user) or can use any other means of interacting with your postgres db depending on what language/libraries you use to write your action handlers. I will build you any backend database in Hasura. It's common to run these as lambda functions, but they could be hosted however you like. This is just a webhook + query/mutation type that becomes part of your Hasura api.

The downside is, that there are now two different article types, it might make sense to hide the regular articles query then. This solution is useful if you want to vary the amount of time, that you want to query for. Since Hasura just sits in front of postgres, you can query the data in your db from your remote api however you like (dataloaders, knex.js, or whatever). Now you can again query this view and use a filter query on the extra field. So this could be any graphql server running any code you want. First, you have remote schemas, which is just an external api (graphql or REST) that you can integrate into your hasura api. Hasura gives you a couple options for adding additional resolvers outside of the schema it generates for you. I'll try my best to answer these questions. It shines in cases where you want a simple GraphQL backend quickly. Hasura doesn't do authentication out of the box. You can choose either to write a plpgsql function, or you have to spin up an external lambda to do it via Actions. Handling custom logic is a bit fiddly right now. I also like that it's built on top of Postgres, so if you ever had to migrate away from Hasura, you're not totally hosed. Again, something that Django doesn't do really well. I really like the way you set up row-level permissions in Hasura. The admin interface for configuring tables and stuff is very handy. Subscriptions out of the box! Having done Django for a while, where real-time pubsub-style websocket APIs are a major pain to set up, the fact that I could get subscriptions for free is mind-blowing. I once spun up and configured a Hasura instance in 20 minutes, while on a train. Spinning up a Hasura backend is really quick. I do have experience building real production webservers using Django. Navigate to, and create a new Hasura Cloud account. WHERE Article.publishedDate < Category.Disclaimer: I've only used it in side-projects, so not 'real' production usecases with real traffic. Try it out Step 1: Create an account on Hasura Cloud and create a new Hasura Project.

INNER JOIN Category ON Article.categoryId = Category.categoryId In pseudo-SQL, I would do something similar to this : SELECT ntent, Category.name

What I am trying to achieve, in English, is the following : get the articles that were published in the first 3 days following the creation of their related category. I am having troubles implementing a basic query. I recently started using GraphQL through a Hasura layer on top of a PostgreSQL DB.

Hasura ilike