Re: values not fitting in query result columns, and some ideas - Mailing list pgadmin-support

Murtuza,

 

1. Re: value not fitting in columns.

 

There must be something that can be done.

 

select 12345678.1234567

 

For example displays as “5678.1234567” even though there is lots of space for the column.

Could it not expand the column width as values turn up that area wider than the existing column width as long as the total width is not say twice as wide as the sceen.

Elipsis is used to truncate text value, e.g. [long text…]. Could that not be used for numeric and integer values, rather than truncating the front, display from the start and use ellipsis, e.g. “12345678.12…” in the above exampled.

 

2. Re: option to displaying text in ‘quotes’.

The feature you are requesting will mislead other users, if the actual result will starts with quotes then user might face the problems in inserting/updating the data.

The value could be displayed using the quoting SQL uses, e.g: ’a’’b’ for “a’b”.

The values would only be for display, export to .csv would use the original values.

Presently there is no way to see leading or trailing spaces.

If the value starts with quotes does the user not need to ‘’ quote anyway, e.g. insert into message values (‘’’fred’ is his name’);

pgAdmin4 allows me to edit the values in the query results but does not update the database?

 

3. Transposed results.

Ignore this one, it’s useful for me on the command line but wouldn’t fit in a typical pgAdmin 4 screen layout.

 

4. ​\d is feature of psql, if you want to see the database object definition quickly you can simply select the respective object in browser tree and select the SQL tab.  ​

 

Navigating to Schemas/public/tables and scrolling down and across to the table is not quick.

\d is not valid SQL so could be used.

If \d took you to that page that would suffice.

I want to query and navigate rapidly around the database.

 

Yours Sincerely,

 

Gene Thomas.

 

From: Murtuza Zabuawala [mailto:murtuza.zabuawala@enterprisedb.com]
Sent: Thursday, 9 November 2017 1:21 AM
To: Gene Thomas <gene@nlc.co.nz>
Cc: pgadmin-support@lists.postgresql.org
Subject: Re: values not fitting in query result columns, and some ideas

 

On Wed, Nov 8, 2017 at 9:41 AM, Gene Thomas <gene@nlc.co.nz> wrote:

Hello,

       Firstly, thanks for pgadmin 4, I have found it useful. 1. However, I would really appreciate, if when displaying query results, the columns were resized to fit the values. I recently spent quite some time being misled because the leading digits in some numbers were cut off because the column was not wide enough, and there was no indication that the start of the number was truncated.

​The grid layout is kept to fit the result set on most of the screen resolutions and we are doing this intentionally as pgAdmin4 uses on-demand logic for data retrieval from database server, so we can't predict the size for next columns in advance, as the data in a column may vary. Just consider the simple scenario where column-x in Row-1 has text of length 10 characters and 

in Row-

​2​

 

​it ​

has 

​text

 of length 10

​000​

 characters

​.​

2. Also it would be useful if one could configure the display so text values are show in ‘quotes’, I have to deal with padded values so it would be really useful to see when there is padding. The display of null as [null] is much appreciated.

​The feature you are requesting will mislead other users, if the actual result will starts with quotes then user might face the problems in inserting/updating the data.

3. Also being able to display the query result transposed would be useful, e.g. column headings down the side and the rows displayed in columns.

Could you please provide more details on this, what's the specific benefit we (as a pgAdmin4 user) may get from this feature?​

4. Also being able to display table definitions, i.e. \d table_name in psql would be useful, one has to quickly check table definitions some times.

​\d is feature of psql, if you want to see the database object definition quickly you can simply select the respective object in browser tree and select the SQL tab.  ​

 

 

Yours Sincerely,

 

Gene Thomas.

--

Regards,

Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company