Обсуждение: [pgadmin-support] Issue with PgAdmin 4.13 and DATERANGE[]
I found an issue in PgAdmin. It seems the UI is not able to render arrays of dateranges and thus displays nothing at all.
- Platform: MacOS
- Languag: English
- Distribution: binary
- Version: 4.13
To reproduce:
- CREATE TABLE dates_test(dates DATERANGE[]);
- INSERT INTO dates_test VALUES ('{"(2016-01-01,2017-01-01)"}'::DATERANGE[]);
- SELECT dates FROM dates_test;
- shows nothing in Data Output in pgAdmin
- SELECT dates::VARCHAR FROM public.dates_test;
- works as expected and shows the one inserted row as {"[2016-01-02,2017-01-01)"}
- works as expected and shows the one inserted row as {"[2016-01-02,2017-01-01)"}
A coworker on Windows 10 has the same problem.
Regards,
Manuel Hegner
Thanks for reporting the issue.
RM logged: https://redmine.postgresql.org/issues/2258
--
Regards,
On Wed, Mar 15, 2017 at 8:12 PM, Manuel Hegner <manuel.hegner@bakdata.com> wrote:
I found an issue in PgAdmin. It seems the UI is not able to render arrays of dateranges and thus displays nothing at all.
- Platform: MacOS
- Languag: English
- Distribution: binary
- Version: 4.13
To reproduce:
- CREATE TABLE dates_test(dates DATERANGE[]);
- INSERT INTO dates_test VALUES ('{"(2016-01-01,2017-01-01)"}'
::DATERANGE[]); - SELECT dates FROM dates_test;
- shows nothing in Data Output in pgAdmin
- SELECT dates::VARCHAR FROM public.dates_test;
- works as expected and shows the one inserted row as {"[2016-01-02,2017-01-01)"}
A coworker on Windows 10 has the same problem.
Regards,
Manuel Hegner