#809: v.db.addtable consistently fails in winGrass ------------------------------+--------------------------------------------- Reporter: JonBall | Owner: grass-dev@lists.osgeo.org Type: defect | Status: new Priority: critical | Milestone: 6.4.0 Component: Vector | Version: svn-releasebranch64 Resolution: | Keywords: v.db.addtable, wingrass Platform: MSWindows Vista | Cpu: x86-64 ------------------------------+--------------------------------------------- Comment (by mmetz):
Replying to [comment:7 hamish]: > note you have to be using layer 2 or greater to see this. for layer 1 the DB path is still the unparsed "$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/". On the next iteration for layer 2 it is converted to the real expanded path. I think this is a bug. v.db.addtable should always use the default, unparsed database connection settings because there is no database option in v.db.addtable. If a table already exists in layer 1 and a new table is to be added for another layer, v.db.addtable uses the definition for layer 1 as returned by v.db.connect -g which parses "$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/". Suggested fix would be to always use the default unparsed database connection, i.e. skip the check in v.db.addtable lines 119 - 136 (grass64). Markus M -- Ticket URL: <https://trac.osgeo.org/grass/ticket/809#comment:8> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev