Bug report #8361

DB Manager Versioning

Added by Chris Smit almost 11 years ago. Updated almost 11 years ago.

Status:Closed
Priority:Normal
Assignee:Giovanni Manghi
Category:DB Manager
Affected QGIS version:master Regression?:No
Operating System:Windows Easy fix?:No
Pull Request or Patch supplied:No Resolution:up-/downstream
Crashes QGIS or corrupts data:No Copied to github as #:17141

Description

Under the Table tab in the DB Manager there is a Versioning option. When I run it I get a "language "SQL" does not exist" error when I try to version a table located in PostGIS 2. Please see image. Any suggestions?
Thanks

error.JPG (46.2 KB) Chris Smit, 2013-07-25 05:41 AM

error2.JPG (49.7 KB) Chris Smit, 2013-07-26 03:30 AM

History

#1 Updated by Giovanni Manghi almost 11 years ago

  • Operating System changed from Win 7 to Windows
  • Affected QGIS version changed from 1.8.0 to master
  • Priority changed from High to Normal

It works fine on Linux. Maybe it is something missing in a standard postgresql/postgis installation on Windows.

#2 Updated by Chris Smit almost 11 years ago

  • File error2.JPG added
  • Assignee set to Giovanni Manghi

You will have to excuse my programming/SQL abilities as it is non existent. However, in the newly attached image the first language is SQL and the second refers to plpgsql (both circled in red). Is this correct?

I do not understand most of the code/SQL so I am applying a "spot-the-difference" approach to solving this problem.

#3 Updated by Giovanni Manghi almost 11 years ago

  • Resolution set to up-/downstream
  • Status changed from Open to Closed

Chris Smit wrote:

You will have to excuse my programming/SQL abilities as it is non existent. However, in the newly attached image the first language is SQL and the second refers to plpgsql (both circled in red). Is this correct?

I do not understand most of the code/SQL so I am applying a "spot-the-difference" approach to solving this problem.

anyway I tested with qgis/windows and a postgis/linux server, and it works, so it is not a db manager/qgis issue.

Also available in: Atom PDF