mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-14 17:39:17 +02:00
5b0c9d3603
a physically separate type. Defining 'lo' as a domain over OID works just fine and is more efficient. Improve documentation and fix up the test script. (Would like to turn test script into a proper regression test, but right now its output is not constant because of numeric OIDs; plus it makes Unix-specific assumptions about files it can import.)
30 lines
772 B
MySQL
30 lines
772 B
MySQL
--
|
|
-- PostgreSQL code for managed Large Objects
|
|
--
|
|
-- $PostgreSQL: pgsql/contrib/lo/lo.sql.in,v 1.13 2005/06/23 00:06:37 tgl Exp $
|
|
--
|
|
|
|
-- Adjust this setting to control where the objects get created.
|
|
SET search_path = public;
|
|
|
|
--
|
|
-- Create the data type ... now just a domain over OID
|
|
--
|
|
|
|
CREATE DOMAIN lo AS pg_catalog.oid;
|
|
|
|
--
|
|
-- For backwards compatibility, define a function named lo_oid.
|
|
--
|
|
-- The other functions that formerly existed are not needed because
|
|
-- the implicit casts between a domain and its underlying type handle them.
|
|
--
|
|
CREATE FUNCTION lo_oid(lo) RETURNS pg_catalog.oid AS
|
|
'SELECT $1::pg_catalog.oid' LANGUAGE SQL STRICT IMMUTABLE;
|
|
|
|
-- This is used in triggers
|
|
CREATE FUNCTION lo_manage()
|
|
RETURNS pg_catalog.trigger
|
|
AS 'MODULE_PATHNAME'
|
|
LANGUAGE C;
|