https://issues.qgis.org/https://issues.qgis.org/favicon.ico2012-06-08T03:31:01ZQGIS Issue TrackingQGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=326812012-06-08T03:31:01ZAndreas Neumann
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Severe/Regression</i></li></ul> QGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=326862012-06-08T07:34:48ZJürgen Fischerjef@norbit.de
<ul></ul><p>Are you querying a postgis layer with "use estimated meta data" checked? Then the feature count is inaccurate, but fast. See also <a href="http://lists.osgeo.org/pipermail/qgis-developer/2010-May/009925.html" class="external">![Qgis-developer] Reverse Changeset 13499</a> and <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/a57968532b75023bdd427028d6a086d056582747" title="document impact of using estimated table metadata (and revert last commit)">a5796853</a></p> QGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=327092012-06-09T15:57:53ZNathan Woodrow
<ul></ul><p>Confirmed with PostGIS using "use estimated meta data" checked. Not really a blocker IMO.</p> QGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=327182012-06-10T01:33:59ZAndreas Neumann
<ul></ul><p>Hi,</p>
<p>Yes - the problem only arises when using "estimated meta data". I don't understand how the "estimated metadata" setting is related to the test filter. Why can't the test filter use a more accurate method?</p>
<p>Shouldn't the estimated meta data setting only speed up the initial table listing of the PostgreSQL provider?</p>
<p>If the issue can't be solved - can't we at least issue a warning that with the setting "use estimated metadata" the test filter returns wrong results?</p>
<p>Thanks,<br />Andreas</p> QGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=327202012-06-10T01:52:37ZJürgen Fischerjef@norbit.de
<ul><li><strong>Priority</strong> changed from <i>Severe/Regression</i> to <i>Normal</i></li></ul><p>Andreas Neumann wrote:</p>
<blockquote>
<p>Yes - the problem only arises when using "estimated meta data". I don't understand how the "estimated metadata" setting is related to the test filter. Why can't the test filter use a more accurate method?</p>
</blockquote>
<p>Because the query builder is provider independant. it just set a subset string and retrieves the feature count.</p>
<blockquote>
<p>Shouldn't the estimated meta data setting only speed up the initial table listing of the PostgreSQL provider?</p>
</blockquote>
<p>No, it speeds up querying large layers in general.</p>
<blockquote>
<p>If the issue can't be solved - can't we at least issue a warning that with the setting "use estimated metadata" the test filter returns wrong results?</p>
</blockquote>
<p>The impact of "use estimated table metadata" is documented in the help of the dialog where you enable it - and it's not default.</p>
<p>We could introduce an accurate feature count option - but that would change the provider interface.</p> QGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=347812012-09-04T10:06:44ZPaolo Cavallinicavallini@faunalia.it
<ul><li><strong>Target version</strong> set to <i>Version 2.0.0</i></li></ul> QGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=536972014-06-28T05:42:05ZJürgen Fischerjef@norbit.de
<ul><li><strong>Target version</strong> changed from <i>Version 2.0.0</i> to <i>Future Release - Lower Priority</i></li></ul> QGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=753532017-03-29T00:37:30ZAndreas Neumann
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>fixed/implemented</i></li></ul><p>Apparently this works find now, at least for PostgreSQL layers.</p> QGIS Application - Bug report #5769: Test filter in old query builder incorrecthttps://issues.qgis.org/issues/5769?journal_id=820492017-09-08T11:56:21ZJürgen Fischerjef@norbit.de
<ul><li><strong>Duplicated by</strong> <i><a class="issue tracker-1 status-5 priority-4 priority- closed" href="/issues/16915">Bug report #16915</a>: estimatedmetadata=true parameter on postgres datasource reports wrong number of features when filtering layer</i> added</li></ul>