This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:mysql:constraints [2011/04/07 16:57] 127.0.0.1 external edit |
integration:rdbms:mysql:constraints [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 71: | Line 71: | ||
| === Declaring Indexes === | === Declaring Indexes === | ||
| - | MySQL indexes that exist on primary and foreign key constraints should be declared as NATIVE indexes in the Omnidex Environment File. It can also be beneficial to declare other MySQL indexes as well. | + | MySQL indexes that exist on primary and foreign key constraints should be declared as NATIVE indexes in the Omnidex Environment File. It can be beneficial to declare other MySQL indexes as well. |
| The Omnidex SQL Engine will evaluate the presence of native MySQL indexes when deciding how to process a statement. At times, it may be faster to rely on the native MySQL indexes than to use Omnidex indexes. This is especially true for searches on unique values, such as primary keys. | The Omnidex SQL Engine will evaluate the presence of native MySQL indexes when deciding how to process a statement. At times, it may be faster to rely on the native MySQL indexes than to use Omnidex indexes. This is especially true for searches on unique values, such as primary keys. | ||