Ambiguous columns when adding shipping_description

[bobbyshaw]

I tried using part of the distributed gridcontrol.xml to add shipping_description to the Sales Order Grid but observed the following error when subsequently trying to filter by status:

Integrity constraint violation: 1052 Column 'status' in where clause is ambiguous, query was: SELECT COUNT(*) FROM `sales_flat_order_grid` AS `main_table`
 INNER JOIN `sales_flat_order` AS `sales/order` ON main_table.entity_id=`sales/order`.entity_id WHERE (status = 'processing')

[mpchadwick]

Ugh. You can't join sales_flat_order because sales_flat_order_grid and sales_flat_order have many of the same columns and filtering doesn't specify which table. This happens when searching by increment_id as well.

[Schrank]

Yea, unfortunately is the solution here to copy the content to the grid table instead of joining it

[mpchadwick]

Maybe it should throw a more human friendly exception if you try to join sales_flat_order to sales_flat_order_grid? This example should probably be eliminated too

https://github.com/magento-hackathon/GridControl/blob/master/src/app/code/community/FireGento/GridControl/etc/gridcontrol.xml.dist#L83

[r-martins]

If we could have an node to update the index name to main_table.status would work.

I had the same problem when filtering by increment_id. I solved by removind and re-adding the column. But would be weird if I need to do it for all collumns.

<real_order_id>
    <remove/>
    <add>
        <type>text</type>
        <header>Order #</header>
        <width>80px</width>
        <index>main_table.increment_id</index>
        <escape>true</escape>
        <renderer>robm_tracking/incrementRenderer</renderer>
    </add>
    <after>massaction</after>
</real_order_id>

[r-martins]

If the above pull request is approved, you can do something like this to solve the issue:

<status>
    <updateColumn>
        <filter_index>main_table.status</filter_index>
    </updateColumn>
</status>