[GRASS-dev] [GRASS GIS] #93: db.table -p does not list all tables -> deeper problems in PostgreSQL driver

GRASS GIS trac at osgeo.org
Wed Mar 12 06:56:18 EDT 2008

#93: db.table -p does not list all tables -> deeper problems in PostgreSQL
 Reporter:  harrikoo                                   |       Owner:  grass-dev at lists.osgeo.org
     Type:  defect                                     |      Status:  new                      
 Priority:  major                                      |   Milestone:                           
Component:  default                                    |     Version:  svn-trunk                
 Keywords:  PostgreSQL database db.table v.db.connect  |  
 Hi all,

 first of all, I noticed, that `db.tables -p` does not list all tables in
 the database any more - it seems to list all the views, but some of the
 tables not. This is not a matter of access rights, all the tables were
 created succesfully by GRASS itself, and database links from vectors to
 these tables work, and the data is useable, too - the tables just are not
 visible in the printout of db.tables.

 This leads to another problem: it is not possible to create a new database
 link for a vector to a table that is not visible in `db.table -p`,
 althought the table does exist in the database. I did try this many times,
 so I'm quite certain it's not a typo.

 The bug seems to be consistent, though; restarting GRASS and PostgreSQL do
 not change the fact, whether the table is visible or not.
 Also, from the PostgreSQL side, there does not seem to be any differences
 between the tables that are visible and the ones that are not, but the
 problem obviously is not limited to db.tables.

 I'd be happy to provide some more information, if you just point me to
 what might be of interest.

 Harri K.

Ticket URL: <http://trac.osgeo.org/grass/ticket/93>
GRASS GIS <http://grass.osgeo.org>
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/

More information about the grass-dev mailing list