[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       |  
------------------------------+---------------------------------------------
Changes (by mlennert):

  * priority:  blocker => normal


Comment:

 Replying to [comment:42 neteler]::
 > > > > Replying to [comment:34 hamish]:

 > > > > > You may be seeing the effect of the db.* modules only working
 for databases linked from maps in the current mapset


 > 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"

 The current test is this:

 {{{

     if (db_describe_table(driver, &table_name, &table) != DB_OK)
         G_fatal_error(_("Unable to describe table <%s>"),
 db_get_string(&table_name));
 }}}

 i.e. it justs checks whether it can describe the table and if not it
 fails. No attempt to no why it cannot describe the table (table does not
 exist in this mapset, bad spelling, etc). As the module does allow you to
 define the driver and database (meaning that you can actually describe a
 table in any database, not only tables in a database linked to a GRASS
 mapset), the issue is larger than just mapsets. I would suggest something
 like:


 {{{
 ERREUR :Unable to describe table <overpasses>. Check database connection
         information.
 }}}

 and adding a few lines to the manual.

 I'm attaching a relevant patch proposal.

 In any case, I'm downgrading this bug's priority.

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