pgAdmin is the most popular and feature rich Open Source administration and development platform for PostgreSQL, the most advanced Open Source database in the world.
If a select result contains a data column wider than the internal minimum default, the result is always truncated by a few pixels. This effect is visible when selecting something like the following string literal:
select '[10001, 20002, 30003, 40004, 50005, 60006, 70007, 80008, 90009]'
which is truncated also when the same string is casted to JSON(B):
Thus the effect is independent of output formatting. As it seems to me, the column size computation just misses the left padding offset and thus always recognizes that it has to truncate the contents and show an ellipsis. This in fact always hides the last character only. I have been observing this behaviour since more than a year already.
Tested with
Version
8.13
Application Mode
Desktop
Commit:
b2782650055dd41c060cd016f29ecd5575cd1828 2024-11-11
Current User
pgadmin4@pgadmin.org
Electron Version
33.2.0
Browser
Chrome 130.0.6723.118
Operating System
Windows-10-10.0.19045-SP0
If a select result contains a data column wider than the internal minimum default, the result is always truncated by a few pixels. This effect is visible when selecting something like the following string literal:
select '[10001, 20002, 30003, 40004, 50005, 60006, 70007, 80008, 90009]'which is truncated also when the same string is casted to JSON(B):
Thus the effect is independent of output formatting. As it seems to me, the column size computation just misses the left padding offset and thus always recognizes that it has to truncate the contents and show an ellipsis. This in fact always hides the last character only. I have been observing this behaviour since more than a year already.
Tested with Version 8.13 Application Mode Desktop Commit: b2782650055dd41c060cd016f29ecd5575cd1828 2024-11-11 Current User pgadmin4@pgadmin.org Electron Version 33.2.0 Browser Chrome 130.0.6723.118 Operating System Windows-10-10.0.19045-SP0