-
-
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
DBManager: spatial indexes are not reamed when a table is renamed #29253
Comments
Author Name: Giovanni Manghi (@gioman) Does it happens in a previous release? only after renaming a table or also after deleting one?
|
Author Name: Pedro Venâncio (Pedro Venâncio) Ok, I've been digging more in this issue and:
This only happens after renaming a table, without renaming the correspondent spatial index. Dropping the table, the spatial index goes with it.
|
Author Name: Giovanni Manghi (@gioman)
|
But should they be renamed? As far as I can see, pgadmin does not rename dependent objects when renaming a table. Also if we choose to go with renaming, we will need to rename not only indexes but also all other objects like sequences, views, triggers, etc which maybe error prone in automatic mode. |
@PedroVenancio what about this comment from @alexbruy ? |
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". |
While we hate to see this happen, this Issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue. |
Author Name: Pedro Venâncio (Pedro Venâncio)
Original Redmine Issue: 21436
Affected QGIS version: 3.6.0
Redmine category:db_manager
DBManager throws an error when importing a new layer to PostGIS, and the layer name is the same of an old layer already in PostGIS (name meanwhile changed). As the old layer name had a spatial index with the same name structure (sidx_ + layer_name + _the_geom) of the new layer name, DBManager throws an error, instead of show an warning window or so.
The text was updated successfully, but these errors were encountered: