What is the bug or the crash?
When reading a column from a GeoPackage file (exported by QGIS itself from a PostGIS view) that contains a jsonb column, having verified that the data is correctly saved in it via SQLite DB Browser), the column is read incorrectly in the attribute pane:
- if the column contains an object, QGIS shows only the key names instead of the object
- if the column contains an array, QGIS shows an empty field
The same data loaded directly from the view is shown correctly.
Steps to reproduce the issue
- Load a PostGIS table with a jsonb column with data in it
- check that the attributes are correctly shown, both via the map (feature info tool) and via the attribute table
- export the layer to a geopackage
- open the geopackage
- try to do the same as 2. but the info is not shown correctly
Versions
| QGIS version | 3.42.2-Münster |
| QGIS code revision | 402273f8c2 |
| |
| Libraries |
| Qt version | 5.15.13 |
| Python version | 3.12.10 |
| GDAL version | 3.10.3 |
| PROJ version | 9.6.0 |
| EPSG Registry database version | v12.004 (2025-03-02) |
| GEOS version | 3.13.1-CAPI-1.19.2 |
| SQLite version | 3.46.1 |
| PDAL version | 2.8.3 |
| PostgreSQL client version | 17.3 |
| SpatiaLite version | 5.1.0 |
| QWT version | 6.3.0 |
| QScintilla2 version | 2.14.1 |
| OS version | Windows 11 Version 2009 |
| |
| Active Python plugins |
| batchvectorlayersaver | 0.9 |
| Cxf_in | 9.2 |
| db_manager | 0.1.20 |
| grassprovider | 2.12.99 |
| MetaSearch | 0.3.6 |
| processing | 2.12.99 |
Also:
| QGIS version | 3.44.0-Solothurn |
| QGIS code revision | 5d9ba037df1 |
| |
| Libraries |
| Qt version | 5.15.13 |
| Python version | 3.12.11 |
| GDAL version | 3.11.0 — Eganville |
| PROJ version | 9.6.2 |
| EPSG Registry database version | v12.013 (2025-05-26) |
| GEOS version | 3.13.1-CAPI-1.19.2 |
| SQLite version | 3.46.1 |
| PDAL version | 2.9.0 |
| PostgreSQL client version | 17.3 |
| SpatiaLite version | 5.1.0 |
| QWT version | 6.3.0 |
| QScintilla2 version | 2.14.1 |
| OS version | Windows 11 Version 2009 |
| |
| Active Python plugins |
| batchvectorlayersaver | 0.9 |
| Cxf_in | 9.2 |
| db_manager | 0.1.20 |
| grassprovider | 2.12.99 |
| MetaSearch | 0.3.6 |
| processing | 2.12.99 |
Supported QGIS version
New profile
Additional context
No response
What is the bug or the crash?
When reading a column from a GeoPackage file (exported by QGIS itself from a PostGIS view) that contains a jsonb column, having verified that the data is correctly saved in it via SQLite DB Browser), the column is read incorrectly in the attribute pane:
The same data loaded directly from the view is shown correctly.
Steps to reproduce the issue
Versions
Also:
Supported QGIS version
New profile
Additional context
No response