You may see the section named group by optimization on the document.
On Tue, Sep 30, 2008 at 4:44 AM, Rob Wultsch <[EMAIL PROTECTED]> wrote:
> Glancing over things I suggest:
> ALTER TABLE browse_nodes_to_products ADD INDEX(browse_node_id,product_id);
>
> (if product_id has greater cardinality pu
Glancing over things I suggest:
ALTER TABLE browse_nodes_to_products ADD INDEX(browse_node_id,product_id);
(if product_id has greater cardinality put that before browse_node_id)
The syntax:
inner join (browse_nodes, browse_nodes_to_products) on
(browse_nodes.amazon_id = browse_nodes_to_products
Good morning everyone,
products.id is defined as a PRIMARY KEY so it's index.
browse_nodes_to_products.product_id is defined as a INDEX so it's
indexed.
browse_nodes_to_products.browse_node_id is defined as an INDEX so it's
indexed.
browse_nodes.amazon_id is defined as an INDEX so it's index
Hi Eric-
the immediate challenge is to fic the join statement so
make sure products.id is indexed
make sure browse_nodes_to_products.product_id is indexed
make sure browse_nodes_to_products.browse_node_id is indexed
make sure browse_nodes.amazon_id is indexed
there seems to be mapping/relations
