This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:concepts:retrieval [2011/01/24 15:27] 127.0.0.1 external edit |
admin:indexing:concepts:retrieval [2012/10/26 14:57] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| + | {{page>:top_add&nofooter&noeditbtn}} | ||
| ====== Administration: Indexing Strategies ====== | ====== Administration: Indexing Strategies ====== | ||
| Line 23: | Line 23: | ||
| Other queries may request primary keys, or even data from other columns. If these columns are found in the indexes, they will be returned from the index in order to minimize retrieval from the database. Omnidex will automatically perform this optimization. | Other queries may request primary keys, or even data from other columns. If these columns are found in the indexes, they will be returned from the index in order to minimize retrieval from the database. Omnidex will automatically perform this optimization. | ||
| - | Using these techniques, it is possible to optimize complex queries without ever accessing the database. A query may access a dozens of tables, applying a wide variety of criteria and performing aggregations and ordering. If Omnidex can, it will attempt to satisfy all of these aspects in the indexes, providing the best performance possible. | + | Using these techniques, it is possible to optimize complex queries without ever accessing the database. A query may access dozens of tables, applying a wide variety of criteria and performing aggregations and ordering. If Omnidex can, it will attempt to satisfy all of these aspects in the indexes, providing the best performance possible. |
| ===== ===== | ===== ===== | ||
| **[[admin:indexing:concepts:ordering|Prev]]** | **[[admin:indexing:concepts:ordering|Prev]]** | ||
| + | |||
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||