Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Recent content by benknight
-
SQL for Customers Who Bought This Item Also Bought
No worries at all... we have a column called "title", so that was an easy swap :-) I already tested the code thoroughly, checked it into subversion and deployed the new app. Thanks again. Have a great weekend! -
SQL for Customers Who Bought This Item Also Bought
Wow, r937! Not only does my query generate invalid results but your query is accurate and runs lightning fast! I created 5000 test records and your query ran as follows: 108 rows in set (0.06 sec) Here is what my (invalid) version did :-( 999 rows in set (5.65 sec) I... -
SQL for Customers Who Bought This Item Also Bought
Thanks again. books_read.id is a "surrogate" key required by our ORM package. id "1" is simply the id of the current user that is not logged in (which in this case is my test id) -- I do this since we are trying to show members what "other" members are reading, I added that check in there... -
SQL for Customers Who Bought This Item Also Bought
Thanks, r937. However, what I really need help with is the actual query. For starters, we have "members" who "read books," and we would like these members to know what other members are reading. So, we have a table called "books" which contains info about the books (unique key column: id)... -
SQL for Customers Who Bought This Item Also Bought
Hello. We need to develop a feature very similar to Amazon's "Customers Who Bought This Item Also Bought" feature. I'm looking for suggestions on best ways to handle this, via real-time using the actual table or a periodic process that updates a different table (e.g. nightly). Any...
