StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13763289
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-07T12:40:09.817
FavoriteCount
0
LastActivityDate
2012-12-07T12:40:09.817
LastEditDate
LastEditorUserId
0
OwnerUserId
1700048
ParentId
13555521
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I am still looking for a good solution myself. But as an approach I would like to contribute my knowledge so far based on Magento 1.7 <ul> <li>I prefer use of <code>setCollection</code> instead of <code>_prepareCollection()</code>. It seems there are less problems with filtering etc. when using <code>setCollection</code></li> <li>The perfect attribute is so close yet so far. shipping_description can be found in <code>sales_order_flat</code>. Unfortunately the default collection is based upon <code>sales_flat_order_grid</code>. One possible solution is to switch this by overwriting <code>_getCollectionClass</code> <pre><code>protected function _getCollectionClass() { //return 'sales/order_grid_collection'; return 'sales/order_collection'; } </code></pre> It's important to say that this leads to other problems. E.g. shipping name and billing name are empty because they got their info from <code>sales_flat_order_grid</code>. We could get them from <code>sales_flat_order_address</code> but I am not sure if this leads to far away from a good solution...</li> <li>Another approach is to join with <code>sales_order_flat</code>. This way we keep all information from <code>sales_flat_order_grid</code> and also can get the <code>shipping_method</code>. Problem here is a count(*) statement that occurs while filtering. The error is about an ambigious <code>increment_id</code>. At the moment I think it is a Magento bug because <code>increment_id</code> should not be used without conjunction to its table. </li> <li>Not to forget a third way: We could extend <code>saled_flat_order_grid</code> and add <code>shipping_method</code>, but I think that would be way to harsh. Dont't touch <code>app/code/core</code> und the tables as long as nobody stands behind you with a gun in his hands ;-)</li> </ul> So far I am still undecided which way to go. Perhaps there is another (better) way that I didn't list here?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMagento (v 1.7.0.2) - Add "Shipping Method" column in Sales Order Grid
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCelldweller
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.