On Wed, May 9, 2012 at 5:29 PM, Falko Engel <[email protected]> wrote: > Dear list, > > I had a strange behavior of v.buffer today: > > v.buffer input=mydata output=mydata_buf bufcolumn=my_buf_col > > results in an error: > > "DBMI-Postgres driver error: > Cannot select: > SELECT cat, my_buf_col FROM mydata" > > > However, if I copy the exact statement of the error message into > > echo "SELECT cat, my_buf_col FROM mydata" | db.select > > the result is fine!
You could set this: g.gisenv set=DEBUG=3 then relaunch the command to see if the more detailed output contains relevant pieces (to post here, not all please :-). To disable debug output, use g.gisenv set=DEBUG=0 Markus ... > I'm using the following setup: > Opensuse 11.3, GRASS GIS 6.4.2 > > My attribute tables are stored in a Postgres DB which is located on a > network server. > All other DB operations in GRASS are fine. > > > Falko > > _______________________________________________ > grass-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-user _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
