-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSSQL Estimated table parameter is not used #14986
Comments
Author Name: Tamas Szekeres (@szekerest) Fixed in git@github.com:szekerest/Quantum-GIS.git |
Author Name: Tamas Szekeres (@szekerest) Fixed in changeset "51011559c4d7cdb5a11e50cae23a20b688df2b77".
|
Author Name: Jeremy Palmer (@palmerj) Thanks. Can this stuff be backported to 1.8?
|
Author Name: Jeremy Palmer (@palmerj) Hi Tamas, I just re-tested this and it still seems that the estimated metadata parameter is not being used correctly. If the un-tick the "Only look in the geometry_columns metadata table" option large layers take a long time to update in the grid. Also when I add the layer to the canvas it takes a long time too (as it again tries to determine the table geometry type). Once the layer is added to the canvas, if I view the datasource URI in the metadata tab with the layer properties it doesn't have the estimated metadata parameter listed. I'm using revision e54e87f trunk on winxp Cheers
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Tamas Szekeres (@szekerest) Fixed in changeset "51011559c4d7cdb5a11e50cae23a20b688df2b77".
|
Author Name: Jeremy Palmer (@palmerj)
Original Redmine Issue: 5252
Affected QGIS version: master
Redmine category:data_provider
Assignee: Tamas Szekeres
When loading the "Add MS Tables(s)" Dialog and connecting to a MSSQL database, determining the geometry type is very slow for large table, even if the "Use estimated table parameters" option is set for the connection.
Looking at https://github.com/qgis/Quantum-GIS/blob/d212ca7f7174a2063f245e31e27f2848387c1df0/src/providers/mssql/qgsmssqlsourceselect.cpp#L740 is seems like it should be working. Maybe the parameter is not being passed down correctly?
The text was updated successfully, but these errors were encountered: