Hasura GraphQL Engine and SQL Server
github.com
Hasura GraphQL Engine and SQL Server
1–10 of 85 posts
Re: Hasura GraphQL Engine and SQL Server
#2(Vamshi from Hasura)
We've been working on SQL server native support and we're happy to announce support for read-only GraphQL cases with new or existing SQL Servers.
Next up is adding support for stored procedures, mutations, Hasura event triggers [1] and more!
[1]: https://hasura.io/docs/latest/graphql/core/event-triggers/in...
Re: Hasura GraphQL Engine and SQL Server
#3Happy customer on Postgres who just signed a large contract that needs SQL support.
Love the product and the team, keep up the great work.
Out of curiosity is support for multiple roles in the works?
Re: Hasura GraphQL Engine and SQL Server
#4The space is def interesting and the product probably lowers the barrier to entry for development. My main question will be why would you use it against plain/open-source PostgreSQL RBAC + GraphQL server or something like https://www.graphile.org/postgraphile/ ?
Re: Hasura GraphQL Engine and SQL Server
#5How about build-in authorization for Postgesql?
Re: Hasura GraphQL Engine and SQL Server
#6Happy customer on Postgres who just signed a large contract that needs SQL support. Love the product and the team, keep up the great work. Out of curiosity is support for multiple roles in the works?
Yes! We announced experimental support earlier and here's the new spec we're implementing that will support all databases and remote schemas too.
https://github.com/hasura/graphql-engine/issues/6991
General support for inherited roles is one of the things I'm most excited about because it makes a bunch of hard things around reusing and composition so easy.
This improvement plays really well along with things like "role-based schemas" so that GraphQL clients have access to just the exact GraphQL schema they should be able to access - which is in turn composed by putting multiple scopes together into one role.
Also interesting is how well this could play with other innovations on the GraphQL client ecosystem like gqless[1] and graphql-zeus[2] because now there's a typesafe and secure SDK for really smooth developer experience on the client side.
[1]: https://github.com/gqless/gqless [2]: https://github.com/graphql-editor/graphql-zeus
Re: Hasura GraphQL Engine and SQL Server
#7How about build-in authorization for Postgesql?
That already works! :)
Postgres was the first database we added support for!
https://hasura.io/docs/2.0/graphql/core/databases/postgres/i...
Re: Hasura GraphQL Engine and SQL Server
#8How about build-in authorization for Postgesql?
I think hasura supports this? Or do you mean native postgres users with postgres RLS? The hasura team has explained somewhere why they don‘t want to do this. IIRC it had something to do with caching and/or subscriptions.
Re: Hasura GraphQL Engine and SQL Server
#9The space is def interesting and the product probably lowers the barrier to entry for development. My main question will be why would you use it against plain/open-source PostgreSQL RBAC + GraphQL server or something like https://www.graphile.org/postgraphile/ ?
I considered Postgraphile for our company but picked Hasura. While PG has better extensibility, Hasura has a more polished unboxing experience and way lower learning curve. Time to market is crucial for us as we needed to prove our MVP.
Re: Hasura GraphQL Engine and SQL Server
#10The space is def interesting and the product probably lowers the barrier to entry for development. My main question will be why would you use it against plain/open-source PostgreSQL RBAC + GraphQL server or something like https://www.graphile.org/postgraphile/ ?
In general, and for SQL Server specifically, our intent was to add great support (low footprint, works out of the box) in a way that doesn't need DDL or write access to the underlying database.
This becomes super useful for folks building new applications or new features against existing SQL Server systems (which is a rather large ecosystem beyond just the database, since so many products use SQL Server underneath too!)