Re: indexes and hashing

[Atrix Wolfe]

im using version 6.5   unfortunately this column is an accounting number made up of sever fields seperated by dashes.  We use the sget()'s to do things like grab all accounting numbers from a specific location and other such things.  Also,since there are multiple accounting "types" the size and location of the fields varies widely so i dont think we could do the sget() idea although that is a neat idea i hadnt thought of (:   ----- Original Message ----- From: Bernard Lis To: [EMAIL PROTECTED] Sent: Saturday, October 19, 2002 4:37 PM Subject: Re: indexes and hashing What version are you using ? You could create a computed column with (sget( )) Then set your index on the computed col.   Bernie Lis Megabytes, Inc. ----- Original Message ----- From: Atrix Wolfe To: [EMAIL PROTECTED] Sent: Saturday, October 19, 2002 5:46 PM Subject: indexes and hashing hello, im considering setting an index on a text (50) column we have in a table.  We have to do quite a few sget()'s on this column so it runs slow under some circumstances and am looking to speed it up.  My question is 2 fold i guess...first of all...are there other ways besides indexing to speed up such a column?  And my second question is that when i create an index on this column it asks how many of the characters i want to hash and that the rest will be preserved.  I know what hashing is...taking a string of data, putting it through a function and the result is a smaller peice of data (im assuming is used as the index value?) that should be statisticly balanced for random input.  I was wondering though in such a situation is it better to have more of it hashed or less? and in general...what are the pros and cons of hasing more as opposed to less?   Thanx, tryin to expand my r:mind (; -Atrix