The following is a list of fixes and enhancements for Omnidex organized by the release.
OdxSQL no longer requires Windows file specifications to be escaped when using a connection string. Prior to 5.01.01G, the following syntax was required when using Windows filespecs and connection strings:
odxsql> connect [localhost:7555]c:\\dev\\odx\\myodx.xml;
Now the following syntax is allowed:
odxsql> connect [localhost:7555]c:\dev\odx\myodx.xml;
Fixes to OdxNet to better handle network processing across a grid.
Known Problems:
NsAdmin does not work.
odxnet -admin option is not currently active.
odxnet -nodaemon option is disabled.
As of the 5.01.01F release, the Index Directory option of the CREATE DATABASE no longer uses the index direction option and will instead create the directory if they do not already exist in the OS. Existing DDL may have to be modified if they are using the Index_Directory/Index_Prefix option.
Omnidex Index is a MDK index with the NP and NE options. QuickText Index is a MDK index with the KW option. FullText Index is a MDK index.
As of Omnidex 5.1 XML Environments are the preferred approach over the legacy Omnidex Environment Catalogs using the original OmniAccess Environment syntax and compiled with oacomp. With 5.1, XML Environments can be more easily maintained with the OdxSQL using the DDL CREATE statements. The new Omnidex Environment file is stored in the common XML format.