Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1brkzf-0003gn-1v for pgadmin-hackers@arkaria.postgresql.org; Wed, 05 Oct 2016 12:08:15 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1brkze-0007wG-3z for pgadmin-hackers@arkaria.postgresql.org; Wed, 05 Oct 2016 12:08:14 +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 1brkzd-0007w9-GK for pgadmin-hackers@postgresql.org; Wed, 05 Oct 2016 12:08:13 +0000 Received: from mail-it0-x234.google.com ([2607:f8b0:4001:c0b::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1brkzY-000682-7B for pgadmin-hackers@postgresql.org; Wed, 05 Oct 2016 12:08:12 +0000 Received: by mail-it0-x234.google.com with SMTP id r192so182425214ita.0 for ; Wed, 05 Oct 2016 05:08:07 -0700 (PDT) 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:from:date:message-id:subject:to :cc; bh=Uu/YjtXEjhwjnV0PM6q2/dzr6v3w5rrnJ8LvLd7tAOo=; b=yi1BMR+Cf7bK3u1lNkMF8br1lBuqkVxPKYfCXkqEqK8n9KR+6tkYLLA+R/1AUcWdjS +H1ozerOf1CqPFDg9JZcs9gxrNFl0CT28pGq5WT4agSqPL+RQW0UWJ86bG8gYufCAG9G Fu+9ik/dz52CG39VBeV2vx9pKL54BssmjhlxOHbpaasF+LH3gmkPRnRy6kJqPI3V/WTR 0QuI86J+H7TItJwXZB4isZU+cjq6YUA+Wt5g3011yCFZLGJc2869TymTF12hX6BEiP8Y 0/StbkgyTnn7hcX+keXMWXYwSbbpa1HOPAg9jneUDdWGB3zuNHYjRdl7klUevHrnnot0 HKRw== 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:from:date :message-id:subject:to:cc; bh=Uu/YjtXEjhwjnV0PM6q2/dzr6v3w5rrnJ8LvLd7tAOo=; b=iuz3NF3tXTGPeMNLgx/aRUDqk6WV6pfzHMMk8PWV4e2+1scnkk2UuXHF+9TmBTrlt9 nTAufKOzn7mUWokw6FK4EBJGhpIZ42fXy30+Sz+ZXWgvwl7PW21l6YchIo/C0D1y2bUf 3RDQr8L5IWBfaPQPxfurPH1YcRuvUkYQax531IgPVbgd9CalCVXmELby4KYHgUYY943t Ch5Kvdh7/ZfMJnuKVt3hMC/3dGGZ5xNcRFdoxdQlVuh2WGKvsHsBvU1mesxsb6Ht8wY9 KrG1uajWizjrxFg1yOX2ekoFQP+i9zjykmtj7WFPv0o7h96fjW8zAsx1Wrv5fbOg68nZ 1WlA== X-Gm-Message-State: AA6/9RmXTKpGo+YgFaP8RyWv0nszHEBy4CM5qKQlHwF4g6OnLNqAse5K+RWn8khUteuY+d3AjVgek7bpPinrdQ== X-Received: by 10.107.28.148 with SMTP id c142mr8968435ioc.45.1475669287121; Wed, 05 Oct 2016 05:08:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.1.203 with HTTP; Wed, 5 Oct 2016 05:08:06 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Wed, 5 Oct 2016 13:08:06 +0100 Message-ID: Subject: Re: PATCH: To fix issue in synonym node (pgAdmin4) To: Murtuza Zabuawala Cc: pgadmin-hackers 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 Hi On Wed, Oct 5, 2016 at 9:53 AM, Murtuza Zabuawala wrote: > Hi, > > PFA patch to fix the issue in synonym node, where it was not horning parent > node while creating in different node, issue was that we were not sending > node properly. > RM#1611 That doesn't seem like a reliable way to get the correct parent ID - what if there are multiple synonyms in different schemas but with the same name? -- 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