Bug report #741
identify not working for some postgis layers
|Affected QGIS version:||Regression?:||No|
|Operating System:||All||Easy fix?:||No|
|Pull Request or Patch supplied:||Resolution:||fixed|
|Crashes QGIS or corrupts data:||Copied to github as #:||10800|
Identify returns no features found when in fact features are within the region clicked.
Looking at the query sent to the server it seems that there are two problems:
- the column names aren't being properly quoted so this will raise an error and abort the xaction.
- all columns are being converted to text and not all columns are convertible to text. In my case I had a bytea column and that raised an error which aborted the transaction.
This might also affect the attribute table.
#3 Updated by Marco Hugentobler almost 14 years ago
- Resolution deleted (
- Status changed from Closed to Feedback
The problem with this patch is that all the numeric columns now appear as 0. This is because their values are now transfered in binary format, but in the postgresprovider, they are interpreted as strings.
The problem with the primary key coming as 0 has already been adressed in a former fix.
#5 Updated by Jürgen Fischer almost 14 years ago
- Resolution set to fixed
- Status changed from Feedback to Closed
the quoting part looks like a good thing. You could have mixed-case or uppercase column names that postgres will choke on unless properly quoted.
There's no support for BLOB attributes in QGIS anywhere anyway, so it's probably best to simply ignore columns that are of unsupported types, ie. bytea and maybe more.
I did that with f35fb37d (SVN r7444).