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

[Bug]PostgreSQL execute SQL processing tool raise QGIS quit abnormally #36641

Closed
sshuair opened this issue May 22, 2020 · 0 comments · Fixed by #36642
Closed

[Bug]PostgreSQL execute SQL processing tool raise QGIS quit abnormally #36641

sshuair opened this issue May 22, 2020 · 0 comments · Fixed by #36642
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@sshuair
Copy link
Contributor

sshuair commented May 22, 2020

Describe the bug

Processing tool PostgreSQL execute SQL raise quit abnormally

How to Reproduce

  1. Go to 'processing' -- > database-- > PostgreSQL execute SQL
  2. Execute an SQL query
  3. Then click the Parameters
  4. QGIS will quit.

QGIS and OS versions

QGIS version 3.13.0-Master QGIS code revision 0d54cac
Compiled against Qt 5.12.3 Running against Qt 5.12.3
Compiled against GDAL/OGR 2.4.1 Running against GDAL/OGR 2.4.1
Compiled against GEOS 3.7.2-CAPI-1.11.2 Running against GEOS 3.7.2-CAPI-1.11.2 b55d2125
Compiled against SQLite 3.28.0 Running against SQLite 3.28.0
PostgreSQL Client Version 11.3 SpatiaLite Version 4.3.0a
QWT Version 6.1.4 QScintilla2 Version 2.11.1
Compiled against PROJ 5.2.0 Running against PROJ Rel. 5.2.0, September 15th, 2018
OS Version macOS 10.15
@sshuair sshuair added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 22, 2020
@nyalldawson nyalldawson self-assigned this May 22, 2020
nyalldawson added a commit to nyalldawson/QGIS that referenced this issue May 22, 2020
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!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants