Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b5NC6-0007zU-7d for pgadmin-hackers@arkaria.postgresql.org; Wed, 25 May 2016 01:01:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b5NC5-0005PS-J1 for pgadmin-hackers@arkaria.postgresql.org; Wed, 25 May 2016 01:01:05 +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 1b5NBs-0005BV-3x for pgadmin-hackers@postgresql.org; Wed, 25 May 2016 01:00:52 +0000 Received: from mail-vk0-x229.google.com ([2607:f8b0:400c:c05::229]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1b5NBo-00010K-ST for pgadmin-hackers@postgresql.org; Wed, 25 May 2016 01:00:50 +0000 Received: by mail-vk0-x229.google.com with SMTP id f66so44806769vkh.2 for ; Tue, 24 May 2016 18:00:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=yHeOcAy/ovLy5S2XujbPcJqWfrYSeGvlPldnilSZkQ4=; b=p3gAfno1EkztLX+ba3Hxc2ULsUzyT6Q6DIXGd87tl0hG5SbSvrFZX7+lC9ZBb2vuM4 9uNpXWbzqvCpniHuO9gmH4saEdeUCGyMs50tsYbHi374iRaZzRGwlFqRxvbqOYZXQ01w 3R8oAUikjPi9e+C0YUHyPt0Ko/FpB9CdPZDDPg7XYMmZinP4/EEijZy+f5PDBVjIpism y7QaqRCeeNq4MkIY70mfb3coYjTxjlLFbymphC6vLnYuyB8k4f2d4y23kKKX1Hsmzyjt +Rkoow20lOC62X5fOzihe6ADtBPGzmtCO4yaim+56A4rYE2H00ACAHlXnJ26jmOJLl8B VKmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=yHeOcAy/ovLy5S2XujbPcJqWfrYSeGvlPldnilSZkQ4=; b=HtlIuzXBN+rZINUnPn54L92GlsatFRR3zZnWeg+uIDVbExCLt75w3v1pchGa9JE1DJ WL8rM8tXL74L/Y5F7fOnrcyfWcCIQ2oaAHyKZ63z6sdJq5ewAWS6DzcxooztFsYSGeWV XrlErB+V01IN+j3GBKOGq9uo8zzmwDC5nC3W59KPmlkgupfEIhnTmIDisMaYJnXDTc5q lpO6UHGU3HhVanWI2LEgH4vvkfGjKIl8cTtjeW7HwfPNwovROWJCkFwlSJa/lOlp6rEx WV+iSAqLwqZ6aRuOZ1+7Kieb6YSE1KZB1wgpjX9mWtE7Qpp8viaGTBV/OAHpMDUijwDC hK5w== X-Gm-Message-State: ALyK8tIF8m9/HTGo8Qa9uXOV810pcfhdpb14FFkrnnoFNlr2LClyRY6PUscyD8cPbmotas42P/0x0UTki5I8Ag== X-Received: by 10.31.157.211 with SMTP id g202mr600835vke.49.1464138047596; Tue, 24 May 2016 18:00:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.2.239 with HTTP; Tue, 24 May 2016 18:00:17 -0700 (PDT) In-Reply-To: References: From: Thom Brown Date: Wed, 25 May 2016 02:00:17 +0100 X-Google-Sender-Auth: 6AXix4tJ-G3O_9GJYt598nLBhks Message-ID: Subject: Re: [PATCH] Tables node (pgAdmin4) To: Ashesh Vashi Cc: Murtuza Zabuawala , Dave Page , Akshay Joshi , Harshal Dhumal , pgadmin-hackers Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.4 (--) 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 On 25 May 2016 at 00:29, Thom Brown wrote: > On 24 May 2016 at 19:09, Ashesh Vashi wrote: >> >> On Mon, May 23, 2016 at 6:35 PM, Murtuza Zabuawala >> wrote: >>> >>> Hi, >>> >>> PFA patch, which will fixes below mentioned issues, >> >> Committed. > > > In the Create Table dialog, on the Advanced tab, the "Of type" drop-down > lists tables and composite types, but those are supposed to just be > composite types. > > Also, when using OF in CREATE TABLE, LIKE is no longer valid, so LIKE should > be disabled when using OF. Also, there should probably be a way of setting > options for the columns taken from the composite type. For example: > > CREATE TYPE inventory AS (product_id bigint, product_name text, weight > numeric); > > CREATE TABLE stock OF inventory ( > PRIMARY KEY (product_id), > weight WITH OPTIONS DEFAULT 0 > ); > > There's currently no way of doing this (neither the primary key, nor the > default value for any columns). It should probably automatically populate > the columns from the composite type on the columns tab. > > Also, could the generated SQL have an empty line between each statement? Another thing I've noticed is that, when adding columns, the "Is primary key?" column is greyed out. Why not just make those modifiable in that view rather than having to go into the details for each column? When there's something that hasn't been set up correctly, like adding variables for a column, but not actually selecting a variable, the SQL pane, correctly, doesn't show an output, but the error message, "Please provide input for variable." isn't enough to identify what needs checking. Could the relevant tab and field/row be highlighted/coloured in red/bold? This is more general, so doesn't just apply to the create table dialog. Thom -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers