[GRASSLIST:6747] Re: dbmi protocol error / null-values

[Radim Blazek]

yuhuu at gmx.de wrote:
> Hi,
> any ideas what im doing wrong to get following error-message as soon as a
> table containing NULL-values is queried:
> "dbmi: Protocol error (invalid table/column name or unsupported column
> type)"
> 
> For example:
> 
> step 1:
> echo 'create table soils (cat integer, soiltype varchar(10) )' | db.execute
> 
> step 2:
> echo "INSERT INTO soils (cat,soiltype) values (5,'hello')" | db.execute
> 
> step 3:
> db.select sql='select* from soils'
> results correctly in output:
> cat|soiltype
> 5|hello
> 
> step 4:
> echo "INSERT INTO soils (cat) values (6)" | db.execute
> 
> but now, step 5:
> db.select sql='select* from soils'
> results with error message:
> dbmi: Protocol error (invalid table/column name or unsupported column type)
> 
> I get this always when there is a NULL-value anywhere in one of the queried
> columns, also in other contexts, like v.reclass, d.what.vect etc.
> I suppose this also produces problems in v.digit.
> I got the problem both with dbf and mysql.
> grass version is "grass-6.0.cvs_src_snapshot_2005_05_07" on debian
> 
> Thanks
> Jones
> 

Fixed in CVS, until you update, you can use

echo "INSERT INTO soils (cat,soiltype) values (5,null)" | db.execute

Radim