db.table -p does not list all tables -> deeper problems in PostgreSQL driver

[harrikoo]

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.

[neteler]

Harri,

I tried and did not see that problem. Are you sure that GRANT was properly applied to your DB?

Markus

[neteler]

Replying to harrikoo:

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.

I assume that the mechanism used here is the same. If db.table doesn't see it, also the rest won't see it.

Markus

[mlennert]

Can confirm. Suspect that it is my fault from when adding views to the list of tables. Taking over this ticket.

Moritz

[mlennert]

Fixed in revision 33973.

Moritz