Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bdGqA-0007aw-HU for pgsql-sql@arkaria.postgresql.org; Fri, 26 Aug 2016 13:06:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bdGq9-0008O1-Sc for pgsql-sql@arkaria.postgresql.org; Fri, 26 Aug 2016 13:06:33 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bdGpA-0006Bd-LH; Fri, 26 Aug 2016 13:05:32 +0000 Received: from mout.kundenserver.de ([212.227.126.134]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.84_2) (envelope-from ) id 1bdGp3-0004uW-Bt; Fri, 26 Aug 2016 13:05:31 +0000 Received: from [192.168.178.26] ([84.165.203.170]) by mrelayeu.kundenserver.de (mreue004) with ESMTPSA (Nemesis) id 0MhPzK-1bQfeC1YWI-00MesQ; Fri, 26 Aug 2016 15:05:22 +0200 To: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= Subject: Unsupported feature F867: WITH TIES Message-ID: <5ab043b6-686d-b907-6672-7d39738ebd6f@purtz.de> Date: Fri, 26 Aug 2016 15:06:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:OtYic9OPeQj+/6iFRfBAx823jcoWHQxzTsAM9ow46ZoprlbQp4U 1GGRDNN3sW+slMIPNjiIqJAjn9FgXAeA5BNx6ZAeHJwrVwsSb7B22P0i/Jl/3Rw6peTaYkH JlomGf95UW9/l3vQWCNjr0OPb3vNBpIh1u1iyoWUmeTbsXt8S5OXsIwRpH0pbtQKhNQvrh7 rKkwAay0CcVX2oHDyDscQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:7fGEAd0xSYc=:L4p5X4yRFpQB32U9Jl0lL3 FPxPXut59nEue2Wh9XroJ3vqMee621+O/BPUWk3oeYkQG9y2+LHnIVfYRn87325OEkcUMFEE4 r15yZwnBPyhZoH96Z2el+/YoULnYozgCOpOeH5Ub1R6nDwqeBiC3+vI2rEZ6l+y6/3AgLauUi HV3DrbsxAkENbPVUgotPwX+E6JOoalcIkScKPczYU8AgkclRx59puKgTVUmB7NEuiMGcFSzDx yBiKbyh4ZxTsIchmjali7FZic+QxDlehPc88bZXVVTWdskwx/9IAmKrWGdkc9T9Hl+mgXRkdR PU4ujrksYRoJdjroFxTnRx8KCRNX2grtXOUKL4s3fhq71FUUNU8o9p4dOMhL5pE1ePmMd/TJI edFVvWUYJkmqzm0LBvsrbdDBFz3QLrZ3PbHsTen86rNEjtgmX7XZIDAUX8O29yDs/T8dJcCgJ SWvvOeVPYOoYGb526CXivA1KbHidf4TJa5jm8Kn3/uyYKaTfwsMxmzevikGCfHg1oigEyzv+/ 4id0UhaVnbTBAnMK4hs5tt4zjPD1GGaCLvoS6xsARlseUiiW9FfjvqL3khK/0bPCQI/bVYvcA r+ux+1/GqBYHpaBLeRbta8jTVj6yDC/YoN605kURmcXjaTwTbJgRzSWyH5Ps2ERljgfiKVCIb YuI1tmKAhWtmauHoGR28SodaHutxzHDVwALwQd6oO3+RDou2TcipnXZqbmtu0hfhjV1o2bMPf 2ym5YBIzfssbuBTT X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org Actually we don't support the SQL feature F867 "FETCH FIRST clause: WITH TIES option". On the other side we support the window function "rank()" which acts like the "WITH TIES option". My questions are: Is it hard to implement the "WITH TIES option"? Are there plans for a realization / how do we decide in general what to do next? Differs the semantic of the "WITH TIES option" significantly from the "rank()" window function or can we treat it as some kind of 'syntactical sugar'? Regards, Jürgen Purtz -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql