Bug report #13521

Won't list postgres columns of json or jsonb type

Added by Brian Freed over 8 years ago. Updated almost 5 years ago.

Affected QGIS version:2.10.1 Regression?:No
Operating System:Windows 64-bit Easy fix?:No
Pull Request or Patch supplied:No Resolution:end of life
Crashes QGIS or corrupts data:No Copied to github as #:21565


QGIS doesn't seem to display postgresql json/jsonb columns at all.
Both tables and views.

CREATE TABLE json_text (id serial primary key, the_data TEXT, geog geography(point, 4326));
INSERT INTO json_text (the_data, geog) VALUES ($${"one": 1}$$, ST_MakePoint(-80, 40));

ADD TO QGIS >> see the_data.

CREATE VIEW as_json AS SELECT id, the_data::json as the_data, geog FROM json_text;

ADD TO QGIS >> no the_data in Layer Properties / Fields.


#1 Updated by Vladimir Rutsky over 7 years ago

Any progress on this issue?

The issue can be reproduced on QGIS 2.14.1-Essen on GNU/Linux 64-bit.

#2 Updated by Jean-Gabriel JGH almost 7 years ago


it is still the case with 2.18.4. I am using the json datatype in a spatial view - though the geometry column is one of its own. The Json columns are ignored (not even listed in the layer field property).

To overcome the issue I have to convert to Text in my view definition
select myJsonCol::Text, jsonb_pretty(myJsonBcol), geom from myTable. it works OK for display (and the true json(b) column remains available in Postgres)


#3 Updated by Giovanni Manghi almost 7 years ago

  • Easy fix? set to No
  • Regression? set to No

#4 Updated by Jürgen Fischer over 6 years ago

  • Category set to Unknown

#5 Updated by Giovanni Manghi almost 5 years ago

  • Status changed from Open to Closed
  • Resolution set to end of life

End of life notice: QGIS 2.18 LTR


QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.

Also available in: Atom PDF