Skip to content
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

Closed
qgib opened this issue Mar 28, 2012 · 6 comments
Closed

MSSQL Estimated table parameter is not used #14986

qgib opened this issue Mar 28, 2012 · 6 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Mar 28, 2012

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?

@qgib
Copy link
Contributor Author

qgib commented Apr 1, 2012

Author Name: Tamas Szekeres (@szekerest)


Fixed in git@github.com:szekerest/Quantum-GIS.git

@qgib
Copy link
Contributor Author

qgib commented Apr 1, 2012

Author Name: Tamas Szekeres (@szekerest)


Fixed in changeset "51011559c4d7cdb5a11e50cae23a20b688df2b77".


  • status_id was changed from Open to Closed

@qgib
Copy link
Contributor Author

qgib commented Apr 1, 2012

Author Name: Jeremy Palmer (@palmerj)


Thanks. Can this stuff be backported to 1.8?


  • assigned_to_id was changed from Tamas Szekeres to Jürgen Fischer

@qgib
Copy link
Contributor Author

qgib commented Apr 9, 2012

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
Jeremy


  • status_id was changed from Closed to Reopened
  • assigned_to_id was changed from Jürgen Fischer to Tamas Szekeres

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2012

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was changed from Version 1.8.0 to Version 2.0.0

@qgib
Copy link
Contributor Author

qgib commented Oct 1, 2013

Author Name: Tamas Szekeres (@szekerest)


Fixed in changeset "51011559c4d7cdb5a11e50cae23a20b688df2b77".


  • status_id was changed from Reopened to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers labels May 24, 2019
@qgib qgib added this to the Version 2.0.0 milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers
Projects
None yet
Development

No branches or pull requests

1 participant