[GRASS-dev] [GRASS GIS] #2796: PostgreSQL database connections fail in some parts of the gui

#2796: PostgreSQL database connections fail in some parts of the gui
------------------------+-------------------------
Reporter: harrik | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone:
Component: Database | Version: 7.0.1
Keywords: PostgreSQL | CPU: x86-64
Platform: Linux |
------------------------+-------------------------
Hi!

I tested the 7.0.2RC2, and noticed, that the database connections for my
vectors from 6.4 did not work anymore with the new GUI. The attribute
table is shown ok, but the display of labels and editing of attributes in
the digitizer do not work: if I try to display labels for the vector
features, the map stays empty, and neither the features nor labels are
shown; without labels, the features are shown fine. The digitizer opens
fine, but trying to see the attributes, or adding attributes to a newly
drawn feature fail with no clear error messages.

From what I gathered, it seems that the setting for the "schema" in the
database is not taken into account, for example the connection for vector
"struct" used to be to the postgres table "grass.struct", where "grass" is
the schema set up with db.connect. However, this version of GRASS seems to
try to access the table using just the name "struct", which will lead to
error.

Best,

Harri K.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2796&gt;
GRASS GIS <https://grass.osgeo.org>

#2796: PostgreSQL database connections fail in some parts of the gui
-----------------------+-------------------------
  Reporter: harrik | Owner: grass-dev@…
      Type: defect | Status: closed
  Priority: normal | Milestone:
Component: Database | Version: 7.0.1
Resolution: invalid | Keywords: PostgreSQL
       CPU: x86-64 | Platform: Linux
-----------------------+-------------------------
Changes (by harrik):

* status: new => closed
* resolution: => invalid

Comment:

Sorry, this bug is not actually there. I don't actually know what was the
problem, but suddenly the vector-database-connections began working as
they should.

Closing as invalid.

Best,

Harri

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2796#comment:1&gt;
GRASS GIS <https://grass.osgeo.org>