Definitely yes. A, D, I, S and SQL index types are all supported by UniVerse.
You only need to look at the LIST.INDEX report to see that.
- Original Message -
From: "Marc Harbeson" <[EMAIL PROTECTED]>
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Double Indexes
D
> From: Marc Harbeson
> What about an index on an I-DESC? (Does universe do that?)
Yes.
Virtual attribute is another name for I-descriptor, UniData's term
mostly.
See Scott Ballinger's earlier post on thist thread & here is a repost of
part of my own answer:
> From: Stevenson, Charles
> Sent: T
Sorry, are you talking about U2 or D3? I don't think I-Types work to well
on D3.
Mark:
I have done a lot of indexing on I-Type items. I have had no problems with
the indexing, it just works, solid.
The thing you have to be careful of is indexing on translates. Once you
think about it the pr
, October 21, 2005 4:03 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Double Indexes
I putzed around with correlative-based indexed fields and got a lot of
errmsg static. I'll try your suggestions.
I'm trying to use the system instead of maintain manual xref files. This
system is cramm
What about an index on an I-DESC? (Does universe do that?)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Johnson
Sent: Friday, October 21, 2005 5:03 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Double Indexes
I putzed around with
guarantee not being perfect.
Thanks.
- Original Message -
From: "Scott Ballinger" <[EMAIL PROTECTED]>
To:
Sent: Friday, October 21, 2005 11:42 AM
Subject: RE: [U2] Double Indexes
> [snip]
> >Does U2 support indexing virtual fields, ie DATE.CUST? I don't
eadv'd
within a subroutine to get the specific CUST. Thus the DATE index remained.
The users seemed happy with this approach. It ended up being around 15
seconds at best.
Thanks.
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Friday, October 21, 2005 2:43 AM
Subject: Re: [U2
[snip]
>Does U2 support indexing virtual fields, ie DATE.CUST? I don't think D3
can.
Sure, both U2 and D3 support virtual index fields.
U2 I type:
CUST:".":DATE
One caveat I know of is that in D3 you must use A-correlatives to define
the index, e.g.
Cust.date:
a5:".":6
Or
A0(call cust.date)
C
2
[EMAIL PROTECTED] wrote: -
>To:
>From: "Mark Johnson"
>Sent by: [EMAIL PROTECTED]
>Date: 21/10/2005 13:50
>Subject: [U2] Double Indexes
>
>I'm wondering if a UD or UV system behaves similarly to a D3 problem
>I see.
>
On UV I believe there were some optimizations at rel 10.0 and it will
use both indexes and take the intersection.
Use EXPLAIN keyword to see what's going on.
Before then, and maybe still on UD(??) it is as you described.
A good workaround is:
SELECT FILE WITH DATE = "10.18" TO 1
SELECT FIL
Goo'day Mark,
At 23:50 20/10/05 -0400, you wrote:
I'm wondering if a UD or UV system behaves similarly to a D3 problem I see.
File contains 6,000,000 records. First field is DATE and 2nd field is CUST.
Both are INDEXed.
SELECT FILE WITH DATE = "10.18"
quickly returns 11,000 items
CLEARSELECT
I'm wondering if a UD or UV system behaves similarly to a D3 problem I see.
File contains 6,000,000 records. First field is DATE and 2nd field is CUST.
Both are INDEXed.
SELECT FILE WITH DATE = "10.18"
quickly returns 11,000 items
CLEARSELECT
SELECT FILE WITH CUST = "12345"
quickly returns 180,00
12 matches
Mail list logo
