Bogus SQL error message handling in db_execute_immediate

[marisn]

I was trying to import shapefile with v.in.ogr and it failed while trying to create database. Only problem - there was no meaningfull error message displayed. Using same SQL expression with db.execute also failed to produce readable error message. After subsequent runs I once got some wired character as error message most likely coming from bogous printf statement argument. Still I was not able to identify origin of that error message to check printf arguments.
Revision: 34900 make distclean && make

$ echo "create table gps_pents_osl (cat integer, SHAPEID integer, ELE double precision, NAME varchar ( 80 ), DESC varchar ( 80 ), AUGST double precision)" | db.execute
DBMI-DBF driver error:
SQL parser error: �۷
in statement:
create table gps_pents_osl (cat integer, SHAPEID integer, ELE double precision, NAME varchar ( 80 ), DESC varchar ( 80 ), AUGST double precision)

Error in db_execute_immediate()

[neteler]

AFAIK "DESC" is a reserved SQL word which cannot be a column name.

See "ERROR MESSAGES" in the v.in.ogr manual. Apparently the vector modules catch the error while the db.* modules don't.

Markus

[hamish]

the "SQL parser error: �۷" indicates e.g. %s of an uninitialized variable.

Hamish

[marisn]

Error message was used after freeing it. Fixed in r36326.