CREATE FUNCTION, PROCEDURE, TRIGGER, EXTENSION

CREATE FUNCTION — parses#

CREATE FUNCTION name ( [ [argname] datatype [, ...] ] )
RETURNS rettype
LANGUAGE lang
AS $$ body $$ | AS 'body'

Source: CreateStatement::Function { name, args: Vec<FunctionArg{name, data_type}>, returns, language, body }.

CREATE FUNCTION add_two(a INT, b INT) RETURNS INT LANGUAGE sql AS $$ SELECT a + b $$;

CREATE FUNCTION greet(name TEXT) RETURNS TEXT LANGUAGE plpgsql AS $$ BEGIN RETURN 'hi'; END $$;

CREATE FUNCTION f(INT, TEXT) RETURNS VOID LANGUAGE c AS 'f_body';

Behavior: accepted, stored nowhere, callable nowhere. Calling SELECT add_two(1,2) → unknown-function error. DROP FUNCTION name[(types)] [CASCADE|RESTRICT] parses and removes the stub entry shape only.

What to use instead: implement logic in SQL expressions, views, or application code. See Functions.

CREATE PROCEDURE — parses#

CREATE PROCEDURE clean_old_orders() LANGUAGE sql AS
  $$ DELETE FROM orders WHERE placed_at < now() - INTERVAL '1 year' $$;

CreateStatement::Procedure { name } only — args/body discarded shapes. No CALL execution in v0.1.0.

CREATE TRIGGER — parses#

CREATE TRIGGER audit_insert AFTER INSERT ON orders FOR EACH ROW EXECUTE FUNCTION audit_fn();

CreateStatement::Trigger { name } only. No firing, no audit_fn resolution, no OLD/NEW support.

CREATE EXTENSION — parses#

CREATE EXTENSION pgcrypto;
CREATE EXTENSION IF NOT EXISTS "uuid-ossp";

CreateStatement::Extension { name } only. No loading, no new functions/types. If you need gen_random_uuid()-style helpers, they do not exist in v0.1.0 — generate UUIDs client-side.

Related#