Martin, el al.,
  I don't know if this has been responded to as yet, but let me bring a few
issues that I'm aware of from the Omnidex side of things:
 
1) The Express-3 version of IMAGE/SQL does know about Third Party Indexes.
 
2) It only supports using SORTED indexes and doesn't use the KEYWORD
indexes.
 
3) It registers (at attach time or TPI ENABLE time) ALL keys (including
keyword/multiple keys)
     This causes a problem because although it registers the
keyword/multiple indexes, it can't use them.  This results in an error -3220
being returned on from a SELECT which tries to use one of these non-sorted
indexes.  The patch for this problem is ATCHXT2 and is version G.G1.08 of
the IMAGESQL program.  The workaround if you're having this problem is the
remove your non-sorted indexes.
 
4) As of last report, HP has not committed to supporting the non-sorted,
keyword or "multiple" indexes.   They are in the process of evaluating this
possibility.
 
Even with these limitations, the Express-3 version of IMAGE/SQL is much
improved.  Not only will it use Sorted Third Party Indexes, but it will use
it's own IMAGE search items.  I noticed a huge performance gain with this
version simply because it wasn't doing serial reads ALL the time.  TPI gives
it much more flexibility and speed.   I think supporting keyword indexes (if
done "correctly" will allow a tremendous performance/flexibility increase
when using 2 or more keyword indexes in the same select.
 
IPROF is coming quickly and NOW is the time to make your desires/wishes
known regarding TurboIMAGE and IMAGE/SQL.  Also the SIGIMAGE Executive
Committee is meeting on February 2nd with HP management to discuss HP's
future direction in light of recent management changes.   All of the members
of the committee regularly monitor and participate in this discussion group.
 Please let us know what you're needs/desires are for IMAGE/SQL.
 
There isn't a SIGOMNIDEX meeting scheduled at IPROF, but I'm assured that if
some (NON-DISC employee (i.e. not me)) wants to lead a meeting, we can sneak
one in during the week.   The SIGOMNIDEX chair is up for grabs.  Any takers?
 
Rich Trapp "RAT"
 
________ Dynamic Information Systems Corp.   |
\!DISC / Rich Trapp                          | My opinions are my own.
 \    /  OMNIDEX Product Manager - IMAGE/SQL | With any luck they're
  \  /   Phone : 303 444-4000                | correct ;-)
   \/    E-mail: [log in to unmask]                |
 ----------------------------------------------------------------------
 ----------
>From: Martin Knapp
>To: Multiple recipients of list HP3000-L
>Subject: More on TPI and IMAGE/SQL
>Date: Tuesday, December 12, 1995 11:18AM
>
>I have followed the thread about Query and TPI, and noticed all those odd
>ways of putting in conditions in order to take advantage of the indexes
>(Superdex in this particular case). Now if my memory does not play me
>false (which it might of course!), the Express 3 release of MPE was
>supposed to make IMAGE/SQL TPI-sensitive. In other words, I should be
>able to submit an SQL Select statement, and IMAGE/SQL would work out
>whether or not to use TPI, and if so how.
>
>All the ways that Bradmark have explained of putting in conditions in
>IMAGE (eg ITEM = "<5") sound a bit iffy to me, if you had to use standard
>SQL to get the same result. Would anyone like to comment on this? What
>will be the limitations of using TPI with SQL access?
>
>Martin Knapp
>