AW: defining files with sql but using setll/read to access

bummer

I was just drooling for a join logical with indexes and select/omit based
on fields in all files without that darn dynslt keyword.

(-darn- wasn't my first choice).

Jim

------------------------------

message: 5
date: Fri, 14 Aug 2009 06:16:23 +0200
from: "Birgitta Hauser" <Hauser@xxxxxxxxxxxxxxx>
subject: AW: defining files with sql but using setll/read to access

Hi Vern and Jim,

>>Yeah Jim, I believe so - you don't have a subset of the fields in an
index, as you can with standard logical files.

This is true before release 6.1.

Under release 6.1 it is possible to define indexes with a field selection.
It is even possible to define additional columns, for example a column for
quantity*price or Upper(MyFld). These new columns can also be defined as
key
fields.
... and even more you can specify where conditions within an index just
like
select/omit clauses within logical files.
What is not possible with an index is to build an index over joined
tables,
i.e. there is no replacement for keyed join logical files.

BTW currently these enhancements work with native I/0, while the SQL query
optimizer is not yet able to exploit all these enhancements.

Mit freundlichen Gr??en / Best regards

Jim Horn

This email is intended only for the person or entity
to which it is addressed and may contain information
that is privileged, confidential or otherwise protected
from disclosure. If you are not the named addressee
or an employee or agent responsible for delivering
this message to the named addressee, you are not
authorized to read, print, retain copy, and disseminate
this message or any part of it. If you have received this
message in error please notify us immediately by email,
discard any paper copies and delete all electronic files
of this message.