Bachir Soussi Chiadmi
78adf3a099
first global commit
|
4 years ago | |
|---|---|---|
| .. | ||
| LICENSE.txt | 4 years ago | |
| README.txt | 4 years ago | |
| search_api_db.info | 4 years ago | |
| search_api_db.install | 4 years ago | |
| search_api_db.module | 4 years ago | |
| search_api_db.test | 4 years ago | |
| service.inc | 4 years ago | |
README.txt
Database search
---------------
This module provides a database based implementation of the Search API. The
database and target to use for storing and accessing the indexes can be selected
when creating a new server.
All Search API datatypes are supported by using appropriate SQL datatypes for
their respective columns (with "String"/"URI", and "Integer"/"Duration" being
equivalent).
The "direct" parse mode for queries will result in a simple splitting of the
query string into keys. Additionally, search keys containing whitespace will be
split, as searching for phrases is currently not supported.
Due to SQL limitations, fulltext searches are always case-insensitive.
Supported optional features
---------------------------
Regarding third-party features, this module supports the "search_api_facets"
feature, introduced by the module of the same name. This lets you create
facetted searches for any index lying on a database server.
If you feel some service option is missing, or have other ideas for improving
this implementation, please file a feature request in the project's issue queue,
at [http://drupal.org/project/issues/search_api], using the "Database search"
component.
Known problems
--------------
Currently, Drupal doesn't support setting the table collation when creating
tables. This might cause problems when you are using MySQL (maybe also other
databases) and want to index data which can contain accented characters,
umlauts, etc. (à, á, ä, …).
To resolve the issue, please set "utf8_bin" as the collation for all tables
starting with "search_api_db_".
See [1] for details.
[1] http://drupal.org/node/1144620
---------------
This module provides a database based implementation of the Search API. The
database and target to use for storing and accessing the indexes can be selected
when creating a new server.
All Search API datatypes are supported by using appropriate SQL datatypes for
their respective columns (with "String"/"URI", and "Integer"/"Duration" being
equivalent).
The "direct" parse mode for queries will result in a simple splitting of the
query string into keys. Additionally, search keys containing whitespace will be
split, as searching for phrases is currently not supported.
Due to SQL limitations, fulltext searches are always case-insensitive.
Supported optional features
---------------------------
Regarding third-party features, this module supports the "search_api_facets"
feature, introduced by the module of the same name. This lets you create
facetted searches for any index lying on a database server.
If you feel some service option is missing, or have other ideas for improving
this implementation, please file a feature request in the project's issue queue,
at [http://drupal.org/project/issues/search_api], using the "Database search"
component.
Known problems
--------------
Currently, Drupal doesn't support setting the table collation when creating
tables. This might cause problems when you are using MySQL (maybe also other
databases) and want to index data which can contain accented characters,
umlauts, etc. (à, á, ä, …).
To resolve the issue, please set "utf8_bin" as the collation for all tables
starting with "search_api_db_".
See [1] for details.
[1] http://drupal.org/node/1144620