https://issues.qgis.org/https://issues.qgis.org/favicon.ico2007-07-20T14:09:38ZQGIS Issue TrackingQGIS Application - Bug report #741: identify not working for some postgis layershttps://issues.qgis.org/issues/741?journal_id=155252007-07-20T14:09:38ZRedmine Admin
<ul></ul><p>Further, when the tool does identify a feature (i.e. neither of the aforementioned problems raise an error and aborts the transaction) the primary key of the table always comes back as 0. Also affects the attribute table.</p> QGIS Application - Bug report #741: identify not working for some postgis layershttps://issues.qgis.org/issues/741?journal_id=155262007-11-16T14:39:19ZGary Shermansherman@mrcc.com
<ul><li><strong>Resolution</strong> set to <i>fixed</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>Patch applied. Please test to make sure it solves the issue and doesn't introduce any other issues.</p> QGIS Application - Bug report #741: identify not working for some postgis layershttps://issues.qgis.org/issues/741?journal_id=155272007-11-16T22:31:44ZMarco Hugentoblermarco.hugentobler@sourcepole.ch
<ul><li><strong>Resolution</strong> deleted (<del><i>fixed</i></del>)</li><li><strong>Status</strong> changed from <i>Closed</i> to <i>Feedback</i></li></ul><p>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.</p>
<p>The problem with the primary key coming as 0 has already been adressed in a former fix.</p> QGIS Application - Bug report #741: identify not working for some postgis layershttps://issues.qgis.org/issues/741?journal_id=155282007-11-17T06:12:04ZGary Shermansherman@mrcc.com
<ul></ul><p>So is the issue only the handling of bytea fields?</p> QGIS Application - Bug report #741: identify not working for some postgis layershttps://issues.qgis.org/issues/741?journal_id=155292007-11-17T08:24:44ZJürgen Fischerjef@norbit.de
<ul><li><strong>Resolution</strong> set to <i>fixed</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>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.</p>
<p>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.</p>
<p>I did that with <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/f35fb37d8eaa27a9dd9b61a50c88eece6bdedbb5" title="quote identifiers and ignore bytea columns, fix for #741 git-svn-id: http://svn.osgeo.org/qgis/t...">f35fb37d</a> (SVN r7444).</p> QGIS Application - Bug report #741: identify not working for some postgis layershttps://issues.qgis.org/issues/741?journal_id=155302009-08-21T22:52:53ZAnonymous
<ul></ul><p>Milestone Version 0.9.1 deleted</p>