Bug report #14219: DB manager error when using "move to schema" - QGIS Application - QGIS Issue Tracking

Bug report #14219

DB manager error when using "move to schema"

Added by Giovanni Manghi almost 9 years ago. Updated over 8 years ago.

Status:	Closed
Priority:	High
Assignee:	Sebastian Dietrich
Category:	DB Manager
Affected QGIS version:	master	Regression?:	No
Operating System:		Easy fix?:	No
Pull Request or Patch supplied:	Yes	Resolution:
Crashes QGIS or corrupts data:	No	Copied to github as #:	22219

Description

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'

Associated revisions

Revision 0ab36538
Added by Sebastian Dietrich over 8 years ago

[DbManager] Fix the 'MoveToSchema' functionality (fixes #14219)

Revision 25c28944
Added by Jürgen Fischer over 8 years ago

Merge pull request #2789 from SebDieBln/DbManager_FixMoveToSchema

[DbManager] Fix the 'MoveToSchema' functionality (fixes #14219)

History

#1 Updated by Sebastian Dietrich over 8 years ago

Priority changed from Severe/Regression to High
Assignee set to Sebastian Dietrich
Status changed from Open to In Progress

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?