create or replace function etp__create_page(integer, varchar, varchar, varchar) returns integer as ' declare p_package_id alias for $1; p_name alias for $2; p_title alias for $3; p_content_type alias for $4; -- default null -> use content_revision v_item_id integer; v_revision_id integer; v_folder_id integer; begin v_item_id := acs_object__new(null, ''content_item'', now(), null, null, p_package_id); v_folder_id := etp__get_folder_id(p_package_id); -- due to a change in acs_object__delete we can reference the actual -- object type we want -- using this we can more easily search, but we will have to create a service -- contract for each custom content type -- we define a default etp_page_revision and service contract to go with it -- make sure to subtype from etp_page_revision for any custom types -- 2003-01-12 DaveB insert into cr_items ( item_id, parent_id, name, content_type ) values ( v_item_id, v_folder_id, p_name, p_content_type ); v_revision_id := acs_object__new(null, p_content_type, now(), null, null, v_item_id); insert into cr_revisions (revision_id, item_id, title, publish_date, mime_type) values (v_revision_id, v_item_id, p_title, now(), ''text/enhanced''); update cr_items set live_revision = v_revision_id where item_id = v_item_id; return 1; end; ' language 'plpgsql'; create or replace function etp__create_page(integer, integer, varchar, varchar, varchar) returns integer as ' declare p_item_id alias for $1; p_package_id alias for $2; p_name alias for $3; p_title alias for $4; p_content_type alias for $5; -- default null -> use content_revision v_item_id integer; v_revision_id integer; v_folder_id integer; begin if p_item_id is null then v_item_id := acs_object__new(null, ''content_item'', now(), null, null, p_package_id); else v_item_id := acs_object__new(p_item_id, ''content_item'', now(), null, null, p_package_id); end if; v_folder_id := etp__get_folder_id(p_package_id); -- due to a change in acs_object__delete we can reference the actual -- object type we want -- using this we can more easily search, but we will have to create a service -- contract for each custom content type -- we define a default etp_page_revision and service contract to go with it -- make sure to subtype from etp_page_revision for any custom types -- 2003-01-12 DaveB insert into cr_items ( item_id, parent_id, name, content_type ) values ( v_item_id, v_folder_id, p_name, p_content_type ); v_revision_id := acs_object__new(null, p_content_type, now(), null, null, v_item_id); insert into cr_revisions (revision_id, item_id, title, publish_date, mime_type) values (v_revision_id, v_item_id, p_title, now(), ''text/enhanced''); update cr_items set live_revision = v_revision_id where item_id = v_item_id; return 1; end; ' language 'plpgsql';