This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
admin:lifecycle:development [2009/12/08 04:37] els removed |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== Building Omnidex Applications ====== | ||
| - | |||
| - | [[admin:applications:design|Design]] -> [[admin:applications:prototype|Prototype]] -> **[[admin:applications:development|Development]]** -> [[admin:applications:testing|Testing]] -> [[admin:applications:staging|Staging]] -> [[admin:applications:production|Production]] -> [[admin:applications:optimization|Optimization]] | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== 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. | ||
| - | |||
| - | ==== Application Language ==== | ||
| - | |||
| - | Omnidex supports standard ODBC and JDBC interfaces for interacting with applications. These interfaces allow applications to connect to an Omnidex database, submit queries and issue updates. These interfaces also support statements to build and maintain Omnidex environments. The [[dev:odbc:home|ODBC]] and [[dev:jdbc:home|JDBC]] sections of the documentation describe how to use these languages in your applications. | ||
| - | |||
| - | |||
| - | Omnidex supports lower level API's that can be used if needed. These are mostly used by Omnidex internally and are not frequently used by customers; however, contact Omnidex Technical Support if you would like more information. | ||
| - | |||
| - | Omnidex supports interfaces for Oracle and SQL Server stored procedures. These interfaces allow developers to submit Omnidex queries from within their stored procedures. The [[dev:procedures:home|Stored Procedures]] section of the documentation describes how to develop using these interfaces. | ||
| - | |||
| - | |||
| - | ==== SQL Language ==== | ||
| - | |||
| - | 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. | ||
| - | |||
| - | 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. | ||
| - | |||
| - | Omnidex is often integrated into existing applications. If these applications use non-standard SQL, some change to the application will be necessary. Database-specific extensions, such as SQL Server or Oracle-specific extensions, will need to be changed to their ANSI SQL or Omnidex SQL equivalents. | ||
| - | |||
| - | The [[dev:sql:home|Omnidex SQL Reference]] section of the documentation describes the Omnidex SQL language, including its extensions. | ||
| - | |||
| - | |||
| - | ====== ====== | ||
| - | \\ | ||
| - | ---- | ||
| - | \\ | ||
| - | |||
| - | The next stage in building an Omnidex application is [[admin:applications:testing|Testing]]. | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||