I never create any compount indexes, instead I would create 2 indexes, then
you can specifiy the order individually for each. Then the optimizer usually
picks the correct ones in teh correct order.

Rich P...

-----Original Message-----
From: Michael Weissenbacher [mailto:MWeissenbacher@...]
Sent: 12 August 2002 10:55
To: 'ib-support@yahoogroups.com'
Subject: [ib-support] RE: indexes are one way streets


well, this is the problem: this does not work. one can specify ascending or
descending only at the beginning like in:
create descending index myindex on people (first_name, birthday)
but not for every part of the index seperately.
any ideas/comments?

michael weissenbacher

-----Original Message-----
From: Nando Dessena [mailto:nandod@...]
Sent: Monday, August 12, 2002 11:14 AM
To: ib-support@yahoogroups.com
Subject: Re: indexes are one way streets (was: RE: [ib-support] Speed on
select with order by ......)


Michael,

> i have some question about this "one-way" streets:
> what do i do if for example i want to order persons by their first name
> ascending and by their birthday descending. if i want to create a
> multi-column index for this it can't be ascending and also not descending.

create index myindex on people (first_name, birthday desc)

Not sure about the syntax, but it should be something like that.
I don't think Paul meant that multicolumn indexes cannot have a
direction specified for each segment, when he said that indexes are one
way streets; just that their use in queries must match the directions in
their definitions (unlike what happens with other RDBMSs).
Ciao
--
____
_/\/ando


To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/