Feature request #8689
Oracle provider - speed of listing
|Pull Request or Patch supplied:||No||Resolution:|
|Easy fix?:||No||Copied to github as #:||17410|
Not sure if this qualifies as a bug or feature request.
My Oracle is listing several hundred tables (500?), the problem is that the scanning for the metadata for these tables can take an unreasonably long time. Take the following, all done during the same QGIS-session:
First time. - 117seconds to list everything on our live database "Only look in meta data table" "use estimated table metadata" "only existing geometry types" were all selected. Second time (without having closed QGIS remember!) - 63 seconds. The third time (instantly after the second) - 3 seconds. Fourth time - 11 seconds
There are two things here:
a) If a full scan of everything must be made, can the results be stored locally/in memory for the session? If QGIS feels paranoid, when a user has selected a layer to add it, QGIS can re-scan that table to make sure stuff hasn't changed.
b) The better option IMHO - don't scan the metadata until the user is actually adding it to QGIS. Most users probably don't care what the SRID, Geometry column, or datatype is when they're adding their data so won't miss it on that screen. You could add a checkbox for it to show it (or not show it, depends on the default).
I think both of these would provide considerable increases to the speed of listing tables in the QGIS Oracle provider where there are lots of tables.
#3 Updated by Ken Karlsson over 4 years ago
We have the same problem, but we have to wait for hours before all tables are listed when trying to add an Oracle Spatial-layer.
We would like to be able to first choose the table we want to add, and then only scan that table's metadata when added if necessary.
This issue seems to be open, but is anyone working on this?
We are using QGIS 2.14.1.
Thanks in advance!
Best regards, Ken Karlsson
#5 Updated by Russell Foster about 3 years ago
At work we have recently been trialling QGIS as an alternative to some proprietary GIS's. The problem outlined above is our main issue with the software. It takes so long to scan the database tables, gathering all the info it wants. We have connections to databases that have hundreds of spatial objects available, and directories with hundreds of files. It would make sense to use Jonathan's option 'b' to us (mentioned above). We know what we're looking for in the databases, we know it's going to be in the projection we made it, all we need are a list of names so we can click on one to add. A simple query on a spatial db could simply cross check with say ALL_SDO_GEOM_METADATA (for Oracle) just to make sure something is spatial, and that would be enough. The details only become important when trying to add the layer. I hope this is something that gets fixed in later versions, because so much about QGIS is positive, and a great piece of software. I'd hate to see it not implemented fully at work because of this one issue, but we don't have time to sit around waiting for it to finally list the one layer we're interested in adding.