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

DB manager error when using "move to schema" #22219

Closed
qgib opened this issue Feb 2, 2016 · 3 comments
Closed

DB manager error when using "move to schema" #22219

qgib opened this issue Feb 2, 2016 · 3 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! DB Manager Relating to the DB Manager core plugin High Priority
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Feb 2, 2016

Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 14219
Affected QGIS version: master
Redmine category:db_manager
Assignee: Sebastian Dietrich


In QGIS 2.12 and master the "move to schema" functionality stopped to work

2016-02-02T18:29:40	1	Traceback (most recent call last):
			  File "/usr/share/qgis/python/plugins/db_manager/db_plugins/plugin.py", line 466, in <lambda>
			    slot = lambda x: lambda: mainWindow.invokeCallback(self.moveTableToSchemaActionSlot, [x])
			  File "/usr/share/qgis/python/plugins/db_manager/db_manager.py", line 287, in invokeCallback
			    callback(self.tree.currentItem(), self.sender(), self, *params)
			  File "/usr/share/qgis/python/plugins/db_manager/db_plugins/plugin.py", line 482, in moveTableToSchemaActionSlot
			    item.moveToSchema(new_schema)
			  File "/usr/share/qgis/python/plugins/db_manager/db_plugins/plugin.py", line 650, in moveToSchema
			    ret = self.database().connector.moveTableToSchema((self.schemaName(), self.name), schema.name)
			AttributeError: 'list' object has no attribute 'name'

@qgib
Copy link
Contributor Author

qgib commented Feb 12, 2016

Author Name: Sebastian Dietrich (Sebastian Dietrich)


I am on it.

I set the priority from Blocker to High because it did not block the release of 2.12 and consequently it can not block the release of 2.14 either. Is that correct?


  • priority_id was changed from Severe/Regression to High
  • assigned_to_id was configured as Sebastian Dietrich
  • status_id was changed from Open to In Progress

@qgib
Copy link
Contributor Author

qgib commented Feb 12, 2016

Author Name: Sebastian Dietrich (Sebastian Dietrich)


Regression bisected to 80a13e3.

See "PR 2789":#2789 for a solution.


  • pull_request_patch_supplied was changed from 0 to 1
  • done_ratio was changed from 0 to 100

@qgib
Copy link
Contributor Author

qgib commented Feb 14, 2016

Author Name: Jürgen Fischer (@jef-n)


Fixed in changeset "25c289441ef2074826cf27aac6fb49667e8d9a23".


  • status_id was changed from In Progress to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority DB Manager Relating to the DB Manager core plugin labels May 25, 2019
@qgib qgib added this to the Version 2.14 milestone May 25, 2019
@qgib qgib closed this as completed May 25, 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! DB Manager Relating to the DB Manager core plugin High Priority
Projects
None yet
Development

No branches or pull requests

1 participant