This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:admin:applications:development [2011/01/10 19:11] els |
admin:admin:applications:development [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| Line 6: | Line 8: | ||
| ===== Building Omnidex Applications ===== | ===== Building Omnidex Applications ===== | ||
| - | [[admin:admin:applications:design|Design]] -> [[admin:admin:applications:prototype|Prototype]] -> **[[admin:admin:applications:development|Development]]** -> [[admin:admin:applications:testing|Testing]] -> [[admin:admin:applications:staging|Staging]] -> [[admin:admin:applications:production|Production]] -> [[admin:admin:applications:optimization|Optimization]] | + | [[admin:admin:applications:design|Design]] | [[admin:admin:applications:prototype|Prototype]] | **[[admin:admin:applications:development|Development]]** | [[admin:admin:applications:testing|Testing]] | [[admin:admin:applications:staging|Staging]] | [[admin:admin:applications:production|Production]] | [[admin:admin:applications:optimization|Optimization]] |
| ---- | ---- | ||
| Line 12: | Line 14: | ||
| ==== Development ==== | ==== Development ==== | ||
| - | Development of Omnidex applications is remarkable straightforward. Most business access Omnidex databases using a standard ODBC or JDBC interface, and integration of Omnidex can be as simple as changing the connection string to point to Omnidex. Omnidex uses ANSI SQL as its base language, but also has a number of extensions to support features like fuzzy searches and geographical searches. | + | Development of Omnidex applications is remarkably straightforward. Most businesses access Omnidex databases using a standard ODBC or JDBC interface, and integration of Omnidex can be as simple as changing the connection string to point to Omnidex. Omnidex uses ANSI SQL as its base language, but also has a number of extensions to support features like fuzzy searches and geographical searches. |
| === Application Language === | === Application Language === | ||
| Line 28: | Line 30: | ||
| Omnidex uses the SQL language for connecting, querying, updating and maintaining Omnidex databases. Omnidex uses ANSI-standard SQL as its base language, and also has extensions to support Omnidex-specific features such as fuzzy searches and geographic searches. | Omnidex uses the SQL language for connecting, querying, updating and maintaining Omnidex databases. Omnidex uses ANSI-standard SQL as its base language, and also has extensions to support Omnidex-specific features such as fuzzy searches and geographic searches. | ||
| - | Omnidex includes a SQL optimizer that evaluates the SQL statements and automatically uses Omnidex indexes to improve performance. Omnidex can generally determine the best optimization for a given statement, but Omnidex also provides configuration settings and options that allow some control over the optimization approaches. | + | Omnidex includes a SQL optimizer that evaluates the SQL statements and automatically uses Omnidex indexing to improve performance. Omnidex can generally determine the best optimization for a given statement, but Omnidex also provides configuration settings and options that allow some control over the optimization approaches. |
| Standard SQL allows developers to select against tables and columns without references to the indexes. This allows administrators to add and remove indexes without requiring changes to the application. Omnidex encourages developers to use standard SQL for this reason; however, Omnidex also provides additional statements for directly accessing the Omnidex indexes. | Standard SQL allows developers to select against tables and columns without references to the indexes. This allows administrators to add and remove indexes without requiring changes to the application. Omnidex encourages developers to use standard SQL for this reason; however, Omnidex also provides additional statements for directly accessing the Omnidex indexes. | ||
| Line 37: | Line 39: | ||
| - | ===== ===== | + | ==== ==== |
| **[[admin:admin:applications:prototype|Prev]]** | **[[admin:admin:applications:testing|Next]]** | **[[admin:admin:applications:prototype|Prev]]** | **[[admin:admin:applications:testing|Next]]** | ||