Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aGPOU-0005AE-Fa for pgadmin-hackers@arkaria.postgresql.org; Tue, 05 Jan 2016 11:03:15 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aGPOU-00082q-2A for pgadmin-hackers@arkaria.postgresql.org; Tue, 05 Jan 2016 11:03:14 +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) (envelope-from ) id 1aGPOT-00082X-CO for pgadmin-hackers@postgresql.org; Tue, 05 Jan 2016 11:03:13 +0000 Received: from forward4o.cmail.yandex.net ([2a02:6b8:0:1a72::289]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aGPOP-000880-OQ for pgadmin-hackers@postgresql.org; Tue, 05 Jan 2016 11:03:12 +0000 Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::27]) by forward4o.cmail.yandex.net (Yandex) with ESMTP id 93ED520E96 for ; Tue, 5 Jan 2016 14:03:07 +0300 (MSK) Received: from smtp3o.mail.yandex.net (localhost [127.0.0.1]) by smtp3o.mail.yandex.net (Yandex) with ESMTP id 767E21E023A for ; Tue, 5 Jan 2016 14:03:07 +0300 (MSK) Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ZRhttHZWrd-36bWKtKr; Tue, 5 Jan 2016 14:03:07 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1451991787; bh=9HKTcaspjDfNa0UlLDYFYiLyOAWjbFXtRL8k4E3XOL8=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=OuImO/Z72JeaCgTCg2GMS/vWwkDjjk+Bqb6huNv168aXc7ACGADk8qmEFoxssBEuu A9kU81PoAp/aXEuY/pWx6+i9iYls9DBI7FgPGe+T4FDiI13uDCr3gBkMgW6lLafXm2 snfjdWXLgFrythWiJfvoVPKVc0Leuiv6zijKq45E= Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <568BA29D.2070305@yandex.ru> Date: Tue, 05 Jan 2016 14:01:49 +0300 From: Nikolai Zhubr User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: pgadmin-hackers@postgresql.org Subject: Re: pgAdmin III commit: As per commit:600daf650bd5e50e664c4ece2e53e95446390 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org Hi all, Running 1.22-rc1 now I observe that this commit has apparently still not solved the issue in at least one place. That is: - "RETURNS SETOF record" is correctly displayed in SQL panel now. - "RETURNS SETOF SETOF record" is still erroneously displayed under SQL tab within the properties window (effectively preventing set-returning function to be changed in any way through the properties window). Thank you, Nikolai 12.10.2015 5:33, Ashesh Vashi: > As per commit:600daf650bd5e50e664c4ece2e53e95446390b6d, we now use > pg_get_function_result(..) function to identify the return type of the > function, hence - we don't need to add SETOF keyword explicitly, when a > function returns set of records. > > Branch > ------ > master > > Details > ------- > http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=9d7596dc552cf9315d4aa83eafe19db1acf7e531 > > Modified Files > -------------- > pgadmin/schema/pgFunction.cpp | 2 -- > 1 file changed, 2 deletions(-) > > -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers