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.)
16 lines
375 B
SQL
16 lines
375 B
SQL
--
|
|
-- This removes the LO type
|
|
-- It's used just for development
|
|
--
|
|
|
|
-- Adjust this setting to control where the objects get created.
|
|
SET search_path = public;
|
|
|
|
-- drop the type and associated functions
|
|
DROP TYPE lo CASCADE;
|
|
|
|
-- the trigger function has no dependency on the type, so drop separately
|
|
DROP FUNCTION lo_manage();
|
|
|
|
-- the lo stuff is now removed from the system
|