mirror of
https://github.com/supabase/supabase.git
synced 2026-05-06 08:56:46 -04:00
Laurence Isla
08e9cdde5e
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Replaces "stored procedures" with "functions" for everything related to the Data API. ## Additional context It's not accurate to call database functions "stored procedures". It may have been that way before Postgres 11, but now it causes confusion because PostgREST allows functions and not stored procedures. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Standardized terminology across docs, SDK guides, CLI/config specs, examples, UI, and config comments to use "database functions" instead of "stored procedures". * Updated API docs, CLI/config descriptions, Studio UI labels, help text, empty-state and navigation copy, RPC documentation, and example text for consistency. * Adjusted explanatory text and error/help messages to reflect the revised terminology. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
21 lines
516 B
TypeScript
21 lines
516 B
TypeScript
import { DocSection } from '../../DocSection'
|
|
|
|
const Introduction = () => {
|
|
return (
|
|
<DocSection
|
|
title="Introduction"
|
|
content={
|
|
<>
|
|
<p>
|
|
All of your database functions are available on your API. This means you can build your
|
|
logic directly into the database (if you're brave enough)!
|
|
</p>
|
|
<p>The API endpoint supports POST (and in some cases GET) to execute the function.</p>
|
|
</>
|
|
}
|
|
/>
|
|
)
|
|
}
|
|
|
|
export default Introduction
|