This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:indexes:groups [2011/01/24 15:27] 127.0.0.1 external edit |
admin:indexing:indexes:groups [2011/03/18 17:45] deb |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| Line 13: | Line 14: | ||
| ==== Index Groups ==== | ==== Index Groups ==== | ||
| - | Index Groups are used to combine multiple indexes into one single index. This allows a search against any one index within the group to automatically search all indexes within the group. For example, if a table has three lines, ADDRESS_LINE_1, ADDRESS_LINE_2 and ADDRESS_LINE_3, they can be indexed as an Index Group. Criteria against any one of those three columns will automatically search all address lines. | + | Index Groups are used to combine multiple indexes into one single index. This allows a search against any one index within the group to automatically search all indexes within the group. For example, if a table has three lines, ADDRESS_LINE_1, ADDRESS_LINE_2, and ADDRESS_LINE_3, they can be indexed as an Index Group. Criteria against any one of those three columns will automatically search all address lines. |
| In the example below, a row displays an address: | In the example below, a row displays an address: | ||
| Line 39: | Line 40: | ||
| === Common Uses of Index Groups === | === Common Uses of Index Groups === | ||
| - | Index Groups can be used in many different situations. Here is a little of common situation where Index Groups are used: | + | Index Groups can be used in many different situations. Here is a common situation where Index Groups are used: |
| * Combining indexes for multiple address lines | * Combining indexes for multiple address lines | ||
| * Combining indexes for a short-description column and a long-description column. | * Combining indexes for a short-description column and a long-description column. | ||
| - | * Combining indexes for given names, nicknames and aliases | + | * Combining indexes for given names, nicknames, and aliases |
| * Combining indexes for multiple telephone numbers | * Combining indexes for multiple telephone numbers | ||
| * Combining indexes for multiple email addresses | * Combining indexes for multiple email addresses | ||
| Line 78: | Line 79: | ||
| </code> | </code> | ||
| - | As discussed above, care should be taken when considering where to use Index Groups across tables. It can be confusing that when a table is searched without it being included in the SQL statement. A row can also be qualified when a portion of the criteria exists in the parent and another portion exists in a child row. For example, the following search will also locate this household: | + | As discussed above, care should be taken when considering where to use Index Groups across tables. It can be confusing when a table is actually searched without it being referenced in the SQL statement. A row can also be qualified when a portion of the criteria exists in the parent and another portion exists in a child row. For example, the following search will also locate this household: |
| <code sql> | <code sql> | ||