[GRASS-user] v.db.select works, db.select fails: same mapset, same VAR

Hello,

any idea why v.db.select works while db.select fails when invoked from inside the same mapset?

I call db.connect -p before calling (v.)db.select and get:

driver:odbc

database:3drov

schema:(null)

group:(null)

This all works fine for v.db.select but db.select fails with an error message. My version of GRASS is 6.2.3 and the error message reads:

DBMI-ODBC driver error: SQLConnect():

[UnixODBC]FATAL: role '' does not exist (210)

Now, I am pretty confident that unixODBC is correctly configured on my Linux box as I have C code that works with the same DSN (3drov) and also, obviously, because v.db.select manages to connect to my database through the same DSN. I also made sure that the 3 in the name 3drov is not the source of the problem, but I'm now totally clueless.

Any idea why? Thanks in advance!

Sébastien E. Wailliez
Software Engineer
Trasys Space - Consulting & Solutions
Terhulpsesteenweg 6C
B-1560 Hoeilaart - Belgium

Office: 2K22
Tel: +32 2 773 75 64
Fax: +32 2 773 79 30
Email: sebastien.wailliez@trasys.be

Sébastien,

could you try ogrinfo on that data set? Just to see if it also
fails. Should be something like

ogrinfo ODBC:user/pass@DSN table

Markus

On Wed, Mar 19, 2008 at 1:30 PM, Wailliez Sébastien
<sebastien.wailliez@trasys.be> wrote:

Hello,

any idea why v.db.select works while db.select fails when invoked from
inside the same mapset?

I call db.connect –p before calling (v.)db.select and get:

driver:odbc

database:3drov

schema:(null)

group:(null)

This all works fine for v.db.select but db.select fails with an error
message. My version of GRASS is 6.2.3 and the error message reads:

DBMI-ODBC driver error: SQLConnect():

[UnixODBC]FATAL: role '' does not exist (210)

Now, I am pretty confident that unixODBC is correctly configured on my Linux
box as I have C code that works with the same DSN (3drov) and also,
obviously, because v.db.select manages to connect to my database through the
same DSN. I also made sure that the 3 in the name 3drov is not the source of
the problem, but I'm now totally clueless.

Any idea why? Thanks in advance!

Sébastien E. Wailliez
Software Engineer
Trasys Space - Consulting & Solutions
Terhulpsesteenweg 6C
B-1560 Hoeilaart - Belgium

Office: 2K22
Tel: +32 2 773 75 64
Fax: +32 2 773 79 30
Email: sebastien.wailliez@trasys.be

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

--
Open Source Geospatial Foundation
http://www.osgeo.org/
http://www.grassbook.org/