At 6:06 AM -0500 9/15/99, Matthias Urlichs wrote:
>> Nope the primary key is something else
>> But i don't want to do select on this too often so will it be wise to
>> of indexes ?
>That depends on how dynamic the table is and how often you'd want to do
>such a query.
>> If i add more indexes to the table wont it make it slower and heavier
>Indices slow things down, but not so much that you'd notice, IF you have
>enough RAM to keep the common stuff in memory.
Can you explain what you mean by saying that indexes slow things down?
>Case in point, we have a two-million-records accounting database here,
>indexed by a zillion and one field in various combinations. I haven't
>really noticed any slowdown since the times it was at ten thousand records
>with two indices. On the contrary, we're hashing the seven fields
>which would make up the primary index into a new key (with duplicates
>allowed, of course) and have noticed a 30% speedup for inserts and updates.
>(We only update non-indexed fields.)
>Matthias Urlichs | noris network GmbH | smurf@stripped | ICQ: 20193661
>The quote was selected randomly. Really. | http://www.noris.de/~smurf/
>If I can have honesty, it's easier to overlook mistakes.
> -- Kirk, "Space Seed," stardate 3141.9
Paul DuBois, paul@stripped