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/03/18 16:47] deb |
admin:indexing:indexes:groups [2011/03/18 17:45] deb |
||
|---|---|---|---|
| Line 44: | Line 44: | ||
| * 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 79: | 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> | ||