This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:powersearch:sql [2012/01/30 19:21] doc |
admin:indexing:powersearch:sql [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| BILLIE E COOK | BILLIE E COOK | ||
| MR. WILL COOK | MR. WILL COOK | ||
| - | |||
| </code> | </code> | ||
| + | |||
| + | === The USAGE Clause === | ||
| The POWERSEARCH option works hand-in-hand with the data stored in the Omnidex Environment File. To use POWERSEARCH, administrators add a context to columns telling Omnidex what they contain. For example, a column named NAME may have a character datatype, but that alone is not enough to tell Omnidex what the column contains. Moreover, Omnidex cannot look to the column name, as there are many different conventions for naming columns. Administrators add a USAGE clause that identifies the contents as given names, as shown in this example: | The POWERSEARCH option works hand-in-hand with the data stored in the Omnidex Environment File. To use POWERSEARCH, administrators add a context to columns telling Omnidex what they contain. For example, a column named NAME may have a character datatype, but that alone is not enough to tell Omnidex what the column contains. Moreover, Omnidex cannot look to the column name, as there are many different conventions for naming columns. Administrators add a USAGE clause that identifies the contents as given names, as shown in this example: | ||
| Line 80: | Line 81: | ||
| * PHONE | * PHONE | ||
| + | * ... plus, you can add any custom usages needed for your application. | ||