Index: openacs-4/packages/search/sql/oracle/search-tables-create.sql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/search/sql/oracle/search-tables-create.sql,v
diff -u -r1.7 -r1.7.4.1
--- openacs-4/packages/search/sql/oracle/search-tables-create.sql	31 Aug 2006 07:31:29 -0000	1.7
+++ openacs-4/packages/search/sql/oracle/search-tables-create.sql	16 Apr 2008 12:41:13 -0000	1.7.4.1
@@ -15,46 +15,13 @@
 --
 
 --
--- Create database tables for .LRN site-wide search
 --
 -- @author <a href="mailto:openacs@dirkgomez.de">openacs@dirkgomez.de</a>
 -- @version $Id$
 -- @creation-date 13-May-2005
 --
 -- Partly ported from ACES.
 
--- Central table for site-wide search. 
-create table site_wide_index (
-	object_id		integer
-                                        constraint sws_index_pk primary key
-                                        constraint sws_index_fk references acs_objects(object_id) on delete cascade,
-	object_name	     	varchar(4000),
-	indexed_content	        clob,
-	 -- Dirk Gomez: no not null constraint because we also want to
-	 -- be able to index objects which are not tied to an object,
-	 -- in particular people.
-	package_id		integer
-			        constraint swi_package_id_fk
-                                references apm_packages
-                                on delete cascade,
-        -- Dirk Gomez: This is a .LRNism. It looks like .LRN has not
-        -- only object-granular permiissions, but also
-        -- community-granular ones. In search we need not only check
-        -- whether a user has the right to view this object, but also
-        -- its community.  In pure OpenACS this should always be a
-        -- null column and it should have no referential integrity.
-        --	community_id		integer
-	--		        constraint swi_community_id_fk
-        --                        references dotlrn_communities_all
-        --                        on delete cascade,
-        -- DAVEB: We'll need to add a way for dotlrn to integrate
-        -- without tying it into the search table.
-        -- Dirk Gomez: That's the place to put an object's relevant
-        -- date which is part of the ranking function. In calendar
-        -- this is the item date, in forum it could be the last reply
-        -- date to a thread etc.
-        relevant_date           date
-);
 
 create table search_observer_queue (
     object_id                       integer,