RE: disabling QueryElevationComponent

2012-03-05 Thread Welty, Richard
Walter Underwood [mailto:wun...@wunderwood.org] writes: >On Mar 5, 2012, at 1:16 PM, Welty, Richard wrote: >> Walter Underwood [mailto:wun...@wunderwood.org] writes: >>> You may be able to have unique keys. At Netflix, I found that there were >>> collisions between the movie IDs and the person

Re: disabling QueryElevationComponent

2012-03-05 Thread Walter Underwood
On Mar 5, 2012, at 1:16 PM, Welty, Richard wrote: > Walter Underwood [mailto:wun...@wunderwood.org] writes: > >> You may be able to have unique keys. At Netflix, I found that there were >> collisions between >the movie IDs and the person IDs. So, I put an 'm' at >> the beginning of each movie I

RE: disabling QueryElevationComponent

2012-03-05 Thread Welty, Richard
Walter Underwood [mailto:wun...@wunderwood.org] writes: >You may be able to have unique keys. At Netflix, I found that there were >collisions between >the movie IDs and the person IDs. So, I put an 'm' at the >beginning of each movie ID and a >'p' at the beginning of each person ID. Like >ma

Re: disabling QueryElevationComponent

2012-03-05 Thread Walter Underwood
You may be able to have unique keys. At Netflix, I found that there were collisions between the movie IDs and the person IDs. So, I put an 'm' at the beginning of each movie ID and a 'p' at the beginning of each person ID. Like magic, I had unique IDs. You should be able to disable the query el