This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
integration:rdbms:mysql:queries [2011/04/05 02:53] 127.0.0.1 external edit |
integration:rdbms:mysql:queries [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| 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. | 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 Call Interface (OCI). | + | In all cases, Omnidex will access the data in the MySQL database using standard MySQL SQL statements issued using the MySQL OBDC Connector. |
| === MySQL-specific Syntax === | === MySQL-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. If the statement, [[dev:sql:statements:set_sqlsyntax:home|SET SQLSYNTAX MYSQL]] is issued, then Omnidex SQL will also support these MySQL-specific functions: | + | 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. |
| - | + | ||
| - | * [[dev:sql:functions:chr|CHR]] | + | |
| - | * [[dev:sql:functions:instr|INSTR]] | + | |
| - | * [[dev:sql:functions:new_time|NEW_TIME]] | + | |
| - | * [[dev:sql:functions:nvl|NVL]] | + | |
| - | * [[dev:sql:functions:power|POWER]] | + | |
| - | * [[dev:sql:functions:substr|SUBSTR]] | + | |
| - | * [[dev:sql:functions:sysdate|SYSDATE]] | + | |
| - | * [[dev:sql:functions:systimestamp|SYSTIMESTAMP]] | + | |
| - | * [[dev:sql:functions:sys_extract_utc|SYS_EXTRACT_UTC]] | + | |
| - | * [[dev:sql:functions:to_date|TO_DATE]] | + | |
| - | * [[dev:sql:functions:to_number|TO_NUMBER]] | + | |
| - | + | ||
| - | Other MySQL-specific syntax will cause errors when submitted to Omnidex. In these situations, the statements must be converted to Omnidex SQL. | + | |
| ===== ===== | ===== ===== | ||