[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 757
  • Last Modified:

4 table Join - Eliminate repeating rows

I am trying to show customer name and address together with the products they purchased. Including product attributes (color etc.).
Example
Joe Rabbitte, 1- Hopper Ave,
1 - Wolly jumper - Red,
2 - Wolly Socks - white
(count removed for clarity)


This query works fine with the first two joins but returns the products twice in the products_column when the third join is added.

Joe Rabbitte, 1- Hopper Ave,
1- Wolly jumper - Red,
1- Wolly jumper - Red,
2- Wolly Socks - white,
2- Wolly Socks - white,

I'm stuck has anyone any ideas on what I am doing wrong?
SELECT customers_name, customers_telephone, 
GROUP_CONCAT(products_name, ' ', LEFT(products_options_values, 4) SEPARATOR ' - ') AS products_bought
FROM orders
LEFT JOIN orders_products ON orders.orders_id = orders_products.orders_id
LEFT JOIN cc ON orders_products.orders_id = cc.order_id
LEFT JOIN orders_products_attributes ON cc.order_id = orders_products_attributes.orders_id
WHERE cc.payment_status = 'completed' AND orders.orders_id >10000
 
GROUP BY customers_name

Open in new window

0
fearialtog
Asked:
fearialtog
3 Solutions
 
mahomeCommented:
This will happen if you have 2 rows in orders_products_attributes per order id.
0
 
yousaftahirCommented:
use distinct to get the distinct rows.
0
 
pellepCommented:
Using "distinct" is an option, but keep in mind that it's a very, very expensive operation, especially in your case where you construct the result by formula and strings. Basically, it has the compare each row returned lexigraphically with the current list of results. If your query returns even a medium sized resultset, you will likely see a significant performance-impact.

Agreeing with mahome, it seems this is more of an issue of data than query. For some reason, there appears to be two (or more) rows in the orders_products_attributes table for each order, even if the rows represent the same data (assuming here that the products_options_values column comes from the orders_products_attributes table). Either this is not intended, in which case it should be fixed and your query should run fine. If it IS intended than you may end up having to use distinct or dropping the orders_products_attributes portion from the query.

This is one of the inherent downsides to a normalized model and this pattern of attributes storage you're using - it makes this type of query more problematic.
0
 
fearialtogAuthor Commented:
Thank you all for your help
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now