https://issues.qgis.org/https://issues.qgis.org/favicon.ico2016-11-03T04:57:31ZQGIS Issue TrackingQGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=733362016-11-03T04:57:31ZHugues Bernard
<ul></ul><p>The bug is also on the new version 2.18</p>
<p>Additional info, the virtual query is:<br />SELECT * FROM hafa_origin_03 WHERE indicatif LIKE '%03'</p> QGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=775032017-04-30T23:02:09ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Regression?</strong> set to <i>No</i></li><li><strong>Easy fix?</strong> set to <i>No</i></li></ul> QGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=824982017-09-22T07:55:51ZJürgen Fischerjef@norbit.de
<ul><li><strong>Category</strong> set to <i>Unknown</i></li></ul> QGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=858982018-01-18T05:32:56ZNyall Dawson
<ul><li><strong>Resolution</strong> set to <i>fixed/implemented</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li><li><strong>Description</strong> updated (<a href="/journals/diff/85898?detail_id=74532" title="View differences">diff</a>)</li></ul><p>Fixed in 2.18 and 3.0</p> QGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=862242018-01-26T21:02:49ZHugues Bernard
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li></ul><p>The bug isn't fixed in 2.18. With the data joined at this the ticket, the problem is always present.</p>
<p>Tested the 2018-01-26 on version :<br />- rel 2.18.16-1 <br />- rel dev 2.18.16-4</p> QGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=862282018-01-26T23:03:24ZGerhard Spieles
<ul></ul><p>Hi,<br />the behavior is similar to <a class="issue tracker-1 status-1 priority-5 priority-" href="https://issues.qgis.org/issues/15600" title="Selecting features feature in spatial views and virtual layers leads to wrong results (Open)">#15600</a> and spatialite views have the same problem.</p> QGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=862452018-01-27T08:45:36ZJürgen Fischerjef@norbit.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-5 priority-" href="/issues/15600">Bug report #15600</a>: Selecting features feature in spatial views and virtual layers leads to wrong results</i> added</li></ul> QGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=947492018-10-24T10:06:11ZHugo Mercierhugo.mercier@oslandia.com
<ul></ul><p>It is due to the virtual layer that does not have a unique id column defined.</p>
<p>In this case, the "id" will be an incremented integer for each row. The problem is when the identify tool is used, only one row is returned and the resulting id is then 1.</p>
<p>There is no easy way to automate the generation of a unique id for each row. I'm wondering if the right fix would be to prevent the identify tool to be used on layers without unique id.</p> QGIS Application - Bug report #15709: bad match of valeurs with virtual layerhttps://issues.qgis.org/issues/15709?journal_id=948502018-10-26T12:03:48ZHugo Mercierhugo.mercier@oslandia.com
<ul><li><strong>Status</strong> changed from <i>Reopened</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/efe4a79687eef7866de0f02df5bf1950431356aa" title="Fix virtual layer FilterRect handling when no uid is defined (fixes #15709) When no uid if defin...">qgis|efe4a79687eef7866de0f02df5bf1950431356aa</a>.</p>