postgresql/contrib/lo/lo.sql.in

--
--	PostgreSQL code for LargeObjects
--
--	$Id: lo.sql.in,v 1.8 2002/10/18 18:41:20 momjian Exp $
--
--
--	Create the data type
--

-- used by the lo type, it takes an oid and returns an lo object

-- Adjust this setting to control where the objects get created.
SET search_path = public;

SET autocommit TO 'on';

CREATE FUNCTION lo_in(cstring)
RETURNS lo
AS 'MODULE_PATHNAME'
LANGUAGE 'C';

-- used by the lo type, it returns the oid of the object
CREATE FUNCTION lo_out(lo)
RETURNS cstring
AS 'MODULE_PATHNAME'
LANGUAGE 'C';

-- finally the type itself
CREATE TYPE lo (
	INTERNALLENGTH = 4,
	EXTERNALLENGTH = variable,
	INPUT = lo_in,
	OUTPUT = lo_out
);

-- this returns the oid associated with a lo object
CREATE FUNCTION lo_oid(lo)
RETURNS oid
AS 'MODULE_PATHNAME'
LANGUAGE 'C';

-- same function, named to allow it to be used as a type coercion, eg:
--    CREATE TABLE a (image lo);
--    SELECT image::oid FROM a;
--
CREATE FUNCTION oid(lo)
RETURNS oid
AS 'MODULE_PATHNAME', 'lo_oid'
LANGUAGE 'C';

-- this allows us to convert an oid to a managed lo object
-- ie: insert into test values (lo_import('/fullpath/file')::lo);
CREATE FUNCTION lo(oid)
RETURNS lo
AS 'MODULE_PATHNAME'
LANGUAGE 'C';

-- This is used in triggers
CREATE FUNCTION lo_manage()
RETURNS trigger
AS 'MODULE_PATHNAME'
LANGUAGE 'C';