Sender: |
|
Date: |
Mon, 6 May 2002 15:47:07 -0600 |
Reply-To: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
base64 |
Content-Type: |
text/plain; charset="utf-8" |
From: |
|
Comments: |
|
Parts/Attachments: |
|
|
All:
For those folks porting applications to other platforms, DISC is working
with a sister company (called DISC Migration Services) consisting of
former DISC employees who are providing migration consulting and RDBMS
porting assistance to Omnidex customers and are providing a mapping api
that maps the odxfind, dbiopen, etc. calls to the underlying RDBMS calls
and the Omnidex open system calls (OmniAccess) so little to no source
code changes will be needed. The mapping api runs on all the same
platforms and RDBMS that Omnidex supports and will work in conjunction
with porting tools such as the ones offered by Transformix.
And a quick update on our porting status - we have most of the technical
details worked out on making Omnidex work with HP-Eloquence and do plan
on offering Omnidex/HP-Eloquence as a migration option to the Omnidex
customers.
Terry
-----Original Message-----
From: David T Darnell
Sent: Mon 5/6/2002 2:00 PM
To: [log in to unmask]
Cc:
Subject: Re: [HP3000-L] Eloquence + Omnidex (inspired by: HP3000 and
HP-UX)
Right. What Wayne said.
For the systems I am looking at, we probably don't want to do
any redesign
to use only b-tree indexing, and would probably prefer to
continue using
Omnidex "sorted" (b-tree) indexing even though it's available in
Eloquence.
The objective is to port the applications with as few code
changes as
possible, not to make full use of Eloquence features.
And again, the applications I have in mind use at least ten
times the
number of keyword indexes as they use b-tree. They also use
other features
such as "pre-joined" files [index domains] and some soundex.
So, addition
of keyword capability and other Omnidex features is highly
important.
-Dave
"Wayne R. Boyer" <[log in to unmask]>@RAVEN.UTC.EDU> on
05/06/2002 01:20:20
PM
Please respond to [log in to unmask]
Sent by: HP-3000 Systems Discussion <[log in to unmask]>
To: [log in to unmask]
cc:
Subject: Re: [HP3000-L] Eloquence + Omnidex (inspired by:
HP3000 and
HP-UX)
A point to remember though is that if your source code has lots
of Omnidex
type related CALLs, these CALLs stay there until someboy does
something
like
remove them. Thus, the CALLed routines must exist on whatever
platform you
run on even if there might be a better way to do the same
functionality
onthis idfferent platform.
Wayne Boyer
Cal-Logic
* To join/leave the list, search archives, change list settings,
*
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html
*
|
|
|