#1866: broken db driver communication in winGRASS 7 ------------------------------+--------------------------------------------- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: blocker | Milestone: 7.0.0 Component: Database | Version: unspecified Keywords: sqlite, wingrass | Platform: MSWindows 2K Cpu: Unspecified | ------------------------------+---------------------------------------------
Comment(by mlennert): Replying to [comment:38 neteler]: > Replying to [comment:34 hamish]: > > Replying to [comment:33 neteler]: > > > I have tried with r56943 on Windows8, still failing: > > {{{ > > > GRASS 7.0.svn> db.describe overpasses > > ... > > is the overpass vector map in the current mapset? You may be seeing the effect of the db.* modules only working for databases linked from maps in the current mapset, unless you explicitly set database= to the real path, not the default which may expand $MAPSET to the current mapset, not the other mapset's dir name. > > In fact it was in a different mapset (PERMANENT). But it should not hang > (instead it should report that the table was not found in the current mapset). Does it really hand, or does it fail and give back the prompt after the error message ? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1866#comment:39> GRASS GIS <http://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev