-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Can't edit GeoPackage using SQL through DBManager #26773
Comments
Author Name: julie - (julie -) Similar problem here, with QGIS 3.2 and Ubuntu 16.04 (xenial). When clicking on SQL Window icon, I get same error message : File "/usr/share/qgis/python/plugins/db_manager/db_manager.py", line 195, in runSqlWindow |
Author Name: Daniel Victoria (Daniel Victoria) I'm also having this issue. QGis v3.2.0-Bonn on Ubuntu 16.04 (xenial). Loaded a shapefile in QGis and opened DB Manager. I can see the layer info, table and preview. But when I click on SQL Window, I get the same error reported by julie: @2018-07-05T16:13:20 WARNING Traceback (most recent call last): |
Author Name: Nyall Dawson (@nyalldawson) Already fixed in master /3.2.1
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: James Passmore (@nmtoken)
Original Redmine Issue: 18941
Affected QGIS version: 3.1(master)
Redmine category:db_manager
At work, using QGIS 3.0.1 on Windows, I can edit a GeoPackage created by QGIS by running SQL in DBManager, great!
However, at home using QGIS 3 master on Linux I can't.
I get Python error:
2018-05-12T06:44:10 WARNING Traceback (most recent call last):
File "/usr/share/qgis/python/plugins/db_manager/db_manager.py", line 195, in runSqlWindow
query = DlgSqlWindow(self.iface, db, self)
File "/usr/share/qgis/python/plugins/db_manager/dlg_sql_window.py", line 99, in init
self.btnCancel.setShortcut(QKeySequence.Cancel)
AttributeError: type object 'QKeySequence' has no attribute 'Cancel'
The GeoPackage was created in the Linux QGIS app, but when clicking on the SQL Window icon, I get the error above.
Related issue(s): #27137 (duplicates)
Redmine related issue(s): 19309
The text was updated successfully, but these errors were encountered: