#2353: v.univar says type not supported instead of column does not exist
----------------------------------------+-----------------------------------
 Reporter:  wenzeslaus                  |       Owner:  grass-dev@…             
 
     Type:  enhancement                 |      Status:  new                     
 
 Priority:  trivial                     |   Milestone:  7.1.0                   
 
Component:  Database                    |     Version:  svn-trunk               
 
 Keywords:  v.univar, vector, messages  |    Platform:  All                     
 
      Cpu:  Unspecified                 |  
----------------------------------------+-----------------------------------
 G7:v.univar with column which does not exists reports low-level message
 "no such column" tow times together with some other things and than gives
 GRASS standard error "Column type not supported". It should end after the
 first try, not print the low-level (detailed) messages (if possible,
 should go to debug), and print the correct error message ""Column does not
 exist" (or "not found"?).

 {{{
 v.univar map=bridges column='YEAR_BUILTTT'
 }}}

 {{{
 DBMI-SQLite driver error:
 Error in sqlite3_prepare():
 SELECT cat, YEAR_BUILTTT FROM bridges
 no such column: YEAR_BUILTTT

 DBMI-SQLite driver error:
 Error in sqlite3_prepare():
 SELECT cat, YEAR_BUILTTT FROM bridges
 no such column: YEAR_BUILTTT

 ERROR: Column type not supported
 }}}

 I was not looking to the source code.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2353>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to