添加链接
link之家
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接
相关文章推荐
yxchen1962  ·  Distinct Localization ...·  3 年前    · 
天涯  ·  count(distinct) ...·  4 年前    · 
鼻子大的肉夹馍  ·  WPF 按钮 Button 的 ...·  1 年前    · 
乐观的小笼包  ·  Azure Spatial Anchors ...·  1 年前    · 
冷静的米饭  ·  svg text align center-掘金·  1 年前    · 
Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

I want to run this query:

SELECT DISTINCT ON (address_id) purchases.address_id, purchases.*
FROM purchases
WHERE purchases.product_id = 1
ORDER BY purchases.purchased_at DESC

But I get this error:

PG::Error: ERROR: SELECT DISTINCT ON expressions must match initial ORDER BY expressions

Adding address_id as first ORDER BY expression silences the error, but I really don't want to add sorting over address_id. Is it possible to do without ordering by address_id?

my order has purchase because i want it, but postgres also asks for address(see error message). – sl_bug Mar 20, 2012 at 22:03 Fully answered here - stackoverflow.com/questions/9796078/… Thanks to stackoverflow.com/users/268273/mosty-mostacho – sl_bug Dec 21, 2012 at 23:40 Personally I think requiring DISTINCT ON to match ORDER BY is very questionable, as there are a variety of legitimate use cases for having them differ. There is a post on postgresql.uservoice trying to change this for those who feel similarly. postgresql.uservoice.com/forums/21853-general/suggestions/… – semicolon Jul 16, 2019 at 21:37 got the exact same issue, and facing the same limtation. At the moment I have broken it into a sub-query and then ordering, but it feels dirty. – Guy Park Oct 24, 2019 at 6:30

DISTINCT ON ( expression [, ...] ) keeps only the first row of each set of rows where the given expressions evaluate to equal. [...] Note that the "first row" of each set is unpredictable unless ORDER BY is used to ensure that the desired row appears first. [...] The DISTINCT ON expression(s) must match the leftmost ORDER BY expression(s).

Official documentation

So you'll have to add the address_id to the order by.

Alternatively, if you're looking for the full row that contains the most recent purchased product for each address_id and that result sorted by purchased_at then you're trying to solve a greatest N per group problem which can be solved by the following approaches:

The general solution that should work in most DBMSs:

SELECT t1.* FROM purchases t1
JOIN (
    SELECT address_id, max(purchased_at) max_purchased_at
    FROM purchases
    WHERE product_id = 1
    GROUP BY address_id
ON t1.address_id = t2.address_id AND t1.purchased_at = t2.max_purchased_at
ORDER BY t1.purchased_at DESC

A more PostgreSQL-oriented solution based on @hkf's answer:

SELECT * FROM (
  SELECT DISTINCT ON (address_id) *
  FROM purchases 
  WHERE product_id = 1
  ORDER BY address_id, purchased_at DESC
ORDER BY purchased_at DESC

Problem clarified, extended and solved here: Selecting rows ordered by some column and distinct on another

It works, but gives wrong ordering. That's why i want to get rid of address_id in order clause – sl_bug Mar 20, 2012 at 22:12 If you need to order by purchases.purchased_at, you can add purchased_at to your DISTINCT conditions: SELECT DISTINCT ON (purchases.purchased_at, address_id). However, two records with the same address_id but different purchased_at values will result in duplicates in the returned set. Make sure you are cognizant of the data you're querying. – Brendan Benson Jan 26, 2015 at 21:44 The spirit of the question is clear. No need to pick on semantics. It's sad that the accepted and most voted answer doesn't help you solve the problem. – ichigolas Apr 7, 2017 at 22:39 Here is a postgresql.uservoice post trying to lift this limitation for those that agree it is a questionable limitation. postgresql.uservoice.com/forums/21853-general/suggestions/… – semicolon Jul 16, 2019 at 21:40 ORDER BY purchased_at DESC;

Leading expressions in ORDER BY have to agree with columns in DISTINCT ON, so you can't order by different columns in the same SELECT.

Only use an additional ORDER BY in the subquery if you want to pick a particular row from each set:

SELECT *
FROM  (
    SELECT DISTINCT ON (address_id) *
    FROM   purchases
    WHERE  product_id = 1
    ORDER  BY address_id, purchased_at DESC  -- get "latest" row per address_id
ORDER  BY purchased_at DESC;

If purchased_at can be NULL, use DESC NULLS LAST - and match your index for best performance. See:

  • Sort by column ASC, but NULL values first?
  • Why does ORDER BY NULLS LAST affect the query plan on a primary key?
  • Related, with more explanation:

  • Select first row in each GROUP BY group?
  • Sort by column ASC, but NULL values first?
  • You cannot use DISTINCT ON without a matching ORDER BY. The first query requires an ORDER BY address_id inside the subquery. – Aristotle Pagaltzis Jul 12, 2017 at 18:46 @AristotlePagaltzis: But you can. Wherever you got that from, it's incorrect. You can use DISTINCT ON without ORDER BY in the same query. You get an arbitrary row from each set of peers defined by the DISTINCT ON clause in this case. Try it or follow the links above for details and links to the manual. ORDER BY in the same query (the same SELECT) just cannot disagree with DISTINCT ON. I did explain that, too. – Erwin Brandstetter Jul 13, 2017 at 0:08 Huh, you’re right. I was blind to the implication of the “unpredictable unless ORDER BY is used” note in the docs because it does not make sense to me that the feature is implemented to be able deal with non-consecutive sets of values… yet won’t allow you to exploit that with an explicit ordering. Annoying. – Aristotle Pagaltzis Jul 13, 2017 at 6:31 @AristotlePagaltzis: That's because, internally, Postgres uses one of (at least) two distinct algorithms: either traverse a sorted list or work with hash values - whichever promises to be faster. In the later case the result is not sorted by DISTINCT ON expressions (yet). – Erwin Brandstetter Jul 13, 2017 at 15:15

    You can order by address_id in an subquery, then order by what you want in an outer query.

    SELECT * FROM 
        (SELECT DISTINCT ON (address_id) purchases.address_id, purchases.* 
        FROM "purchases" 
        WHERE "purchases"."product_id" = 1 ORDER BY address_id DESC ) 
    ORDER BY purchased_at DESC
                    Very marginally yes. Although since you have a purchases.* in your original select, I don't think this is production code?
    – hkf
                    Mar 20, 2012 at 22:06
                    I'd add that for newer versions of postgres you need to alias the subquery. For example: SELECT * FROM (SELECT DISTINCT ON (address_id) purchases.address_id, purchases.* FROM "purchases" WHERE "purchases"."product_id" = 1 ORDER BY address_id DESC ) AS tmp ORDER BY tmp.purchased_at DESC
    – aembke
                    Jun 17, 2014 at 20:38
                    This would return address_id twice (without need). Many clients have problems with duplicate column names. ORDER BY address_id DESC is pointless and misleading. It does nothing useful in this query. The result is an arbitrary pick from each set of rows with the same address_id, not the row with the latest purchased_at. The ambiguous question did not ask for that explicitly, but that's almost certainly the OP's intention. In short: do not use this query. I posted alternatives with explanation.
    – Erwin Brandstetter
                    Jul 17, 2017 at 15:22
    
    SELECT DISTINCT ON (address_id) 
       LAST_VALUE(purchases.address_id) OVER wnd AS address_id
    FROM "purchases"
    WHERE "purchases"."product_id" = 1
    WINDOW wnd AS (
       PARTITION BY address_id ORDER BY purchases.purchased_at DESC
       ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING)
                    @Gajus: Short explanation: it doesn't work, only returns distinct address_id. The principle could work, though. Related examples: stackoverflow.com/a/22064571/939860 or stackoverflow.com/a/11533808/939860. But there are shorter and / or faster queries for the problem at hand.
    – Erwin Brandstetter
                    Jul 17, 2017 at 15:56
    

    For anyone using Flask-SQLAlchemy, this worked for me

    from app import db
    from app.models import Purchases
    from sqlalchemy.orm import aliased
    from sqlalchemy import desc
    stmt = Purchases.query.distinct(Purchases.address_id).subquery('purchases')
    alias = aliased(Purchases, stmt)
    distinct = db.session.query(alias)
    distinct.order_by(desc(alias.purchased_at))
                    That's weird, is from_self something undocumented? I cannot get it to work – Query and QuerySet raise AttributeError when I try to access it
    – DataGreed
                    Apr 15, 2021 at 23:11
    

    It can also be solved using the following query along with other answers.

    WITH purchase_data AS (
            SELECT address_id, purchased_at, product_id,
                    row_number() OVER (PARTITION BY address_id ORDER BY purchased_at DESC) AS row_number
            FROM purchases
            WHERE product_id = 1)
    SELECT address_id, purchased_at, product_id
    FROM purchase_data where row_number = 1
    

    You can also done this by using group by clause

       SELECT purchases.address_id, purchases.* FROM "purchases"
        WHERE "purchases"."product_id" = 1 GROUP BY address_id,
    purchases.purchased_at ORDER purchases.purchased_at DESC
                    This is incorrect (unless purchases has only the two columns address_id and purchased_at). Because of GROUP BY, you will need to use an aggregate function to get the value of each column not used for grouping, so they values will all be coming from different rows of the group unless you go through ugly and inefficient gymnastics. This can be fixed only by using window functions rather than GROUP BY.
    – Aristotle Pagaltzis
                    Jul 12, 2017 at 18:10
            

    Thanks for contributing an answer to Stack Overflow!

    • Please be sure to answer the question. Provide details and share your research!

    But avoid

    • Asking for help, clarification, or responding to other answers.
    • Making statements based on opinion; back them up with references or personal experience.

    To learn more, see our tips on writing great answers.