Does anyone know how to resolve errors that result from db.test? For example, see the error below:
select * from grass_test1
dbmi: Protocol error
/Applications/grass61cvs.app/Contents/Resources/grass-6.1.cvs/scripts/db.test: line 85: 15700 Done echo "$SQL"
15701 Broken pipe | db.select -c >$result
EXECUTE: ******** ERROR ********
0a1,2
> 1|123.456000|abcd
> 2||xxx
RESULT: ******** ERROR ********
A little more information on my db problem:
I discovered that this works just fine:
db.select table=colonies database=tx_state_nad83 driver=mysql sql=“select abbrv from colonies”
However, this does not work:
db.select table=colonies database=tx_state_nad83 driver=mysql sql=“select * from colonies”
dbmi: Protocol error
Broken pipe
If i use a column name in the select statement, everything works fine. If I use an * or a column name that doesn’t exist, I get the errors above, namely:
dbmi: Protocol error
Broken pipe
I hope that sheds some light on the problem. Does anyone know what’s happening here?
Jason Horn
Boston University Department of Biology
5 Cumington Street Boston, MA 02215
office: 617 353 6987
cell: 401 588 2766
On Sep 13, 2005, at 1:51 PM, Jason Horn wrote:
Does anyone know how to resolve errors that result from db.test? For example, see the error below:
select * from grass_test1
dbmi: Protocol error
/Applications/grass61cvs.app/Contents/Resources/grass-6.1.cvs/scripts/db.test: line 85: 15700 Done echo “$SQL”
15701 Broken pipe | db.select -c >$result
EXECUTE: ******** ERROR ********
0a1,21|123.456000|abcd
2||xxx
RESULT: ******** ERROR ********