I’ve recreated it again

See attached screenshot



For info the JSON for id 6343 is [{"name":"people_and_property","app_id":37}]

Field 8256 is [“whole..”,”.. ….]

I have conformed the issue exists with another field that is of type [{ …}]

It appears to be an issue with arrays

Dave Barter
d...@phased.co.uk
@citizenfishy
www.phased.co.uk

> On 19 Sep 2016, at 14:51, Murtuza Zabuawala 
> <murtuza.zabuaw...@enterprisedb.com> wrote:
> 
> Hi,
> 
> I tried many times opening/closing grid with table definition & sample data 
> given by Dave but without inherits option but no luck in re-producing the 
> issue on my side.
> 
> Regards,
> Murtuza
> 
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com <http://www.enterprisedb.com/>
> The Enterprise PostgreSQL Company
> 
> On Mon, Sep 19, 2016 at 6:26 PM, Dave Barter <d...@phased.co.uk 
> <mailto:d...@phased.co.uk>> wrote:
> Interestingly shutting down and restarting PGAdmin and the issue has gone 
> away. I will try and recreate again.
> 
> If it makes a difference the table was inherited
> 
> CREATE TABLE ng_customer.files
> (
>     file_id integer,
>     file_name text,
>     file_path text,
>     file_attributes json,
>     record_count integer,
>     status character,
>     date_uploaded timestamp without time zone,
>     CONSTRAINT files_pkey PRIMARY KEY (file_id)
> )
>     INHERITS (ng_toplevel.files)
> WITH (
>     OIDS = FALSE
> )
> 
> 
> Dave Barter
> d...@phased.co.uk <mailto:d...@phased.co.uk>
> @citizenfishy
> www.phased.co.uk <http://www.phased.co.uk/>
>> On 19 Sep 2016, at 13:41, Murtuza Zabuawala 
>> <murtuza.zabuaw...@enterprisedb.com 
>> <mailto:murtuza.zabuaw...@enterprisedb.com>> wrote:
>> 
>> Hi Dave,
>> 
>> I am able to see the json data properly in with pgadmin4-1.0-rc1.dmg file on 
>> my mac machine,
>> Please find screenshot attached.
>> 
>> 
>> @Dave Barter,
>> Could you please share screenshot or your table definition, so that I can 
>> re-produce the issue?
>> 
>> 
>> Regards,
>> Murtuza
>> 
>> --
>> Regards,
>> Murtuza Zabuawala
>> EnterpriseDB: http://www.enterprisedb.com <http://www.enterprisedb.com/>
>> The Enterprise PostgreSQL Company
>> 
>> On Mon, Sep 19, 2016 at 5:37 PM, Dave Page <dp...@pgadmin.org 
>> <mailto:dp...@pgadmin.org>> wrote:
>> OK, thanks.
>> 
>> On Mon, Sep 19, 2016 at 1:06 PM, Murtuza Zabuawala
>> <murtuza.zabuaw...@enterprisedb.com 
>> <mailto:murtuza.zabuaw...@enterprisedb.com>> wrote:
>> > Hi Dave,
>> >
>> > I was aware of that issue and that's why I also tested SlickGrid JSON
>> > support(in browsers) when I integrated it :)
>> > Seems like issue with runtime's webkit, let me check & confirm.
>> >
>> > --
>> > Regards,
>> > Murtuza Zabuawala
>> > EnterpriseDB: http://www.enterprisedb.com <http://www.enterprisedb.com/>
>> > The Enterprise PostgreSQL Company
>> >
>> > On Mon, Sep 19, 2016 at 5:19 PM, Dave Page <dp...@pgadmin.org 
>> > <mailto:dp...@pgadmin.org>> wrote:
>> >>
>> >> Murtuza,
>> >>
>> >> On Mon, Sep 19, 2016 at 12:22 PM, Dave Barter <d...@phased.co.uk 
>> >> <mailto:d...@phased.co.uk>> wrote:
>> >> > Apologies if I have missed this elsewhere
>> >> >
>> >> > JSON columns in tables are appearing as [Object object] when viewing
>> >> > data so you cannot edit or view json as you used  to be able to do in
>> >> > pagadmin3
>> >> >
>> >> > I am using pgadmin 4 1.0-rc1 on Mac OSX
>> >> >
>> >> > Is this by design or a bug?
>> >>
>> >> Is this a regression following https://redmine.postgresql.org/issues/1404 
>> >> <https://redmine.postgresql.org/issues/1404>?
>> >>
>> >> --
>> >> Dave Page
>> >> Blog: http://pgsnake.blogspot.com <http://pgsnake.blogspot.com/>
>> >> Twitter: @pgsnake
>> >>
>> >> EnterpriseDB UK: http://www.enterprisedb.com 
>> >> <http://www.enterprisedb.com/>
>> >> The Enterprise PostgreSQL Company
>> >
>> >
>> 
>> 
>> 
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com <http://pgsnake.blogspot.com/>
>> Twitter: @pgsnake
>> 
>> EnterpriseDB UK: http://www.enterprisedb.com <http://www.enterprisedb.com/>
>> The Enterprise PostgreSQL Company
>> 
>> <JSON_data-min.jpg>
> 
> 

Reply via email to