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 13:09] doc |
integration:rdbms:mysql:constraints [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| === Declaring Constraints === | === Declaring Constraints === | ||
| - | The table declarations in the Omnidex Environment File should include primary and foreign key constraints that establish parent-child relationships between the tables. While Omnidex does not validate or enforce these constraints; they are heavily used when optimizing queries. Omnidex does not need to know about column constraints that exist in Oracle, such as NULL, NOT NULL, CHECK or DEFAULT constraint | + | The table declarations in the Omnidex Environment File should include primary and foreign key constraints that establish parent-child relationships between the tables. While Omnidex does not validate or enforce these constraints; they are heavily used when optimizing queries. Omnidex does not need to know about column constraints that exist in MySQL, such as NULL, NOT NULL, CHECK or DEFAULT constraints. |
| In most situations, the constraints declared in Omnidex should match those declared in the MySQL database; however, administrators may alter these if they wish. At times, a parent-child relationship may exist between tables in MySQL even though a constraint is not formally declared. These can be declared in Omnidex, allowing more advanced optimization of multi-table queries. | In most situations, the constraints declared in Omnidex should match those declared in the MySQL database; however, administrators may alter these if they wish. At times, a parent-child relationship may exist between tables in MySQL even though a constraint is not formally declared. These can be declared in Omnidex, allowing more advanced optimization of multi-table queries. | ||
| - | Omnidex requires that the datatype of a foreign key constraint match the datatype of the referencing constraint. If this is not the case within the MySQL datatype, it may be possible to remap the datatype in Omnidex so that they do match. Consult the documentation on [[integration:rdbms:mysql:datatypes|datatypes]] to see the options for remapping datatypes. | + | Omnidex requires that the datatype of a foreign key constraint match the datatype of the referencing constraint. If this is not the case within the MySQL database, it may be possible to remap the datatype in Omnidex so that they do match. Consult the documentation on [[integration:rdbms:mysql:datatypes|datatypes]] to see the options for remapping datatypes. |
| Omnidex is tolerant of violations of foreign key constraints, such as foreign keys for which there are no primary keys in the corresponding tables. Omnidex is not tolerant of violations of primary key constraints, as these can lead to incorrect results returned from queries. | Omnidex is tolerant of violations of foreign key constraints, such as foreign keys for which there are no primary keys in the corresponding tables. Omnidex is not tolerant of violations of primary key constraints, as these can lead to incorrect results returned from queries. | ||
| 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. | ||