Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ainCH-0007XB-Ri for pgsql-sql@arkaria.postgresql.org; Wed, 23 Mar 2016 18:07:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ainCH-0006ta-E8 for pgsql-sql@arkaria.postgresql.org; Wed, 23 Mar 2016 18:07:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ainCE-0006rX-Vp for pgsql-sql@postgresql.org; Wed, 23 Mar 2016 18:07:55 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ainCB-0007E9-7A for pgsql-sql@postgresql.org; Wed, 23 Mar 2016 18:07:54 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 616E520946 for ; Wed, 23 Mar 2016 14:07:48 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 23 Mar 2016 14:07:48 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=dxuN9qpdXRfSBfIKi97cpQDnJ10=; b=Zepa65 Dpm4wWjgnKTijqShR9G5X1dWvauAjtJZJG5VqKNrDFuOdJMnGUjAIgoDqsgncDS7 lsrVzwqTNzio8y6Z6XQ4hH1PDvlC0OgHzY9gxYqPKPX9KhoGtnhU/yaFya3jveyA Cl3NcmD07xBnJlA+f6Xlx094yVznSEh43eAE8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=dxuN9qpdXRfSBfI Ki97cpQDnJ10=; b=ltB9zQMvSVuzLrN+rtTKJ+jH9PVCfm/UHpG/7T+K57q1bcc uLS1sqOipsaBeBfQ43SVkw0ALQsOr/hNlDSqfT875M1pvslp9ybGDgCVmUOLn8DW WtVTq7ZlYnSrPsS564EjWmgNZjViolZACBXr3Qj7HZ2TCTf7KPn7A/FuMufU= X-Sasl-enc: FdNvZC8WW9USlNYmUn00xJiSD5ZFuNox69QatmwGdzes 1458756468 Received: from killi.site (173-160-167-74-washington.hfc.comcastbusiness.net [173.160.167.74]) by mail.messagingengine.com (Postfix) with ESMTPA id E4991C0001B; Wed, 23 Mar 2016 14:07:47 -0400 (EDT) Subject: Re: query based on row number for psql8.3 To: emilu@encs.concordia.ca, pgsql-sql@postgresql.org References: <56F2D9C4.9010304@encs.concordia.ca> From: Adrian Klaver Message-ID: <56F2DB73.2070703@aklaver.com> Date: Wed, 23 Mar 2016 11:07:47 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <56F2D9C4.9010304@encs.concordia.ca> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) 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 On 03/23/2016 11:00 AM, Emi wrote: > Hello, > > For psql8.3, is there a simple way to query based on row number please? First FYI, 8.3 is 3 years past its end of life. Second, Postgres does not have a built in row_num. Anything that could be cobbled together would be dependent on the ordering specified. So what exactly are you trying to do? In other words what is row_num supposed to represent? > > For example, > > select case > when row_num=1 THEN t1.tot_hr > ELSE t1.tot_hr - > t1.pre_hr > END > FROM t1 ; > > > > > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql