Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1aqmj3-0002H4-7r for pgadmin-hackers@arkaria.postgresql.org; Thu, 14 Apr 2016 19:14:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1aqmj2-0004C8-RF for pgadmin-hackers@arkaria.postgresql.org; Thu, 14 Apr 2016 19:14:48 +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 1aqmj2-0004Aw-5S for pgadmin-hackers@postgresql.org; Thu, 14 Apr 2016 19:14:48 +0000 Received: from mail-ig0-x22e.google.com ([2607:f8b0:4001:c05::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1aqmiz-0001Up-17 for pgadmin-hackers@postgresql.org; Thu, 14 Apr 2016 19:14:47 +0000 Received: by mail-ig0-x22e.google.com with SMTP id f1so1518145igr.1 for ; Thu, 14 Apr 2016 12:14:44 -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:date:message-id:subject:from:to :cc; bh=+aPGNomCgUnII5nQPCuY6yomSGJaiXNRH2ZMOE0xBpU=; b=Vj4/mzq/upHNxPNoK7NXVmfz5++M8YPnt23x1wldpI4Q6/dC9/fPfrCoVdhmWQg3Of 0gagdfQU3ycq3UtsPOchUqmC8EtNGyrqeHC7RCXHN+xvt+0GR/WzPoJo7xfTzuIPkewR vfsc6UXGR72a4U2C60so7lf4s/T4r87kfAddlbNVdzXoDeX5ECF44q7g8c31VwfJxjzV DbTDmR8vARleyMjkOjIY9MV5rLUIi6qpSQtdlgC1yMTCyA6JsuXbGfw5CSomEaPP8t2q hUljkurjgzqgubownl3alNIrgyr2oBDgeXWD6TvnnQ6iC9M5b4GH0k97BB5gH71zusRs Hsng== 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; bh=+aPGNomCgUnII5nQPCuY6yomSGJaiXNRH2ZMOE0xBpU=; b=mowYKzDfI0QJQ0Zr5SUtG3IzgFrOBwL23sGRxnjPt/Qxx7cy35o8GvSfvUvAcjHXqu 4uziOIUHWw8qY6RG1jc0HlLUxnKLL9CTWh/2eDst5zUfcb8d+BJAXi2dA6G0CA6aEsLQ 47r4ETGv+tTN9PFcSOX1ruDj1Pi9r0v/iJT9o1xPpGUIyeJ5FM873UGSFNbVnpKvB+5b C1+DihcYCypWv0tSwmzUp/WC1W0+LMp9gqznEZDhhxUihgHopyxiM5jR6wzfT7kIcxUf vA4qdCyw670tkNjWMbDkIia78yIOJtbhfhuIBDdg+ncIjkx5zJgnTMficGuwY0HQx1Qq 4laQ== X-Gm-Message-State: AOPr4FV/djA5auLsSTOj7ma6RYoIUm5YUzfoPfbuEhP2WFvOcFV1Zba9AXWpdnAN5Q89eCLKcZhqjIc/7hDveQ== MIME-Version: 1.0 X-Received: by 10.50.59.210 with SMTP id b18mr290002igr.11.1460661283444; Thu, 14 Apr 2016 12:14:43 -0700 (PDT) Received: by 10.64.105.131 with HTTP; Thu, 14 Apr 2016 12:14:42 -0700 (PDT) In-Reply-To: References: Date: Thu, 14 Apr 2016 20:14:42 +0100 Message-ID: Subject: Re: PATCH: Resolving issue regarding FTS Parser name From: Dave Page To: Sanket Mehta 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 Thanks - applied. On Thu, Apr 14, 2016 at 3:48 PM, Sanket Mehta wrote: > Hi, > > PFA the patch for resolving an issue related to FTS Parser name. > > Steps to reproduce the issue: > > - create fts parser with name "user name" > - Expand fts parser > - Right Click and select properties > - Change name to "user name car" > > > it's give ERROR: syntax error at or near "name" > LINE 2: RENAME TO user name car; > > Please do review the patch and send review comments if any. > > > Regards, > Sanket Mehta > Sr Software engineer > Enterprisedb > > > -- > 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 -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers