Re: SQL Query Scalar Function Versus Second Table

Should it be not more sensible to have one record for the item?

I would test the users' entry to be consistent with the data in the database. 
Now you are creating inconsistent data with redundancy in the tables as well.

On another note:
Why not using XLATE? The user enters A123300 (and let them enter it without 
dashes) and the XLATE makes it A-123-300 (assuminf all items have the same 
format).

The translate constants should be 'ABCDEFG' and 'A-BCD-EFG' respectively, and 
do the translation in the programme. The statement should be something like, 
top of my head:

C                    Input:Const1     XLATE Const2             Result

See the manuals for the exact statement. 

Regards,
Carel Teijgeler


*********** REPLY SEPARATOR  ***********

On 19-8-05 at 14:15 Narayanan R Pillai wrote:

>That is correct, There is only one part ( A-123-300 ). The users enter 
>that as A-123300 or A123300 and we need to be able to match it to A-123-300.
>
>My concern really is that building an index on replace( part, '-', '' ) 
>might impact performance, and not building it might impact the query. 
>D**d if I do, D**d if I don't :/