VIAINDEX usage

Mon, 17 Feb 2003 10:04:52 -0500

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2D695.EC6D1C40
Content-Type: text/plain

For those "historians" out there, many years ago (mid-eighties) we had long
and sometimes heated discussions about how to implement relational support.
We specifically discussed what syntax to use. You're right, using VIAINDEX
is not physically correct. However, in a 4GL, one can argue that it is
logically correct and that it should not matter what the underlying file
system is. I should be able to retrieve the same way and let the 4GL figure
it out.

Now I know that we don't have a perfect or totally consistent solution, but
that's why we use VIAINDEX.

Bob Deskin              
PowerHouse Web Product Manager, Application Development Tools, Cognos Inc. 
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178 
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA 

-----Original Message-----
From: Gordon,Kevin [mailto:Kevin.Gordon@seacontainers.com]
Sent: Monday, February 17, 2003 9:34 AM
To: 'PowerhouseList'
Subject: RE: VIAINDEX usage

To this day I don't understand why ORDERBY was implemented in Qdesign/Quick
but not in Quiz and QDesign. Use of VIAINDEX really shouldn't be necessary
in a relational database environment, but there is no other efficient way of
doing the job, other than creating a ordered view on the database.

Kevin Gordon 
Sea Containers Services Ltd 

-----Original Message----- 
From: Deskin, Bob [  <mailto:Bob.Deskin@cognos> 
Sent: 17 February 2003 14:10
To: 'Peter Bateman'; Roughsedge, Greg N; PowerhouseList
Subject: RE: VIAINDEX usage

Peter is correct and so is your DBA. We take the VIAINDEX and break it down
to the associated columns. We also generate an ORDER BY. It's up to the
database to determine the best retrieval using those columns. So you can use
SORTED.

Bob Deskin              
PowerHouse Web Product Manager, Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178 3755
Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA

-----Original Message-----
From: Peter Bateman [ mailto:shediac92@hotmail.com
<mailto:shediac92@hotmail..com?> ] 
Sent: Monday, February 17, 2003 7:22 AM 
To: Roughsedge, Greg N; PowerhouseList 
Subject: Re: VIAINDEX usage 

Greg: 

When using VIAINDEX PowerHouse I believe 
sends an ORDER BY the segments of the index to 
the database. So you should be able to use SORTED. 

You can check this by using DBAUDIT=FULL 
on your run of PowerHouse. 

Regards, 
Peter Bateman 

----- Original Message ----- 
From: "Roughsedge, Greg N" <Greg.N.Roughsedge@team.telstra.com> 
To: "PowerhouseList" <powerh-l@lists.swau 
Sent: Monday, February 17, 2003 2:41 AM 
Subject: VIAINDEX usage 

> Hi, 
> 
> I would like some clarification around the use of the VIAINDEX clause. 
> 
> Background: 
> Op Sys:        Open VMS V7.1-2 
> Database:      Oracle RDB 7.0-6 
> Powerhouse:  7.10.G1 
> 
> I've used the CHOOSE VIAINDEX <indexname> clause and then assumed that 
> I 
can use the SORTED clause as the records have been retrieved via the named
index. 
> The DBA's believe there is no way to force the retrieval via a 
> specified 
index as the database will determine the most appropriate index and use this
regardless of what's specified. 
> 
> This equally relates to the LINK VIAINDEX clause as well as part of 
> the 
ACCESS statement. 
> 
> My question is, can I be absolutely guaranteed that the VIAINDEX 
> option 
will retrieve records using that index (and consequently know the sequence
of records retrieved). Or, should I not specify the VIAINDEX option and use
SORT instead of SORTED.

> 
> Cheers 
> 
> Greg Roughsedge 
> Media Solutions - Telstra 
> (Black Diamond Technologies) 
> (03) 8696 5968 
> 

****************************************************************************
**
The information contained in this e-mail is confidential. 
It may also be protected by legal privilege. 
It is intended only for the stated addressee(s). 
If you are not an addressee you must not disclose, copy, circulate nor use
the information contained in it. 
If you have received this e-mail in error please inform the sender
immediately and delete it and any copies from your system.
****************************************************************************
**

This message may contain privileged and/or confidential information.  If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.  Thank you.

------_=_NextPart_001_01C2D695.EC6D1C40
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<TITLE>RE: VIAINDEX usage</TITLE>

<META content=3D"MSHTML 5.50.4919.2200" name=3DGENERATOR></HEAD>
<BODY>
<DIV>For=20
those "historians" out there, many years ago (mid-eighties) we had long =
and=20
sometimes heated discussions about how to implement relational support. =
We=20
specifically discussed what syntax to use. You're right, using VIAINDEX =
is not=20
physically correct. However, in a 4GL, one can argue that it is =
logically=20
correct and that it should not matter what the underlying file system =
is. I=20
should be able to retrieve the same way and let the 4GL figure it=20
out.</DIV>
<DIV><SPAN=20
class=3D027190115-17022003>&nbsp;</DIV>
<DIV>Now I=20
know that we don't have a perfect or totally consistent solution, but =
that's why=20
we use VIAINDEX.</DIV>
<DIV><SPAN=20
class=3D027190115-17022003>&nbsp;</DIV>
<DIV>
Bob=20
Deskin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;=20
 PowerHouse Web Product Manager, =
Application=20
Development Tools, Cognos Inc. bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) =
727-1178=20
 3755 Riverside Drive P.O. Box 9707 Stn. =
T, Ottawa ON=20
K1G 4K9 CANADA </DIV>
<BLOCKQUOTE>
 <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft>-----Original Message----- From: Gordon,Kevin=20
 [mailto:Kevin.Gordon@seacontainers.com] Sent: Monday, =
February 17,=20
 2003 9:34 AM To: 'PowerhouseList' Subject: RE: =
VIAINDEX=20
 usage </DIV>
 To this day I don't understand why ORDERBY was =
implemented in=20
 Qdesign/Quick but not in Quiz and QDesign. Use of VIAINDEX really =
shouldn't be=20
 necessary in a relational database environment, but there is no other =

efficient way of doing the job, other than creating a ordered view on =
the=20
 database.
 Kevin Gordon Sea =
Containers Services=20
 Ltd 
 -----Original Message----- From:=20
 Deskin, Bob [<A=20
 href=3D"mailto:Bob.Deskin@cognos Sent: 17 February =
2003 14:10 To: 'Peter Bateman'; Roughsedge, =
Greg N; PowerhouseList Subject: RE: VIAINDEX =
usage Peter is correct and so is your =
DBA. We take the VIAINDEX and break it down to the associated columns. =
We also generate an ORDER BY. It's up to the database to determine the =
best retrieval using those columns. So you can use =
SORTED.Bob =
Deskin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; PowerHouse Web Product Manager, =
Application Development Tools, Cognos Inc. bob.deskin@cognos.com (613) =
738-1338 ext 7268 FAX: (613) 727-1178 3755 Riverside Drive P.O. Box =
9707 Stn. T, Ottawa ON K1G 4K9 CANADA-----Original Message----- From: =
Peter Bateman [<A HREF=3D"=20
 =
mailto:shediac92@hotmail..com?>mailto:shediac92@hotmail.com</A>] =

Sent: Monday, February 17, 2003 7:22 AM =
 <FONT=20
 size=3D2>To: Roughsedge, Greg N; PowerhouseList Subject:=20
 Re: VIAINDEX usage 
 Greg: 
 When using VIAINDEX PowerHouse I believe =
 <FONT=20
 size=3D2>sends an ORDER BY the segments of the index to =
 <FONT=20
 size=3D2>the database. So you should be able to use SORTED. =

 You can check this by using DBAUDIT=3DFULL =
 <FONT=20
 size=3D2>on your run of PowerHouse. 
 Regards, Peter =
Bateman 
 ----- Original Message ----- From:=20
 "Roughsedge, Greg N" =
&lt;Greg.N.Roughsedge@team.telstra.com&gt;=20
 To: "PowerhouseList" &lt;powerh-l@lists.swau =
 <FONT=20
 size=3D2>Sent: Monday, February 17, 2003 2:41 AM <FONT=20
 size=3D2>Subject: VIAINDEX usage 
 &gt; Hi, &gt; =
 <FONT=20
 size=3D2>&gt; I would like some clarification around the use of the =
VIAINDEX=20
 clause. &gt; &gt; =

  Background:</FONT> <BR><FONT size=3D2>&gt; Op=20
  Sys:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Open VMS V7.1-2</FONT> =

&gt; Database:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Oracle RDB=20
 7.0-6 &gt; Powerhouse:&nbsp; 7.10.G1 =
 <FONT=20
 size=3D2>&gt; &gt; I've used the CHOOSE =
VIAINDEX=20
 &lt;indexname&gt; clause and then assumed that &gt;=20
 I can use the SORTED clause as the records =
have been=20
 retrieved via the named index. &gt; The =
DBA's believe=20
 there is no way to force the retrieval via a &gt;=20
 specified index as the database will =
determine the=20
 most appropriate index and use this regardless of what's =
specified.=20
 &gt; &gt; This equally =
relates to the=20
 LINK VIAINDEX clause as well as part of &gt;=20
 the ACCESS statement. <FONT=20
 size=3D2>&gt; &gt; My question is, can I be =
absolutely=20
 guaranteed that the VIAINDEX &gt; =
option=20
 will retrieve records using that index (and =
consequently know=20
 the sequence of records retrieved). Or, should I not specify the =
VIAINDEX=20
 option and use SORT instead of SORTED.
 &gt; &gt; Cheers =
 <FONT=20
 size=3D2>&gt; &gt; Greg Roughsedge =
 <FONT=20
 size=3D2>&gt; Media Solutions - Telstra &gt; (Black=20
 Diamond Technologies) &gt; (03) 8696 =
5968=20
 &gt; <CODE><FONT=20
 =
size=3D3> *******************************************************=
*********************** The=20
 information contained in this e-mail is confidential. It may also =
be=20
 protected by legal privilege. It is intended only for the stated=20
 addressee(s). If you are not an addressee you must not disclose, =
copy,=20
 circulate nor use the information contained in it. If you have =
received=20
 this e-mail in error please inform the sender immediately and delete =
it and=20
 any copies from your=20
 =
system. *************************************************************=
***************** </BLOCKQUOTE></CODE></BODY></HTML>

This message may contain privileged =
and/or confidential information. If you have received this e-mail in =
error or are not the intended recipient, you may not use, copy, =
disseminate or distribute it; do not open any attachments, delete it =
immediately from your system and notify the sender promptly by e-mail =
that you have done so. Thank you.

------_=_NextPart_001_01C2D695.EC6D1C40--