[php-blog-cvs] serendipity/sql db_update_0.6.9_0.7.0_mysql.sql,NONE,1.1 db_update_0.6.9_0.7.0_postgresql.sql,NONE,1.1 db.sql,1.19,1.20

[Joseph T. <jt...@us...>]

Update of /cvsroot/php-blog/serendipity/sql
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17671

Modified Files:
	db.sql 
Added Files:
	db_update_0.6.9_0.7.0_mysql.sql 
	db_update_0.6.9_0.7.0_postgresql.sql 
Log Message:
Fixed an index that was causing problems on PostgreSQL.  It's a bad idea to have an index on a "TEXT" type column.  One rarely uses body or extended as the WHERE clause of a SQL statement, so an index is unwarranted.

--- NEW FILE: db_update_0.6.9_0.7.0_mysql.sql ---
#This is not really necessary for mysql, but is here for consistency
DROP INDEX entry_idx;
CREATE INDEX entry_idx ON serendipity_entries(title);

--- NEW FILE: db_update_0.6.9_0.7.0_postgresql.sql ---
DROP INDEX entry_idx;
CREATE INDEX entry_idx ON serendipity_entries(title);
Index: db.sql
===================================================================
RCS file: /cvsroot/php-blog/serendipity/sql/db.sql,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- db.sql	13 Oct 2004 08:57:52 -0000	1.19
+++ db.sql	30 Oct 2004 22:45:12 -0000	1.20
@@ -65,7 +65,8 @@
   moderate_comments {BOOLEAN}
 );
 
-CREATE {FULLTEXT} INDEX entry_idx on {PREFIX}entries (title,body,extended);
+#Creating an index on the body and extended body is a bad idea
+CREATE {FULLTEXT} INDEX entry_idx on {PREFIX}entries (title);
 CREATE INDEX date_idx ON {PREFIX}entries (timestamp);
 CREATE INDEX mod_idx ON {PREFIX}entries (last_modified);