--- Andrew Piskorski <[EMAIL PROTECTED]> wrote: > That seems bizarre. Typical RDBMS practice would be > to just use a > two-column composite primary key. > > > Did you measure a serious performance problem when > joining on two > separate columns? >
You're right. It feels bizarre to me too. And no, I haven't measured the performance - I still have much development to do. It just seems that with as many as ten thousand item in each of these tables, it would be much quicker to create this "combinedID" rather than select the item from a table based on comparing ID's from two other tables individually. By combining the 2 4-byte ID's, I can create a unique 8-byte ID which should be accessed quicker. I might be wrong. My application isn't a normal query type of application and will be doing as many as 500 of these operations based on something that a user requests. Thanks for your feedback. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
