Introduction to Database Systems

Stored Procedures, Functions and Triggers

in PostGreSQL

Stphane Bressan
Introduction to Database Systems

Disclaimer
The objective of this lecture is neither to offer a exhaustive
presentation of the SQL standard for stored procedures and triggers
or a comprehensive presentation of the underlying concepts, nor to
serve as a complete tutorial for PostgreSQL stored procedures and
functions in PL/pgSQL and triggers.

Rather, the objective of this lecture is to illustrate some selected

important concepts and to give a handful of examples of PostgreSQL
stored procedures and functions in PL/pgSQL and of PostgreSQL
triggers that you can use and extend in your project.
 Introduction to Database Systems

Stored Procedures
Recall that most DBMS, including PostgreSQL, have a client/server
architecture

Application
code Data
Introduction to Database Systems

Stored Procedures
The SQL 1999 standard proposes a language for stored procedures
and triggers. PostgreSQL (and other DBMS) can store, share and
execute code on the server. PL/pgSQL is PostgreSQLs language
specifically designed to seamlessly embed SQL code and interact
with the database SQL code. PL/pgSQL partially complies with the
SQL standard. PL/pgSQL is similar to Oracle PL/SQL, SQLServer
Transact-SQL and DB2 SQL Procedural Language and other
languages implementing variants of the Persistent Stored Modules
portion of the SQL standard.
Introduction to Database Systems

Stored Procedures
Performance: Stored procedures are compiled. The code is cached
and shared by all users. The code is executed on the servers side,
usually a powerful machine. They incur generally fewer data transfer
across the network. The optimization of the SQL code they contain
is not adaptive. The clients computing power is underutilized.
Productivity: Stored procedures are shared and reused under access
control. The application logic that they encode is implemented and
maintained in a single place. The code is not portable from one
DBMS to the next. The languages and concepts are complicated.
Security: Data manipulation can be restricted to calling stored
procedures under strict access control. It is easy to make tragic
mistake while coding.
Introduction to Database Systems

Example Function

CREATE FUNCTION creates a

function. The function definition
is between single quotes. The
language is PLPGSQL (can also
be C, Perl, Python or tcl).

CREATE OR REPLACE FUNCTION SELECT gst(1);

gst(val NUMERIC) RETURNS
NUMERIC AS SELECT g.name,
'BEGIN gst(g.price)
RETURN val * 1.07; FROM games g
END;' WHERE gst(g.price) < 5;
LANGUAGE PLPGSQL;
Introduction to Database Systems

Example Function

The function definition is CREATE OR REPLACE FUNCTION

between $$ or $<name>$ hello()
RETURNS CHAR(5) AS $$
otherwise quotes in the function
BEGIN
definition need to be escaped.
RETURN 'Hello World';
Available types include:
NUMERIC, VARCHAR() END; $$
LANGUAGE PLPGSQL;
(SQL domains),
tablename%ROWTYPE,
tablename.columnname%T SELECT hello();
YPE, RECORD.
SELECT hello() FROM games;
Introduction to Database Systems

Example Function

RAISE NOTICE prints on the DROP FUNCTION hello();

database console.
CREATE OR REPLACE FUNCTION
hello()
RETURNS BOOLEAN AS $$
BEGIN
RAISE NOTICE 'hello';
RETURN TRUE;
END; $$
LANGUAGE PLPGSQL;

SELECT hello() FROM games;

Introduction to Database Systems

Example Function: Reading from the

Database
SQL seamlessly integrates with CREATE OR REPLACE FUNCTION
gst(val NUMERIC)
PL/pgSQL.
RETURNS NUMERIC AS $$
DECLARE gst1 NUMERIC;
CREATE TABLE gst (gst
BEGIN
NUMERIC);
SELECT g.gst/100 INTO gst1
INSERT INTO gst VALUES
FROM gst g;
(7);
RETURN val * (1 + gst1);
END; $$
LANGUAGE PLPGSQL;

SELECT a.name, gst(g.price)

FROM games g;
Introduction to Database Systems

Example Function: Control Structures

CREATE OR REPLACE FUNCTION gst(val
NUMERIC)
IF condition RETURNS NUMERIC AS $$
THEN DECLARE gst1 NUMERIC;
ELSIF condition BEGIN
THEN SELECT g.gst/100 INTO gst1 FROM
gst g;
ELSE END IF;
IF val * (1 + gst1) > 5 THEN
FOR somevariable
RETURN val * 1 + gst1;
IN (number ELSE
number)
RETURN 5;
LOOP END IF;
EXIT END; $$
EXIT WHEN LANGUAGE PLPGSQL;
END LOOP;
SELECT g.name, gst(g.price)
FROM games g;
 Introduction to Database Systems

Cursors

name version price

'Aerified' '1.0' 12
'Aerified' '1.1' 3.99
'Aerified' '1.2' 1.99
'Aerified' '2.0' 5
'Aerified' '2.1' 12
'Aerified' '3.0' 3.99
FETCH NEXT/PRIOR CURSOR 'Alpha' '1.0' 12
'Alpha' '1.1' 3.99
'Alpha' '1.2' 12
'Alpha' '2.0' 12
'Alpha' '2.1' 2.99
'Alpha' '3.0' 5
'Alphazap' '1.1' 5
'Alphazap' '1.2' 3.99
'Alphazap' '2.0' 5
'Alphazap' '2.1' 3.99
'Alphazap' '3.0' 12
'Andalax' '1.0' 12
'Andalax' '1.1' 12
'Andalax' '2.0' 12
Introduction to Database Systems

Example Function: Cursor

CREATE OR REPLACE FUNCTION avg1(appname VARCHAR(32))
RETURNS NUMERIC AS $$
DECLARE mycursor SCROLL CURSOR (vname VARCHAR(32))
Cursors are the scalable way to FOR SELECT g.price FROM games g WHERE g.name=vname;
price NUMERIC; avgprice NUMERIC; count NUMERIC;
process data from a query BEGIN
OPEN mycursor(vname:=appname);
SCROLL, NO SCROLL, indicates avgprice:=0; count:=0; price:=0;

whether the cursor can be LOOP

FETCH mycursor INTO price;
scrolled backwards, or nor, EXIT WHEN NOT FOUND;
avgprice:=avgprice + price;
respectively. A cursor can move count:=count+1;

in different directions and END LOOP;

CLOSE mycursor;
modes: NEXT, LAST, PRIOR, IF count<1 THEN RETURN null;
ELSE RETURN avgprice/count; END IF;
FIRST, ABSOLUTE, END; $$

RELATIVE, FORWARD, LANGUAGE PLPGSQL;

BACKWARD. Cursors must be SELECT avg1('Aerified');

closed. SELECT name, avg1(name)

FROM games;
Introduction to Database Systems

Triggers
Triggers program the reaction to events happening to the database.

triggers

INSERT, UPDATE, DELETE

Introduction to Database Systems

SQL 1999 Triggers

A trigger is a procedure or function that is executed when a database
event occurs on a table (e.g. INSERT, DELETE, UPDATE, CREATE
TABLE, etc.). Triggers are used to maintain integrity, propagate
updates and repair the database (they are a generalization of ON
UPDATE/DELETE). Their syntax and semantics vary from one
DBMS to the next.
Introduction to Database Systems

Triggers
Performance: Triggers are compiled. The code is cached and shared
by all users. The code is executed on the servers side, usually a
powerful machine. They incur no data transfer across the network.
The optimization of the SQL code they contain is not adaptive. The
clients computing power is not utilized.
Productivity: Triggers are applied to all interactions. The application
logic they encode is implemented and maintained in a single place.
The languages and concepts are complicated. The code is not
portable from one DBMS to the next. Interactions among triggers
(chain reactions) and between triggers, constraints and transactions
are difficult to control.
Security: Data manipulation can be restricted and transformations
automatically propagated. It is easy to make tragic mistake while
coding.
Introduction to Database Systems

PostgreSQL Trigger Syntax

CREATE TRIGGER name
{BEFORE|AFTER|INSTEAD OF}{event [OR event]*}
ON table
[FOR [EACH] {ROW|STATEMENT}]% statement by
default
[WHEN condition] % for row only
EXECUTE PROCEDURE function()

Variables: NEW(for row only), OLD(for row only),

TG_WHEN('BEFORE', 'AFTER'),
TG_OP ('INSERT', 'DELETE, 'UPDATE',
'TRUNCATE')
Introduction to Database Systems

Example Trigger: For Each Statement

DROP FUNCTION hello() CASCADE;

In PostgreSQL a trigger execute CREATE OR REPLACE FUNCTION hello()

RETURNS TRIGGER AS $$
a function of type trigger. The BEGIN
example shows a trigger that RAISE NOTICE 'hello';
RETURN NULL;
sends a message to the database END; $$
console before every insertion LANGUAGE PLPGSQL;

and update (for each statement) CREATE TRIGGER hello

on the table apps. The three rows BEFORE INSERT OR UPDATE
are inserted. The message 'hello' ON games
FOR EACH STATEMENT
is displayed once. EXECUTE PROCEDURE hello();

INSERT INTO apps VALUES ('A', '5.1', 100),

('B', '3.0', 101), ('C', '3.0', 102);

SELECT * FROM games g WHERE g.name='A' OR

g.name='B' OR g.name='C';
Introduction to Database Systems

Example Trigger: For each Row

DROP FUNCTION hello() CASCADE;

CREATE OR REPLACE FUNCTION hello()

The example shows a trigger RETURNS TRIGGER AS $$
that sends a message to the BEGIN

database console for each row of RAISE NOTICE 'hello';

RETURN NULL;
the table apps affected by an END; $$ LANGUAGE PLPGSQL;
insertion or update if the new
CREATE TRIGGER hello
price is more than 100. RETURN BEFORE INSERT OR UPDATE
NULL prevents the insertion or ON games

update. The row ('AAA', FOR EACH ROW

WHEN (NEW.price > 100)
'5.1', 100) is inserted. EXECUTE PROCEDURE hello();
The message 'hello' is
INSERT INTO games VALUES ('AA', '5.1',
displayed twice and the other 100), ('BB', '3.0', 101), ('CC', '3.0',
102);
rows are not inserted.
SELECT * FROM games g WHERE g.name='AA' OR
g.name='BB' OR g.name='CC';
Introduction to Database Systems

Example Trigger: RETURN NEW

DROP FUNCTION hello() CASCADE;

The insertion or update is done CREATE OR REPLACE FUNCTION hello()

RETURNS TRIGGER AS $$
when the stored procedure returns BEGIN
NEW. The three rows are inserted. RAISE NOTICE 'hello';
The message 'hello' is RETURN NEW;
END; $$ LANGUAGE PLPGSQL;
displayed twice.
CREATE TRIGGER hello
BEFORE INSERT OR UPDATE
ON games
FOR EACH ROW
WHEN (NEW.price > 100)
EXECUTE PROCEDURE hello();

INSERT INTO games VALUES ('AAA', '5.1',

100), ('BBB', '3.0', 101), ('CCC', '3.0',
102);

SELECT * FROM games WHERE g.name='AAA' OR

g.name='BBB' OR g.name='CCC';
Introduction to Database Systems

Example Trigger: Logging Changes

CREATE TABLE glog (name VARCHAR(32) CREATE TRIGGER pricelog
NOT NULL, version CHAR(3)NOT NULL, AFTER INSERT OR UPDATE
pricebefore NUMERIC, priceafter ON games
NUMERIC NOT NULL, date DATE NOT
NULL); FOR EACH ROW
EXECUTE PROCEDURE pricelog();
CREATE OR REPLACE FUNCTION pricelog()
RETURNS TRIGGER AS $$ INSERT INTO games VALUES ('AAAA',
'5.1', 100), ('BBBB', '3.0', 101),
DECLARE delta NUMERIC; ('CCCC', '3.0', 102);
DECLARE pb NUMERIC;
DECLARE now DATE; SELECT * FROM ganes WHERE name='AAAA'
BEGIN OR name='BBBB' OR name='CCCC';
now := now();
IF TG_OP ='INSERT' INSERT INTO games VALUES ('AAAA',
THEN pb:=null; ELSE pb:=OLD.price; '5.1', 110);
END IF;
INSERT INTO glog VALUES (NEW.name, SELECT * FROM games WHERE
NEW.version, pb, NEW.price, now); name='AAAA';
RETURN NULL;
END; $$
LANGUAGE PLPGSQL;
Introduction to Database Systems

Example Trigger: Logging Changes

DROP FUNCTION hello() CASCADE;

Triggers interact! (in
alphabetical order!). The hello INSERT INTO apps VALUES ('AAAA',
'5.1', 110);
trigger and the hello()
function prevented the change. UPDATE games SET price=99 WHERE name
LIKE'C%';
We the hello trigger and the
hello() function. There is an SELECT * from glog;

integrity constraint violation.

Introduction to Database Systems

A Note on Constraints and

Transactions
CREATE TABLE test1 (
Triggers interact with constraints father NUMERIC primary key NOT DEFERRABLE,
son NUMERIC REFERENCES test1(father)NOT
but things are even more DEFERRABLE);

complicated when constraints CREATE TABLE test2 (

father NUMERIC primary key NOT DEFERRABLE,
son NUMERIC REFERENCES test2(father)DEFERRABLE
are deferred. The foreign key INITIALLY DEFERRED);

constraint on table test1 is not BEGIN;

INSERT INTO test1 VALUES (1,2);
deferred; the foreign key INSERT INTO test1 VALUES (2,1);
END;
constraint on table test2 is SELECT * FROM test1;

deferred. The transaction on BEGIN;

INSERT INTO test2 VALUES (1,2);
table test1 is aborted. The INSERT INTO test2 VALUES (2,1);
END;
transaction on test2 succeeds SELECT * FROM test2;
and is committed.
 Introduction to Database Systems

Credits
Copyright 2017 by Stphane Bressan

The content of this lecture is based

on the book Introduction to
database Systems
By
S. Bressan and B. Catania, McGraw
Hill publisher

Images and clips used in this

presentation are licensed from
Microsoft Office Online Clipart and
Media

For questions about the content of

this course and about copyrights,
please contact Stphane Bressan

[email protected]