This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
install:releases:odx52:history [2011/04/13 03:32] 127.0.0.1 external edit |
install:releases:odx52:history [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| The following table shows the individual releases of Omnidex 5.2, including their release dates and features. | The following table shows the individual releases of Omnidex 5.2, including their release dates and features. | ||
| + | |||
| |< 60% 40% 60% >| | |< 60% 40% 60% >| | ||
| ^ Release ^ Release Date ^ | ^ Release ^ Release Date ^ | ||
| | [[#5_2_01A|5.2.01A]] | Planned for 2011 | | | [[#5_2_01A|5.2.01A]] | Planned for 2011 | | ||
| + | |||
| \\ | \\ | ||
| Line 40: | Line 42: | ||
| == Omnidex Grids == | == Omnidex Grids == | ||
| - | * Omnidex Grids now allow a new node type called [[admin:features:grids:rollups|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 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 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 [[admin:features:grids:pooling|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 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. |
| == SQL Engine == | == SQL Engine == | ||
| - | * Omnidex now supports [[appendix:reference:dates:timezones:home|timezones]] when working with date-class datatypes. | + | * Omnidex now supports timezones when working with date-class datatypes. |
| * Omnidex now supports the [[dev:sql:functions:getenv:home|$GETENV]] function for referencing environment variables in Omnidex SQL statements. | * Omnidex now supports the [[dev:sql:functions:getenv:home|$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 supports spaces in filenames and directory names throughout the Omnidex product on Microsoft Windows operating systems. | ||
| - | * Omnidex now allows the memory used in the [[admin:optimization:hdc:home|Hashed Data Cache]] to be configured on a per-query basis using the [[dev:sql:statements:select:options#data_cache|DATA_CACHE=]] option. | + | * Omnidex now allows the memory used in the [[admin:optimization:caches:hdc|Hashed Data Cache]] to be configured on a per-query basis using the [[dev:sql:statements:select:options#data_cache|DATA_CACHE=]] option. |
| == Licensing == | == Licensing == | ||
| Line 57: | Line 59: | ||
| == Integration == | == Integration == | ||
| * Omnidex now allows DDL statements to be extracted directly from relational databases using the [[dev:sql:statements:extract|EXTRACT]] SQL statement. This replaces the similar feature that was previously found in the legacy program, OAHELPER. | * Omnidex now allows DDL statements to be extracted directly from relational databases using the [[dev:sql:statements:extract|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[[integration:bi:pentaho:home|Pentaho]] suite of Business Intelligence tools. | + | * Omnidex's JDBC driver has been enhanced to support the Pentaho suite of Business Intelligence tools. |
| == Network Services == | == Network Services == | ||