Databases
StackOverflow2013
Postsdbo
POSort Order of Shopify REST Collections
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSort Order of Shopify REST Collections
    primarykey
    data
    text
    <p>Trying to nail down what the sort order is for Shopify's REST collections. Specifically I'm working with orders and customers at the moment.</p> <p>I found this <a href="http://ecommerce.shopify.com/c/ecommerce-design/t/collections-sort-order-3670" rel="nofollow noreferrer">closed thread</a> discussing the ability to sort collections, and the API docs don't mention it at all for either <a href="http://api.shopify.com/order.html" rel="nofollow noreferrer">orders</a> or <a href="http://api.shopify.com/customer.html" rel="nofollow noreferrer">customers</a>.</p> <p>However, customers have a documented search API, which does have an order parameter as an option. I'm not sure whether I can use it as a sort of substitute for the regular list API call. This doesn't seem to work properly for example - it returns more than one result.</p> <pre><code>/admin/customers/search.json?query=&amp;limit=1 </code></pre> <p>Orders don't have a documented search endpoint, but I do get a response when hitting </p> <pre><code>/admin/orders/search.json?query=&amp;limit=1 </code></pre> <p>Although it has the same issues as the customer search endpoint. I found <a href="https://stackoverflow.com/questions/12318899/shopify-api-get-orders-in-shopify-by-date">this thread</a> saying that orders are always returned most recent to newest by date - and inspecting the response I'm getting now that <em>seems</em> to be true although I could have sworn I've seen them come back in a different orders, it almost seems indeterminate.</p> <p>Would like to know if that's the case for sure, and the same for customers. I seem to be getting them returned back in <code>created_at</code> order <em>ascending</em> for customers. Is that always the case?</p> <p>Also, ID's for both customers and orders don't seem to be in <code>created_at</code> order, which is bizzare given that the have the <code>since_id</code> parameter in pretty much all their collections (which I found and promptly built my incremental pulling strategy on top of). I guess I'll have to use <code>created_at</code> instead.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USkalenjordan
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSort Order of Shopify REST Collections
      1. This table or related slice is empty.
      1. VTUpMod
    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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload