Overview | Environments | Databases | Tables | Constraints | Datatypes | Queries | Updates | Example

The Omnidex SQL Engine will optimize queries to take advantage of the Omnidex indexes. Many queries can be fulfilled entirely within the Omnidex indexes. This is especially true for queries that request counts or aggregations from one or more tables. Even queries that return columns of data can be completed using the Omnidex indexes, as long as all of the requested data resides in an index.

Other queries will require access to the underlying MySQL data. The Omnidex SQL Engine will determine how to combine the results from the Omnidex indexes with the data from the MySQL database. Usually, this requires that Omnidex provide MySQL rowids or primary keys and request rows from the MySQL tables based on those values. Other times, Omnidex may issue a more complex statement to MySQL, asking it to perform a larger role in processing the query.

In all cases, Omnidex will access the data in the MySQL database using standard MySQL SQL statements issued using the MySQL OBDC Connector.

Omnidex requires that all statements use Omnidex SQL syntax. Omnidex SQL uses ANSI SQL as a base, but also allows extensions from various databases, as well as Omnidex-specific extensions. Other MySQL-specific syntax will cause errors when submitted to Omnidex. In these situations, the statements must be converted to Omnidex SQL.

Prev | Next

See also: