Changeset 6396

Timestamp:

12/09/07 19:31:12 (1 year ago)

Author:

Carl.Vondrick

Message:

clarified search environment in README files

Files:

• plugins/sfLucenePlugin/branches/1.0/README (modified) (1 diff)
• plugins/sfLucenePlugin/trunk/README (modified) (1 diff)

plugins/sfLucenePlugin/branches/1.0/README

@@ -82 +82 @@
-
-"analyzer" can either by text, textnum, utf8, or utf8num.  If you choose text, all numbers will be ignored.  If you require the index to be case sensitive, set "case_sensitive" to "on".    mb_string determines whether to use the mb_* string functions instead of the standard PHP string filters.  This adds a huge performance bottleneck to indexing when turned on, so use with care.  You only need to turn mb_string on if you are working with a case-insensitive utf8 index.
+
+By default, in the command line sfLucene operates in the "search" environment.  This has the advantage to that if you require a different configuration setting for the search environment, you can easily set it up.  But, if your database is only selectively configured per environment (ie, not for "all"), then you will quickly run into trouble.  To get around this, define a database for either "all" or the "search" environment.  
-
-= Indexing =

plugins/sfLucenePlugin/trunk/README

@@ -76 +76 @@
-
-"analyzer" can either by text, textnum, utf8, or utf8num.  If you choose text, all numbers will be ignored.  If you require the index to be case sensitive, set "case_sensitive" to "on".    mb_string determines whether to use the mb_* string functions instead of the standard PHP string filters.  This adds a huge performance bottleneck to indexing when turned on, so use with care.  You only need to turn mb_string on if you are working with a case-insensitive utf8 index.
+
+By default, in the command line sfLucene operates in the "search" environment.  This has the advantage to that if you require a different configuration setting for the search environment, you can easily set it up.  But, if your database is only selectively configured per environment (ie, not for "all"), then you will quickly run into trouble.  To get around this, define a database for either "all" or the "search" environment.  
-
-= Indexing =