[GRASS-dev] [GRASS GIS] #1866: broken db driver communication in winGRASS 7

[GRASS GIS]

#1866: broken db driver communication in winGRASS 7
------------------------------+---------------------------------------------
 Reporter:  martinl           |       Owner:  grass-dev@…              
     Type:  defect            |      Status:  new                      
 Priority:  normal            |   Milestone:  7.0.0                    
Component:  Database          |     Version:  unspecified              
 Keywords:  sqlite, wingrass  |    Platform:  MSWindows 2K             
      Cpu:  Unspecified       |  
------------------------------+---------------------------------------------

Comment(by mmetz):

 Replying to [comment:42 neteler]:
 > Replying to [comment:41 mlennert]:
 > > Replying to [comment:39 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?
 >
 > No. I tried from the user1 mapset.
 >
 > > > > > You may be seeing the effect of the db.* modules only working
 for databases linked from maps in the current mapset

 This is not true. All db.* modules (should) have an option to define the
 database and driver, as for example db.describe, which can describe any
 table in any database, as long as the driver is supported.
 >
 > Right. So we need a test for that rather than failing with a slightly
 > obscured error message. Or expand it to say:
 >
 > "Table <%s> not found in current mapset"

 Better:
 "Table <%s> not found in database <%s> using driver <%s>"

 Done in r57260.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1866#comment:44>
GRASS GIS <http://grass.osgeo.org>