Posted by Doug on 10/01/03 11:41

>(but the ID field is still a poor crutch for a possibly weak design.)

hmmmm. i'd prefer to think of it as the table stores ALL hits to the
table, but this particular data consumer only wants to see ONE. The
way I think about it, your natural key would be the composite of all
fields in the table; perhaps "natural", but certainly awkword.

I like figital's solution.

• Next in forum: Re: MSSQL Query Memory when using long fields
• Prev in forum: Re: Problem with variable of type money?
• Thread view: Re: How can I remove duplicate entries in a sql query?

[Reply to this message]