This shows you the differences between two versions of the page.
|
integration:rdbms:oracle:updates [2011/04/04 17:31] deb |
integration:rdbms:oracle:updates [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Integration: Relational Databases ====== | ||
| - | |||
| - | ===== Oracle ===== | ||
| - | |||
| - | [[integration:rdbms:oracle:home|Overview]] | | ||
| - | [[integration:rdbms:oracle:environments|Environments]] | | ||
| - | [[integration:rdbms:oracle:databases|Databases]] | | ||
| - | [[integration:rdbms:oracle:tables|Tables]] | | ||
| - | [[integration:rdbms:oracle:constraints|Constraints]] | | ||
| - | [[integration:rdbms:oracle:datatypes|Datatypes]] | | ||
| - | [[integration:rdbms:oracle:queries|Queries]] | | ||
| - | **[[integration:rdbms:oracle:updates|Updates]]** | | ||
| - | [[integration:rdbms:oracle:example|Example]] | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Updates ==== | ||
| - | |||
| - | Omnidex is primarily designed for read-only databases. Most Omnidex applications will place tens or hundreds of indexes on a table, and this makes online updates impractical. Omnidex does support limited online updates using the INSERT, DELETE, and UPDATE statements; however, these should only be used for low-volume updates on lightly-indexed tables. | ||
| - | |||
| - | Most Omnidex applications refresh the data at regular intervals such as daily, weekly or monthly. Once the data is refreshed, the indexes are rebuilt, producing an indexed version of the new data. This data can then be deployed into production. | ||
| - | |||
| - | For applications that require online updates, applications can use INSERT, DELETE and UPDATE statements to update the table. This approach immediately updates both the database and the Omnidex indexes. Alternatively, Omnidex allows Oracle triggers to be installed on a table that copies changes to a separate transaction table. The [[programs:odxaim:home|OdxAIM]] tool can then run in the background, updating the Omnidex indexes with these transactions. This approach preserves transactional integrity, though there is a short delay between the updates of the database and the indexes. | ||
| - | |||
| - | |||
| - | ===== ===== | ||
| - | |||
| - | **[[integration:rdbms:oracle:queries|Prev]]** | | ||
| - | **[[integration:rdbms:oracle:example|Next]]** | ||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | |||
| - | See also: | ||
| - | |||
| - | {{page>:integration:rdbms:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||