[GRASSLIST:8338] RE: db.execute syntax

[Patton, Eric]

Yeah, I checked in db.describe to see what case the system uses. Both cat
and md_60 fields are uppercase. But I tried lowercase for fun, as well.

Still no dice.

~ Eric.
 

-----Original Message-----
From: Trevor Wiens [mailto:twiens at interbaun.com] 
Sent: Monday, September 19, 2005 1:13 PM
To: Patton, Eric
Cc: glynn at gclements.plus.com; epatton at nrcan.gc.ca; GRASSLIST at baylor.edu
Subject: Re: [GRASSLIST:8334] RE: db.execute syntax

On Mon, 19 Sep 2005 13:01:41 -0300
"Patton, Eric" <epatton at nrcan.gc.ca> wrote:

> Hmm...I gave that a try, with the following results:
> 
>  
> echo 'UPDATE Opil184a_ship_nav_med_smth SET MOD_60 = 1 WHERE  CAT % 60  =
0'
> | db.execute
> 
> dbmi: Protocol error (invalid table/column name or unsupported column 
> type)
> ERROR: Error while executing: "UPDATE Opil184a_ship_nav_med_smth SET
MOD_60
>        = 1 WHERE CAT % 60 = 0
> 
> db.describe shows that my cat and MOD_60 columns are indeed INT. So 
> I'm not sure why there's a problem with the table column name/type.
> 
> 
> Perhaps quotation marks are needed somewhere?
> 
> 
> ~ Eric.

This is rather inane, but you do have the case correct? is is CAT not cat
and MOD_60 not mod_60??

T
--
Trevor Wiens
twiens at interbaun.com

The greatest obstacle to discovery is not ignorance - it is the illusion of
knowledge.
(Daniel J. Boorstin)