This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
admin:indexing:indexes:options [2012/04/04 15:45] doc |
admin:indexing:indexes:options [2016/06/28 22:38] (current) |
||
---|---|---|---|
Line 106: | Line 106: | ||
== RECORD_SPECIFIC == | == RECORD_SPECIFIC == | ||
- | The RECORD_SPECIFIC option is used in conjunction with the PREJOIN option to create a pre-joined index. The RECORD_SPECIFIC option indicates that the index in the pre-joined child table should record information about both the row and the parent. This provides a powerful ability to join between multiple children in a parent. At the same time, these indexes are more expensive to build and are slower in base qualifications. Consult the article on [[admin:indexing:advanced:prejoin|Prejoined Indexes]] for more information about this option. | + | The RECORD_SPECIFIC option is used in conjunction with the PREJOIN option to create a pre-joined index. The RECORD_SPECIFIC option indicates that the index in the pre-joined child table should record information about both the row and the parent. This provides a powerful ability to join between multiple children in a parent. At the same time, these indexes are more expensive to build and are slower in base qualifications. |
The RECORD_SPECIFIC and RECORD_COMPLEX options are mutually exclusive. | The RECORD_SPECIFIC and RECORD_COMPLEX options are mutually exclusive. | ||
Line 112: | Line 112: | ||
== RECORD_COMPLEX == | == RECORD_COMPLEX == | ||
- | The RECORD_COMPLEX option is used in conjunction with the PREJOIN option to create a pre-joined index. The RECORD_COMPLEX option indicates that the index in the pre-joined child table should record information about only the parent. This is valuable when a single column in a pre-joined child is used as criteria. This provides a powerful ability to join between a child and its parent. Consult the article on [[admin:indexing:advanced:prejoin|Prejoined Indexes]] for more information about this option. | + | The RECORD_COMPLEX option is used in conjunction with the PREJOIN option to create a pre-joined index. The RECORD_COMPLEX option indicates that the index in the pre-joined child table should record information about only the parent. This is valuable when a single column in a pre-joined child is used as criteria. This provides a powerful ability to join between a child and its parent. |
The RECORD_SPECIFIC and RECORD_COMPLEX options are mutually exclusive. | The RECORD_SPECIFIC and RECORD_COMPLEX options are mutually exclusive. | ||
Line 118: | Line 118: | ||
== PREJOIN table == | == PREJOIN table == | ||
- | The PREJOIN option is used to pre-join a RECORD_SPECIFIC or RECORD_COMPLEX index with a parent table. This is required for Prejoined Indexes. Consult the article on [[admin:indexing:advanced:prejoin|Prejoined Indexes]] for more information about this option. | + | The PREJOIN option is used to pre-join a RECORD_SPECIFIC or RECORD_COMPLEX index with a parent table. This is required for Prejoined Indexes. |
==== ==== | ==== ==== |