Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aGksP-0002As-CD for pgadmin-hackers@arkaria.postgresql.org; Wed, 06 Jan 2016 09:59:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aGksO-0003zE-V6 for pgadmin-hackers@arkaria.postgresql.org; Wed, 06 Jan 2016 09:59:32 +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 1aGksB-0003UU-7M for pgadmin-hackers@postgresql.org; Wed, 06 Jan 2016 09:59:19 +0000 Received: from mail-io0-x233.google.com ([2607:f8b0:4001:c06::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aGks7-0002py-AO for pgadmin-hackers@postgresql.org; Wed, 06 Jan 2016 09:59:18 +0000 Received: by mail-io0-x233.google.com with SMTP id q21so213523415iod.0 for ; Wed, 06 Jan 2016 01:59:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QH9Ng22QBqzfxtNgeJBuctNpURLSB93hpTsUR+NSYyU=; b=b4CfFkIuyfYFhbvr73YEIZQD1q0DRRqe8uJ8R7U3kEfy3YK0DYpz70gMph+HzFAdIV hBK2IBvYfXphXdRJAGKddfDcVyMg/HvFRdxxLkeplnIiaUeiKG3v7c1skw8BBQyFxpVU WmIpuovApr1oMpLaU/L9dRhpnSI19FOrfhJplleCh8qolBX4csTVENklHxq8UDU5FTmn 1pfMurlnRw96TAkmECiVAaGerWZo8Qj3mOlBuvoXUk33sRhCGFqQefzSwHvPOroqlsiy OSAgGFBLeAXD1kUwW+f++JuEFNnIly8ZItnA/gkRL+g59moOo9Fe/oaTgJQGKldfl+xN OmRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=QH9Ng22QBqzfxtNgeJBuctNpURLSB93hpTsUR+NSYyU=; b=Is3Hvjy86GZpDw9x8WWn9ktqh7RUL3yM/w2Kxb3Y/DDTMMHirx4IaEtAc/sksimKYC RhfF56A7zTjUUcTU5VY+EaCF8ArJJmwEEMsBRefzbFSPXzJzXTsvzB6vAy9jmi5iEbuR HxRlHPRSHBLfeuYL/iTWPwHDbsYBU+ZH3mLl1T+H3WmGXa2DFRt0D/Aifd0ogt+VQTNi F4kA3e7IglhdkiKl5DaFseGLGERg2HIrjQMxXsfbM4nJMQzPGmu7wSU+CkTdvzMuYX6S 7c+xR5swEP1Xjc2iTXAyC3O0yoLNHNOdy+jv8xRjVYCNXakD8Skinbo9gwEjMVqEcSPq nFYg== X-Gm-Message-State: ALoCoQnwlHCbXTh/jirYs52DtzuA78vBlhO6fMtORQKV3bzcsghMiY1oq+fixd3FWCrSRZXuY6oZ9KiskRF8z0sH2Ksf0Dwf8Q== MIME-Version: 1.0 X-Received: by 10.107.43.17 with SMTP id r17mr89590079ior.156.1452074353220; Wed, 06 Jan 2016 01:59:13 -0800 (PST) Received: by 10.64.0.195 with HTTP; Wed, 6 Jan 2016 01:59:13 -0800 (PST) In-Reply-To: References: <568BA29D.2070305@yandex.ru> Date: Wed, 6 Jan 2016 09:59:13 +0000 Message-ID: Subject: Re: pgAdmin III commit: As per commit:600daf650bd5e50e664c4ece2e53e95446390 From: Dave Page To: Neel Patel Cc: Nikolai Zhubr , pgadmin-hackers , Ashesh Vashi Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.6 (--) 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 Thanks. Ashesh - can you review/commit please? On Tue, Jan 5, 2016 at 12:24 PM, Neel Patel wrote: > Hi, > > Please find attached patch file with below fix. > - Return value of the function will be displayed as "SETOF record" instead > of "SETOF SETOF record" under SQL tab within properties window. > > Let me know for any comments. > > Thanks, > Neel Patel > > On Tue, Jan 5, 2016 at 5:08 PM, Neel Patel > wrote: >> >> Hi Dave, >> >> Sure, I will look into this issue. >> >> Thanks, >> Neel Patel >> >> On Tue, Jan 5, 2016 at 4:47 PM, Dave Page wrote: >>> >>> Neel, can you look at this please? >>> >>> Thanks. >>> >>> On Tue, Jan 5, 2016 at 11:01 AM, Nikolai Zhubr >>> wrote: >>> > 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 >>> >>> >>> >>> -- >>> Dave Page >>> Blog: http://pgsnake.blogspot.com >>> Twitter: @pgsnake >>> >>> EnterpriseDB UK: http://www.enterprisedb.com >>> The Enterprise PostgreSQL Company >> >> > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers