HP3000-L Archives

December 1995, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Larry Boyd <[log in to unmask]>
Reply To:
Larry Boyd <[log in to unmask]>
Date:
Tue, 12 Dec 1995 10:55:05 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
Martin Knapp wrote:
>
>(snip)
> 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?
 
I haven't had a chance to verify this yet in the IMAGE/SQL code, however,
I believe the original concept was that an "ITEM < 5" select in IMAGE/SQL
will convert the DBFIND to ITEM = "<5".
 
The primary limitation to TPI/SQL will be keywording/relational access.
Only DBFIND mode 1 lookups will be provided on "Generic" index types.
 
--------------------------------------------------
Larry Boyd    <[log in to unmask]>

ATOM RSS1 RSS2