https://issues.qgis.org/https://issues.qgis.org/favicon.ico2017-04-30T22:44:10ZQGIS Issue TrackingQGIS Application - Feature request #16252: SDO_DIMNAME values QGIS Oracle Data Providerhttps://issues.qgis.org/issues/16252?journal_id=759682017-04-30T22:44:10ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Easy fix?</strong> set to <i>No</i></li></ul> QGIS Application - Feature request #16252: SDO_DIMNAME values QGIS Oracle Data Providerhttps://issues.qgis.org/issues/16252?journal_id=820242017-09-08T11:35:26ZJürgen Fischerjef@norbit.de
<ul><li><strong>Assignee</strong> deleted (<del><i>Jürgen Fischer</i></del>)</li></ul> QGIS Application - Feature request #16252: SDO_DIMNAME values QGIS Oracle Data Providerhttps://issues.qgis.org/issues/16252?journal_id=929332018-09-17T13:42:47ZLukas Künzellukas.kuenzel@msgis.com
<ul></ul><p>We recently ran into the same problem, we even tend to use complete custom names for the dimensions, because Oracle itself does not need any specific names.</p>
<p>Is there any specific reason why the spatial extent of a layer has to be determined each time? Would it be possible in the future to use the extent that is already stored in the project file? I see some similarities to <a class="wiki-page new" href="https://issues.qgis.org/projects/qgis/wiki/%2319793"><a class="issue tracker-1 status-1 priority-5 priority-" href="https://issues.qgis.org/issues/19793" title="MSSQL: Poor initial QGIS 3.2.2 starting performance when getting data from a MS SQL Server view (Open)">#19793</a></a><br />When you've really large spatial data sets in your database then some of the current methods (like SDO_AGGR_MBR) to determine spatial extent will fail.</p>
<p>Please share your thoughts!</p> QGIS Application - Feature request #16252: SDO_DIMNAME values QGIS Oracle Data Providerhttps://issues.qgis.org/issues/16252?journal_id=936962018-10-01T20:42:15ZLukas Künzellukas.kuenzel@msgis.com
<ul></ul><p>@Jürgen Fischer</p>
<p>Are there any plans to fix this issue?</p>