Re: Request a feature

From: Robert Eckhardt <reckhardt(at)pivotal(dot)io>
To: Nick Dro <postgresql(at)walla(dot)co(dot)il>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Request a feature
Date: 2017-07-20 20:03:39
Message-ID: CAAtBm9Wvbh3Ai3RN2qk+uWteSbcn2A1_3sRA1wKF+Buqrm7yww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Nick,

We were looking at adding this feature but ran into the same problem you
are describing, e.g. when to include and when to not include headers.

Honestly we were waiting for people to start using the new UX for the
differing copy and paste functionality and waiting to see what people said.

The current design (pgAdmin 4 1.5 +) the existing behavior is a hybrid of
excel like functionality and a non-excel table like behavior. One option
would be to go full Excel and treat the headers like a row.

I think my concern with adding a new keyboard shortcut for copy or copy
with headers would be a discoverability issue.

-- Rob

On Wed, Jul 19, 2017 at 3:34 AM, Nick Dro <postgresql(at)walla(dot)co(dot)il> wrote:

> Hi,
> When copying data from query resut the user can choose whether it would be
> copied with column names or without but choosing the correct setting.
> This is nice but extermly annoying. Sometimes I want it the first way and
> sometimes the other way.
> Would it be possible that Ctrl + C would continue to work with the chosen
> setting and you'll define new key like : Ctrl + B that will be the other?
> Please define some way to have keys for both options. It would help
> considerbly.
> Another solution is simply allow the user to define the shout cut himself
> in the menu.
>
> Thanks,
>

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2017-07-20 20:13:22 Re: [pgadmin-hackers][pgaweb][patch] Update SCSS of styleguide
Previous Message Dave Page 2017-07-20 20:01:12 Re: [pgAdmin4][Patch] Font sizes to 13 px and not bolded