From ac69de17b31453cf61b8e21958a521631ea3e48b Mon Sep 17 00:00:00 2001 From: Brendan Clement Date: Mon, 5 Oct 2026 14:23:40 -0700 Subject: [PATCH] docs: say how to drop a Function maintenance/background-jobs.mdx links to /management/function#drop, which did not exist. The section follows drop_function and drop_function_async on main: dropping removes the name and its object, and deleting the content can finish later as a background job. --- docs/web/management/function.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/web/management/function.mdx b/docs/web/management/function.mdx index cbf442ac5..b1df47901 100644 --- a/docs/web/management/function.mdx +++ b/docs/web/management/function.mdx @@ -196,6 +196,14 @@ In practice this means a function should be self-contained: take its inputs as arguments, import what it needs at module level, and avoid capturing state from the surrounding scope. +## Drop it {#drop} + +`db.drop_function(name, version=...)` drops the function's name and the object +it is bound to; `version` must be a version that exists. It returns `False` if +the name was already gone. Deleting the object's content can finish after the +call returns, as a [background job](/maintenance/background-jobs). +`drop_function_async` returns that job with the result, so you can wait for it. + ## What to read next {#next}