Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml,v
diff -u -N -r1.16 -r1.17
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml	26 Feb 2004 15:28:37 -0000	1.16
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml	1 Mar 2004 21:29:29 -0000	1.17
@@ -717,6 +717,104 @@
     drop function inline_0();
     </programlisting>
 
+    <para>You also need a drop script. This is untested for
+    comptability with the above script.</para>
+    <programlisting>
+--
+-- Project Manager
+--
+-- @author jader@bread.com
+-- @author gwong@orchardlabs.com,ben@openforce.biz
+-- @creation-date 2002-05-16
+--
+-- This code is newly concocted by Ben, but with significant concepts and code
+-- lifted from Gilbert's UBB forums. Thanks Orchard Labs.
+-- Jade in turn lifted this from gwong and ben.
+--
+
+create function inline_0 ()
+returns integer as '
+declare
+    row                             record;
+begin
+    for row in select nt.type_id
+               from notification_types nt
+               where nt.short_name in (''lars_blogger_notif'')
+    loop
+        perform notification_type__delete(row.type_id);
+    end loop;
+
+    return null;
+end;' language 'plpgsql';
+
+select inline_0();
+drop function inline_0 ();
+
+--
+-- Service contract drop stuff was missing - Roberto Mello 
+--
+
+create function inline_0() returns integer as '
+declare
+        impl_id integer;
+        v_foo   integer;
+begin
+
+        -- the notification type impl
+        impl_id := acs_sc_impl__get_id (
+                      ''NotificationType'',             -- impl_contract_name
+                      ''lars_blogger_notif_type'' -- impl_name
+        );
+
+        PERFORM acs_sc_binding__delete (
+                    ''NotificationType'',
+                    ''lars_blogger_notif_type''
+        );
+
+        v_foo := acs_sc_impl_alias__delete (
+                    ''NotificationType'',               -- impl_contract_name   
+                    ''lars_blogger_notif_type'',        -- impl_name
+                    ''GetURL''                          -- impl_operation_name
+        );
+
+        v_foo := acs_sc_impl_alias__delete (
+                    ''NotificationType'',               -- impl_contract_name   
+                    ''lars_blogger_notif_type'',        -- impl_name
+                    ''ProcessReply''                    -- impl_operation_name
+        );
+
+        select into v_foo type_id 
+          from notification_types
+         where sc_impl_id = impl_id
+          and short_name = ''lars_blogger_notif'';
+
+        perform notification_type__delete (v_foo);
+
+        delete from notification_types_intervals
+         where type_id = v_foo 
+           and interval_id in ( 
+                select interval_id
+                  from notification_intervals 
+                 where name in (''instant'',''hourly'',''daily'')
+        );
+
+        delete from notification_types_del_methods
+         where type_id = v_foo
+           and delivery_method_id in (
+                select delivery_method_id
+                  from notification_delivery_methods 
+                 where short_name in (''email'')
+        );
+
+        return (0);
+end;
+' language 'plpgsql';
+
+select inline_0();
+drop function inline_0();
+
+    </programlisting>
+
     <para>The next step is to setup our notification creation. A new notification must 
     be added to the notification table for each blog entry added. We do this using the 
     notification::new procedure</para>