Обсуждение: Bug when a column is JSON?

Поиск
Список
Период
Сортировка

Bug when a column is JSON?

От
Michael Monerau
Дата:
Hi,

Just ran into this bug when trying to simply list the contents of a table:

image.png

And the DataOutput panel is blank.

It definitely works on other tables, and the connection to the server is ok (it correctly pulls out the 268 rows, and downloading the CSV works ok).

The only difference I can see between this table and others is that it has a "JSON" type column.

Is this a known bug?

Best,
Michael
Вложения

Re: Bug when a column is JSON?

От
Fahar Abbas
Дата:
Hi,

This fix will be available in 4.11 release today.

On Thu, Jul 25, 2019 at 2:21 PM Michael Monerau <michael.monerau@gmail.com> wrote:
Hi,

Just ran into this bug when trying to simply list the contents of a table:

image.png

And the DataOutput panel is blank.

It definitely works on other tables, and the connection to the server is ok (it correctly pulls out the 268 rows, and downloading the CSV works ok).

The only difference I can see between this table and others is that it has a "JSON" type column.

Is this a known bug?

Best,
Michael


--
Fahar Abbas
QMG
EnterpriseDB Corporation
Phone Office: +92-51-835-8874
Phone Direct: +92-51-8466803
Mobile: +92-333-5409707
Skype ID: live:fahar.abbas
Website: www.enterprisedb.com
Вложения

Re: Bug when a column is JSON?

От
Michael Monerau
Дата:
Great thanks!

Le jeu. 25 juil. 2019 à 11:37, Fahar Abbas <fahar.abbas@enterprisedb.com> a écrit :
Hi,

This fix will be available in 4.11 release today.

On Thu, Jul 25, 2019 at 2:21 PM Michael Monerau <michael.monerau@gmail.com> wrote:
Hi,

Just ran into this bug when trying to simply list the contents of a table:

image.png

And the DataOutput panel is blank.

It definitely works on other tables, and the connection to the server is ok (it correctly pulls out the 268 rows, and downloading the CSV works ok).

The only difference I can see between this table and others is that it has a "JSON" type column.

Is this a known bug?

Best,
Michael


--
Fahar Abbas
QMG
EnterpriseDB Corporation
Phone Office: +92-51-835-8874
Phone Direct: +92-51-8466803
Mobile: +92-333-5409707
Skype ID: live:fahar.abbas
Website: www.enterprisedb.com
Вложения

Re: Bug when a column is JSON?

От
richard coleman
Дата:
Fahar, 

We've just gotten the 4.10 release in .deb format.  Will we have to wait until 4.11 or maybe 4.13 until we will see 4.10?

Thanks, 

rik.

On Thu, Jul 25, 2019 at 5:37 AM Fahar Abbas <fahar.abbas@enterprisedb.com> wrote:
Hi,

This fix will be available in 4.11 release today.

On Thu, Jul 25, 2019 at 2:21 PM Michael Monerau <michael.monerau@gmail.com> wrote:
Hi,

Just ran into this bug when trying to simply list the contents of a table:

image.png

And the DataOutput panel is blank.

It definitely works on other tables, and the connection to the server is ok (it correctly pulls out the 268 rows, and downloading the CSV works ok).

The only difference I can see between this table and others is that it has a "JSON" type column.

Is this a known bug?

Best,
Michael


--
Fahar Abbas
QMG
EnterpriseDB Corporation
Phone Office: +92-51-835-8874
Phone Direct: +92-51-8466803
Mobile: +92-333-5409707
Skype ID: live:fahar.abbas
Website: www.enterprisedb.com
Вложения

Re: Bug when a column is JSON?

От
Dave Page
Дата:


On Thu, Jul 25, 2019 at 1:11 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:
Fahar, 

We've just gotten the 4.10 release in .deb format.  Will we have to wait until 4.11 or maybe 4.13 until we will see 4.10?

Neither Fahar nor the rest of the pgAdmin developers have any part in the production of the Debian packages. That is handled by a separate team who produce all the Debian/Ubuntu packages on apt.postgresql.org. 

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

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

Re: Bug when a column is JSON?

От
richard coleman
Дата:
Dave, 

Sorry about the typo in the previous missive, it should have read;
We've just gotten the 4.10 release in .deb format.  Will we have to wait until 4.12 or maybe 4.14 until we will see 4.11?

Otherwise, what platforms does the pgAdmin developers release on?

Since it isn't apparently all of the platforms that pgAdmin4 is developed for, shouldn't the pgAdmin4 developers do so?  If not, shouldn't the triage be better, and the rapid release be slower?  As you are aware, there have been several instances where a new version has broken important functionality in pgAdmin4.  It doesn't do a large portion of the user base any favors if the developers release a fix in the form of a new version a couple of days latter only to leave entire platforms bereft of that solution.

rik.

On Thu, Jul 25, 2019 at 8:14 AM Dave Page <dpage@pgadmin.org> wrote:


On Thu, Jul 25, 2019 at 1:11 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:
Fahar, 

We've just gotten the 4.10 release in .deb format.  Will we have to wait until 4.11 or maybe 4.13 until we will see 4.10?

Neither Fahar nor the rest of the pgAdmin developers have any part in the production of the Debian packages. That is handled by a separate team who produce all the Debian/Ubuntu packages on apt.postgresql.org. 

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

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

Re: Bug when a column is JSON?

От
Dave Page
Дата:


On Thu, Jul 25, 2019 at 1:24 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:
Dave, 

Sorry about the typo in the previous missive, it should have read;
We've just gotten the 4.10 release in .deb format.  Will we have to wait until 4.12 or maybe 4.14 until we will see 4.11?

Otherwise, what platforms does the pgAdmin developers release on?

We build source tarballs, Windows and Mac packages, and the container. RPMs and DEBs are built by the PostgreSQL Yum and Apt teams respectively. Copies bundled with PostgreSQL for Windows and Mac are built by EnterpriseDB.
 

Since it isn't apparently all of the platforms that pgAdmin4 is developed for, shouldn't the pgAdmin4 developers do so? 

Volunteers to contribute are always welcome.

If not, shouldn't the triage be better, and the rapid release be slower?  As you are aware, there have been several instances where a new version has broken important functionality in pgAdmin4.  It doesn't do a large portion of the user base any favors if the developers release a fix in the form of a new version a couple of days latter only to leave entire platforms bereft of that solution.

That is one of the reasons why a number of us have spent significant time recently enhancing the automated testsuite.
 

rik.

On Thu, Jul 25, 2019 at 8:14 AM Dave Page <dpage@pgadmin.org> wrote:


On Thu, Jul 25, 2019 at 1:11 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:
Fahar, 

We've just gotten the 4.10 release in .deb format.  Will we have to wait until 4.11 or maybe 4.13 until we will see 4.10?

Neither Fahar nor the rest of the pgAdmin developers have any part in the production of the Debian packages. That is handled by a separate team who produce all the Debian/Ubuntu packages on apt.postgresql.org. 

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

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


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

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