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
📝 Update pg_cron documentation with examples for calling function #26186
📝 Update pg_cron documentation with examples for calling function #26186
Conversation
…ctions and stored procedures
@thibault-chausson is attempting to deploy a commit to the Supabase Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @thibault-chausson!
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Ignored Deployments
|
You're welcome @charislam! |
No problem @thibault-chausson! For the future, it's best not to push to the branch after approval (unless of course you want to make more changes 😄), otherwise we have to reapprove the Vercel checks. But it's a very minor problem, so don't worry about it! We appreciate your help! |
Thanks for these explanations! |
Ahh, that's the main supabase.com website. That failure looks like a fluke, I just reran the check and hopefully this will merge 🤞🏼 |
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
Documentation update for the pg_cron extension.
What is the current behavior?
When we use CALL to call a function, an error occurs.
What is the new behavior?
Additional context
To assist other users, I have updated the documentation to use
SELECT
to call a function, andCALL
for a stored procedure.Additionally, I specified that the
cron.schedule()
function can be used to modify a cron : pg_cron documentation.