[GRASSLIST:9454] Re: DBMI errors with MySQL tables
Dylan Beaudette
dylan.beaudette at gmail.com
Tue Dec 13 19:51:07 EST 2005
On Tuesday 13 December 2005 03:56 pm, Glynn Clements wrote:
> Radim Blazek wrote:
> > On 12/13/05, Dylan Beaudette <dylan.beaudette at gmail.com> wrote:
> > > ./db/drivers/mysql/table.c:113: G_debug(3, "load_table()");
> > > ./db/drivers/mysql/table.c:117: G_debug(3, "load_table() - not
> > > loaded"); ./db/drivers/mysql/table.c:193: G_debug(3, "load_table() -
> > > number of cols is %d", db.tables[t].ncols);
> > >
> > > Not sure how to interpret these debug messages...
> > >
> > > Further ideas? maybe we are getting closer...?
> >
> > The mysql driver is a quick hack which was written by somebody as
> > copy-and-paste from dbf which is completely wrong (loading tables
> > to memery instead of mysql_fetch_field_direct fro each db_fetch etc.)
> > + practicaly it is not maintained few years.
> > It should be completely rewritten.
>
> Presumably you can access MySQL databases using the ODBC driver?
Indeed. I hadn't thought about this. Does anyone have an idea as to how robust
the ODBC driver is when connecting to MySQL ?
Thanks!
--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341
More information about the grass-user
mailing list