-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: document support for different postgres flavours #411
Comments
CockroachDB hasn't supported user defined schema
|
I could imagine scenarios where as a start-up scales they might shift to CockroachDB from Postgres. From a read and most of a write point of view would it not remain compatible with GraphQL? How frequently are user defined schema changes required in standard Hasura + Postgres operation? The other feature that would disappear is the live subscription capability but that is an optional extra and Hasura has strong value even without it. |
Thanks for reporting this @duyleekun. @Smerity Hasura stores all the metadata on a separate schema called Looks like this is a planned feature on CockroachDB. Should land soon. See cockroachdb/cockroach#26443 and cockroachdb/cockroach#30916 |
Hey Guys - is it possible to do the creation of the |
@Disturbing It will be a big change to the internals. Not something we can immediately support. |
Ok, thanks for the quick response.
Out of curiosity, is there a specific reason why you guys when with SCHEMA
Table? I personally dont have much knowledge over this, but would love to
hear your perspective
…On Wed, Mar 27, 2019 at 5:26 PM Shahidh K Muhammed ***@***.***> wrote:
@Disturbing <https://github.com/Disturbing> It will be a big change to
the internals. Not something we can immediately support.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#411 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACQev7cNuU1qDdvSEfOhe8VesUH95rQxks5vazlRgaJpZM4WjIgY>
.
|
@Disturbing When Hasura connects to a Postgres instance, the connection is database scoped. It cannot access another database outside of the given one. Hence the logical choice would be to use the namespacing available within a database which is a schema. |
Thanks - makes sense. |
Hasura is now supported by YugaByte (Postgres-based distributed SQL DB): https://docs.yugabyte.com/latest/develop/graphql/hasura (I haven't personally tested this yet) |
FYI for others who are waiting for this: CockroachDB might implement user-defined schemas sometime in 2020: cockroachdb/cockroach#30916 (comment) |
Do all features of Hasura work on Yugabyte? What about this issue: yugabyte/yugabyte-db#1872? |
CockroachDB user-defined schemas RFC got merged in May. cockroachdb/cockroach#30916 Should Hasura works on CockroachDB now? |
is it possible to reopen the ticket for adding support for cockroachdb considering thier project manager and dev stated they are seeking to make it compatible? or is there some other serious blocker to making it work? |
We document Postgres + compatible databases here. |
An upcoming version of ndc-spec will split out this module as a new crate named `ndc_models`. This PR gets ahead of this change by aliasing so that we can simply delete the `use` lines in the future. This is a very boring, mechanical change that does not modify any behavior at all. V3_GIT_ORIGIN_REV_ID: 078d3f5fbc2961fcd93b924134de40ba693f0061
There are many flavors of postgresql which
graphql-engine
might support out of the box or with slight configuration/modifications. We need to document for each of them.TimescaleDB
Yugabyte
Aurora - Postgres
CockroachDB
CitusDB
CrateDB
PipelineDB
Current status (note that these have not been officially tested by Hasura and are based on empirical usage):
The text was updated successfully, but these errors were encountered: