Skip to content
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

Add SQL trigger support to v4 model #88

Closed
lucyzhang929 opened this issue Apr 26, 2023 · 6 comments · Fixed by #240
Closed

Add SQL trigger support to v4 model #88

lucyzhang929 opened this issue Apr 26, 2023 · 6 comments · Fixed by #240
Assignees
Milestone

Comments

@lucyzhang929
Copy link

More information about SQL Bindings can be found here.

@ejizba ejizba added the v4 🚀 We no longer use this label since v4 is now the default model. label Apr 27, 2023
@ejizba ejizba added this to the May 2023 milestone Apr 27, 2023
@ejizba ejizba added the feature label Apr 27, 2023
@ejizba ejizba modified the milestones: May 2023, June 2023 Jun 1, 2023
@ejizba ejizba self-assigned this Jun 2, 2023
@ejizba ejizba modified the milestones: June 2023, Backlog Candidates Aug 10, 2023
@ejizba
Copy link
Contributor

ejizba commented Sep 20, 2023

Added input and output binding support. I'm hesitant to add trigger support while it's still in preview, especially considering users have a workaround with our generic support.

I'd be willing to reconsider if we have users asking for it (upvotes/comments on this issue would be best), otherwise we should be able to do it as soon as it GA's. Feel free to ping us as the GA date approaches

@ejizba ejizba changed the title Add SQL bindings/trigger type support to v4 model Add SQL trigger support to v4 model Oct 2, 2023
@ejizba ejizba added P2 and removed v4 🚀 We no longer use this label since v4 is now the default model. labels Oct 10, 2023
@ejizba ejizba removed their assignment Jan 4, 2024
@andreasbhansen
Copy link

Any thoughts on adding support for SQL triggers now a half-ish year later, @ejizba? Are there still issues with this functionality which blocks the implementation into @azure/functions?

@ejizba
Copy link
Contributor

ejizba commented Feb 7, 2024

It's a question of priority against our other work, not anything blocking it necessarily. I was primarily waiting for the SQL trigger to go GA, but as far as I can tell the docs still list it as preview. If GA won't be for a long time or if we get sufficient user feedback asking for it, we could add it before GA. But to be honest @andreasbhansen you're the first person to ask for it (excluding Lucy who is on the team that developed the sql stuff 😉)

@lucyzhang929
Copy link
Author

@ejizba GA for SQL trigger will be very soon! We are currently waiting for a new extension bundle version to be released which will contain our GA bits. Will update here once we are officially GA.

@lucyzhang929
Copy link
Author

@ejizba The SQL trigger is now generally available!

@ejizba
Copy link
Contributor

ejizba commented Apr 1, 2024

Fyi @andreasbhansen @lucyzhang929 we just released v4.4.0 with SQL trigger support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants