[GRASS-dev] DBMI parse error question

[Markus Neteler]

On Wed, Feb 28, 2007 at 02:01:29PM +1300, Hamish wrote:
> Markus Neteler wrote:
> > > >I try to import a map from PostgreSQL into GRASS/DBF driver
> > > >with v.in.db, but get
> > > >
> > > >DBMI-DBF driver error:
> > > >SQL parser error in statement:
> > > >create table ticks_feltre_2002_2006_sites ( ID integer, comune  
> > > >varchar(250), localita varchar(250), microsito varchar(250), data  
> > > >date, ora time, larve integer, ninfe integer, adm integer, adf  
> > > >integer, adtot integer, tcelsius double precision, umidrel double  
> > > >precision, note varchar(250), mapsheet varchar(250), mgrs varchar 
> > > >(250), stazione varchar(250), periodo_prelievo varchar(250), north 
> > > >
> > > >double precision, east double precision, siteid integer )
> > > >Cannot create table
> > > >
> > > >but I don't see where the evil is:
> > > >
> > > >echo " ID integer, comune varchar(250), localita varchar(250),  
> > > >microsito varchar(250), data date, ora time, larve integer, ninfe  
> > > >integer, adm integer, adf integer, adtot integer, tcelsius double  
> > > >precision, umidrel double precision, note varchar(250), mapsheet  
> > > >varchar(250), mgrs varchar(250), stazione varchar(250),  
> > > >periodo_prelievo varchar(250), north double precision, east double 
> > > >
> > > >precision, siteid integer" | tr -s ',' '\n' | sort
> > > > adf integer
> > > > adm integer
> > > > adtot integer
> > > > comune varchar(250)
> > > > data date
> > > > east double precision
> > > > ID integer
> > > > larve integer
> > > > localita varchar(250)
> > > > mapsheet varchar(250)
> > > > mgrs varchar(250)
> > > > microsito varchar(250)
> > > > ninfe integer
> > > > north double precision
> > > > note varchar(250)
> > > > ora time
> > > > periodo_prelievo varchar(250)
> > > > siteid integer
> > > > stazione varchar(250)
> > > > tcelsius double precision
> > > > umidrel double precision
> > > >
> > > >Any ideas? Of course it would be fancy to have a more reasonable
> > > >error message. This error uses to pop up if preserved words are
> > > >used as column names, but I don't see any (even, it should tell me
> > > >in an ideal world).
> 
> cutting the list in half, trialing that, cutting in half again, etc.
> shows that "ora time" is the offending entry.

Hamish - thanks for finding this one - I was confused by "ora"
but in fact "time" wasn't supported!

I have now added "time" type support to the parser and
voila' it works.

Thanks,
Markus