Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cYrNA-0006vd-6j for pgadmin-hackers@arkaria.postgresql.org; Wed, 01 Feb 2017 09:38:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cYrN9-0004UT-2u for pgadmin-hackers@arkaria.postgresql.org; Wed, 01 Feb 2017 09:38:39 +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 1cYrMv-0004Bw-LU for pgadmin-hackers@postgresql.org; Wed, 01 Feb 2017 09:38:25 +0000 Received: from mail-io0-x22d.google.com ([2607:f8b0:4001:c06::22d]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cYrMr-0007s9-PN for pgadmin-hackers@postgresql.org; Wed, 01 Feb 2017 09:38:24 +0000 Received: by mail-io0-x22d.google.com with SMTP id v96so56019207ioi.0 for ; Wed, 01 Feb 2017 01:38:21 -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:from:date:message-id:subject:to :cc; bh=VhwJuPVF7Kl8rlqI23EVYRayOI0Efd+gETZMcqodcU0=; b=FgeHd8Zvl91n5YMNlAdQSuUJqdR5dbqM+ozqYpCxv4v7neKEbkIuMcTr2p5jMpeqzt k+WMmgvRu6kVzheIuzCx2e6UfbQzLUH+aByMUrVy2Q+kkdLWuEk8s1RzQEuMyGAe1qJW YtjaIsbadS5wTBo2wt9k0ih3ouoH2BLu+NMhZhXus6p5dB2hqi7AM1axkf7GMc4rfzJM LB5h/VJPcc9Z6jMYZXjL9c7zn2E+Fn9nAxlzi+VoWQq4uuaRS5MQq5uwq/nwmvJCgEz2 fsV48OttfknhH/m6OtY2ca12d+iDOwuhDDy0q0PoiGQgbYwHmWy6D35V0Pn593ChVGyZ aELQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VhwJuPVF7Kl8rlqI23EVYRayOI0Efd+gETZMcqodcU0=; b=Ut7z17R1Qyhs0zcEScLyMZw6H95mbxQXXCw5KjRUg6ktgubXbCiQghIuwshNe7JrDB 4xEYZs/KMOlubAhv5cESJbTxI08IIYmhCX5wle7dongeogQ0PSg5KkpgESSRfpTHbHeA EaTMuebNAtf83IFF9jW5oRzew1lh6mxDR62q8RdvVtHG9ScCsc/iVGCP5IZIcRM/WKE9 PVvQI5qJh9ahXrisZBfXTSCcE3XSVd9S/yXiNC1Iiir7uobQV7tmKYRaB/CC2UwM2/Cw DJc+tY6qk5WJxxZefKOCabpQtX8/ghRpDeG0riveiCOVee7HXcpnOJswyjSWK7YR5clX bvtg== X-Gm-Message-State: AIkVDXIDaKvfozRFNQRPiOObHE++S+rVCNKmLWF5XMAZyCferftXeLpehrVFLSYV2ZeMnbEwefUxpRS/KHWl0A== X-Received: by 10.107.57.5 with SMTP id g5mr1464281ioa.208.1485941899843; Wed, 01 Feb 2017 01:38:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.224.198 with HTTP; Wed, 1 Feb 2017 01:38:19 -0800 (PST) In-Reply-To: References: From: Dave Page Date: Wed, 1 Feb 2017 09:38:19 +0000 Message-ID: Subject: Re: [pgAdmin4][PATCH] To fix the issue in handling of timestamp type 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 Tue, Jan 31, 2017 at 5:19 AM, Murtuza Zabuawala wrote: > Hi Dave, > > PFA updated patch. This seems to display "timestamp(0) with[out] timezone" columns correctly in both the properties panel and dialog now, but the size is still ignored if I try to add a new column through the table or column dialogue. -- 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