This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:oracle:queries [2011/03/31 20:57] doc |
integration:rdbms:oracle:queries [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| [[integration:rdbms:oracle:databases|Databases]] | | [[integration:rdbms:oracle:databases|Databases]] | | ||
| [[integration:rdbms:oracle:tables|Tables]] | | [[integration:rdbms:oracle:tables|Tables]] | | ||
| - | [[integration:rdbms:oracle:indexes|Indexes]] | | + | [[integration:rdbms:oracle:constraints|Constraints]] | |
| + | [[integration:rdbms:oracle:datatypes|Datatypes]] | | ||
| **[[integration:rdbms:oracle:queries|Queries]]** | | **[[integration:rdbms:oracle:queries|Queries]]** | | ||
| [[integration:rdbms:oracle:updates|Updates]] | | [[integration:rdbms:oracle:updates|Updates]] | | ||
| Line 20: | Line 21: | ||
| ==== Queries ==== | ==== Queries ==== | ||
| - | The Omnidex SQL Engine will optimize queries to take advantage of the Omnidex indexes. Many queries can be completed 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 data resides in an index. | + | === === |
| + | 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 Oracle data. The Omnidex SQL Engine will determine how to combine the results from the Omnidex indexes with the data from the Oracle database. Usually, this means that Omnidex provides Oracle rowids or primary keys and requests rows from the Oracle tables based on those values. Other times, Omnidex may issue a more complex statement to Oracle, asking it to perform a larger role in processing the query. | + | Other queries will require access to the underlying Oracle data. The Omnidex SQL Engine will determine how to combine the results from the Omnidex indexes with the data from the Oracle database. Usually, this requires that Omnidex provide Oracle rowids or primary keys and request rows from the Oracle tables based on those values. Other times, Omnidex may issue a more complex statement to Oracle, asking it to perform a larger role in processing the query. |
| In all cases, Omnidex will access the data in the Oracle database using standard Oracle SQL statements issued using the Oracle Call Interface (OCI). | In all cases, Omnidex will access the data in the Oracle database using standard Oracle SQL statements issued using the Oracle Call Interface (OCI). | ||
| Line 28: | Line 30: | ||
| === Oracle-specific Syntax === | === Oracle-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 database, as well as Omnidex-specific extensions. Omnidex SQL does support some Oracle-specific functions, including: | + | 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. If the statement, [[dev:sql:statements:set_sqlsyntax:home|SET SQL_SYNTAX ORACLE]] is issued, then Omnidex SQL will also support these Oracle-specific functions: |
| * [[dev:sql:functions:chr|CHR]] | * [[dev:sql:functions:chr|CHR]] | ||
| Line 46: | Line 48: | ||
| ===== ===== | ===== ===== | ||
| - | **[[integration:rdbms:oracle:indexes|Prev]]** | | + | **[[integration:rdbms:oracle:datatypes|Prev]]** | |
| **[[integration:rdbms:oracle:updates|Next]]** | **[[integration:rdbms:oracle:updates|Next]]** | ||