This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:odbc:queries [2011/04/06 19:21] doc |
integration:rdbms:odbc:queries [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| Other queries will require access to the underlying database. The Omnidex SQL Engine will determine how to combine the results from the Omnidex indexes with the data from the underlying database. Usually, this requires that Omnidex provide primary keys and request rows from the underlying tables based on those values. Other times, Omnidex may issue a more complex statement through ODBC, asking it to perform a larger role in processing the query. | Other queries will require access to the underlying database. The Omnidex SQL Engine will determine how to combine the results from the Omnidex indexes with the data from the underlying database. Usually, this requires that Omnidex provide primary keys and request rows from the underlying tables based on those values. Other times, Omnidex may issue a more complex statement through ODBC, asking it to perform a larger role in processing the query. | ||
| - | In all cases, Omnidex will access the data in the underlying database using standard SQL statements issued using its ODBC driver. | + | In all cases, Omnidex will access the data using standard SQL statements issued to the underlying database's ODBC driver. |
| === ODBC-specific Syntax === | === ODBC-specific Syntax === | ||
| - | 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 ODBC-specific syntax will cause errors when submitted to Omnidex. In these situations, the statements must be converted to Omnidex SQL. | + | 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. ODBC-specific syntax may cause errors when submitted to Omnidex. In these situations, the statements must be converted to Omnidex SQL. |
| ===== ===== | ===== ===== | ||