Each new version of Omnidex brings a collection of improvements, from new features to increased performance. Here are the primary features and enhancements in the major releases of Omnidex:

The following table shows the individual releases of Omnidex 5.2, including their release dates and features.

Release is planned for 2011, and will be available on both Microsoft Windows and Linux.

• Omnidex now supports, real-time connection and query monitoring.

• Omnidex now supports AutoComplete, a feature that allows applications to display relevant choices and their counts as the user types characters into a search field.

• Omnidex now provides broad support for connection strings throughout the product. Connection string provide a simple and universal way of connecting to an Omnidex Environment File.

• Omnidex Grids now allow a new node type called Rollup Nodes that are used to support Omnidex Rollup Tables that span all nodes. Customers that have previously used Unpartitioned Nodes for this purpose should switch to Rollup Tables to improve the performance of building indexes.
• Omnidex Grids now support an UNINDEXED option within the NODE clause of the CREATE TABLE statement. This clause indicates that the table should not be indexed for a particular node. This is often used in Rollup Nodes to avoid the indexing of the tables that underlay rollup tables.
• Omnidex Grids now support Grid Connection Pooling, designed specifically for a grid environment. Connection pooling supports a grid by intelligently obtaining and releasing connections to the nodes in a common pool, increasing performance and reduces resource usage.

• Omnidex now supports timezones when working with date-class datatypes.
• Omnidex now supports the $GETENV function for referencing environment variables in Omnidex SQL statements.
• Omnidex now supports spaces in filenames and directory names throughout the Omnidex product on Microsoft Windows operating systems.
• Omnidex now allows the memory used in the Hashed Data Cache to be configured on a per-query basis using the DATA_CACHE= option.

• Omnidex now supports three product editions.
• Support for three editions of Omnidex: Omnidex Enterprise Edition, Omnidex Developer Edition and Omnidex Trial Edition.
• Omnidex licensing has been streamlined through three new commands in OdxSQL: REQUEST LICENSE, REGISTER LICENSE, and SHOW LICENSE. These commands are also discussed in the guide to Omnidex Licensing.

• Omnidex now allows DDL statements to be extracted directly from relational databases using the EXTRACT SQL statement. This replaces the similar feature that was previously found in the legacy program, OAHELPER.
• Omnidex's JDBC driver has been enhanced to support the Pentaho suite of Business Intelligence tools.

• Omnidex now supports options to allow Omnidex Network Services to terminate existing processes without having to completely restart the service.

• In the 5.x releases of Omnidex, the product is being simplified and streamlined. As part of that effort, the following changes have been made.
  • The acronym TDF, standing for Tab-Delimited Files, was used throughout the product to reference delimited files. This mnemonic has been changed to DELIMITED, though TDF is still an accepted synonym for backward compatibility.
  • The FLATFILE database type within the CREATE DATABASE statement has been change to FILE, though FLATFILE is still a supported synonym for backward compatibility.
  • The C STRING datatype has been changed to STRING, though C STRING is still a supported synonym for backward compatibility.
  • The name used for the Omnidex ODBC driver, which has been “DISC OMNIDEX OdxNet Driver”, has been changed to “Omnidex”. Both names can be registered for backward compatibility using the ODBCReg utility.
  • The NODE clause within the CREATE ENVIRONMENT statement now uses ConnectionString rather than Environment for specifying remote node locations.
  • The optimization setting MDK_RETRIEVAL_THRESHOLD has been changed to QUALIFICATION_THRESHOLD, though MDK_RETRIEVAL_THRESHOLD is still a supported synonym for backward compatibility.
  • The optimization setting ASK_RETRIEVAL_THRESHOLD has been changed to AGGREGATION_THRESHOLD, though ASK_RETRIEVAL_THRESHOLD is still a supported synonym for backward compatibility.

See also: