Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XlEan-0001o8-1F for pgsql-admin@arkaria.postgresql.org; Mon, 03 Nov 2014 10:10:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XlEal-0006L8-6f for pgsql-admin@arkaria.postgresql.org; Mon, 03 Nov 2014 10:10:31 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XlEai-0006Kz-Uj for pgsql-admin@postgresql.org; Mon, 03 Nov 2014 10:10:29 +0000 Received: from mail-wi0-x22d.google.com ([2a00:1450:400c:c05::22d]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XlEab-0003ox-A3 for pgsql-admin@postgresql.org; Mon, 03 Nov 2014 10:10:26 +0000 Received: by mail-wi0-f173.google.com with SMTP id n3so5961139wiv.0 for ; Mon, 03 Nov 2014 02:10:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:reply-to:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=gloqGk4i19ZUW8uiXGvN9z3ZpeJmk3jUHLttLChivkE=; b=ZYtdL43O62oF5BdAHopS2Ha0pZZhxIodGIwO/GDHBlQeVk4oUevUl22VE3a+/xkW9Y sZlCmDpCbOiUFA2wnXAFndDfQ9HnwtUsLZXmAYwluJgBxiVDb8Cu0l2qpcw1QUOHwU1H nhinCD7E8Gvi0yDiDcf6enYiZZODsYDEJGSzWFFQcItB7FIY/nrUq6eBSeRUe2/ZWhbP r1aVeSJDwVd6iD8wbZZTL87qt+WL7yH8n0q70iW/X7B/mrpGwxob8TqS9b7k/45BKLl0 IC0Kj8j+9cHTk8SVcVIMWIN8mfHIdeNbJ/VQOOBOi4H3oAX+WD9QyFLKFB7ZElAzisov dKRw== X-Received: by 10.194.59.17 with SMTP id v17mr1158060wjq.130.1415009418155; Mon, 03 Nov 2014 02:10:18 -0800 (PST) Received: from enterprisedb01 (84.125.177.156.dyn.user.ono.com. [84.125.177.156]) by mx.google.com with ESMTPSA id ci9sm8154015wid.24.2014.11.03.02.10.16 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Nov 2014 02:10:17 -0800 (PST) Message-ID: <1415009415.30359.0.camel@gmail.com> Subject: Re: potential invalid input field of pgAdmin New Column GUI From: jaime soler Reply-To: jaime.soler@gmail.com To: liuyuanyuan Cc: pgsql-admin@postgresql.org Date: Mon, 03 Nov 2014 11:10:15 +0100 In-Reply-To: <001001cff1bc$dea86fc0$9bf94f40$@gmail.com> References: <001001cff1bc$dea86fc0$9bf94f40$@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.7-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org El lun, 27-10-2014 a las 16:05 +0800, liuyuanyuan escribió: > Hi , hackers! > > Currently I test some part of pgadmin GUI, and I found some potential > invalid input field of New Column GUI, > > Like Variables and Security Labels. Could you please have a look on > this issue? Please send this issue to pgadmin support list pgadmin-support@postgresql.org > > > > For example: > > OS: WIN7 64bit > > PostgreSQL 9.3 > > pgAdmin III:Version 1.18.1 > > I use GUI of pgadmin to create table, and add column to this table > (just as follow ). When I add a new column, > > I can add Variables (or Security Label )to this column, but finally in > the tab SQL of New Table Interface I find nothing > > of the Variables (or Security Label ) I’ve add. It seems that the > Variables (or Security Label ) does not work. > > > > > > Best Wishes! > > > > Yours > > Jasmine Liu > > > > October 27, 2014 > > > > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin