-
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
mssql: support event triggers #7228
Comments
Notes from @nicuveo : (Documentation for event triggers: https://hasura.io/docs/latest/graphql/core/event-triggers/index.html.) This is likely to be a long task. First, the code for event triggers need to be generalized (it is Vanilla Postgres only for now);
There already are a few functions related to them in BackendMetadata, but I don't know to which extent we've moved the process to the class. |
Related issues: |
+1 for this! we love to see sql server support. |
|
Also can't wait to see this. |
+1 for this! |
This is now implemented and merged to main via abb57e5. It will be available in the upcoming release. Note that console work is still pending. |
Most excellent, thanks! |
@ecthiender so can we start using it without the console work in the next release? |
@jmarbutt Yeah, it will work without console. Pls do try it out in the next major beta (2.7) ! |
When will the next major release be available in beta? |
In release notes of 2.7 I see that MSSQL Event Trigger support is mentioned, but I cannot select MSSQL while creating an Event Trigger (my primary database is PG, MSSQL is a +1). Is this by design or a bug? |
Console support is still pending and hence we haven't officially released
it. It is slated for 2.9 release.
…On Thu, Jun 9, 2022, 3:42 PM Deluxo ***@***.***> wrote:
In release notes of 2.7 I see that MSSQL Event Trigger support is
mentioned, but I cannot select MSSQL while creating an Event Trigger (my
primary database is PG, MSSQL is a +1).
Is this by design or a bug?
—
Reply to this email directly, view it on GitHub
<#7228 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCDEEXWNLS4GTBXFAZR5J3VOG7Q3ANCNFSM5AJJLREQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Does this mean it's still possible to use it in mssql? Like via API or other ways? @tirumaraiselvan |
Similar to what we have for Postgres
The text was updated successfully, but these errors were encountered: