-
Notifications
You must be signed in to change notification settings - Fork 399
Guide: stored procedures and prepared statements equivalents in ClickHouse #4694
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
Conversation
|
@Blargian is attempting to deploy a commit to the ClickHouse Team on Vercel. A member of the Team first needs to authorize it. |
dhtclk
left a comment
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.
Perhaps we should consider including TL;DR blocks in all or most of our new guides moving forward similar to what has been introduced with clickstack guides.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dhtclk
left a comment
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.
Looks good just some minor formatting discussion, mostly casing and headers. Open to discuss.
docs/guides/developer/stored-procedures-and-prepared-statements.md
Outdated
Show resolved
Hide resolved
docs/guides/developer/stored-procedures-and-prepared-statements.md
Outdated
Show resolved
Hide resolved
docs/guides/developer/stored-procedures-and-prepared-statements.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Dominic Tran <dominic.tran@clickhouse.com>
Co-authored-by: Dominic Tran <dominic.tran@clickhouse.com>
Summary
Addresses one of the Kapa content gap suggestions.
Checklist