Hi to all

One question .. If I create two fields, first with not null and indexed
unique, second field not null. And create Primary Key with frist and
second field with this order. The second field are used for FK with
other tables. First field always get an unique numeric value from one
gen_id. All fields are integer.

When.. I search one record with there fields order. It's most slow ?
What is the correct order for maximize relations/transactions speed with
index ?
I think.. order of fields and order of primary key definition, is not a
problem...
I think.. the system (firebird) use apropiate index for any SQL
transaction.

And I see .. If change order of any index, to "desc", system (firebird)
create the same index table and index data, but neg first all bits. It's
true ? It is good ? If firebird use index with "stack pointers" (first
in first out) .. to create table index and for desc indexes use inverse
"stack pointers" (first in last out) It's not a two index orders ? I
think that. Firebird negate bit to bit, data pointer to search in desc
indexes ? It's for economize length of code ? Same functions for neg
stored data.. I don't know ..

Thanks to all
and Sorry for my English

--
-----------------------------
Aracil Informática
German Aracil Boned