Opened 7 years ago

Closed 7 years ago

#2109 closed enhancement (fixed)

connect error in replacement of $MAPSET

Reported by: lucadelu Owned by: grass-dev@…
Priority: normal Milestone: 7.0.0
Component: Temporal Version: svn-trunk
Keywords: connection Cc:
CPU: All Platform: All

Description

Hi all,

when I try to use a different mapset then PERMANENT using $MAPSET variable it is not changed with the right value but a $MAPSET directory is create on the location path

Change History (5)

comment:1 Changed 7 years ago by huhabla

You can use:

eval `g.gisenv`

To set $GISDBASE, $LOCATION_NAME and $MAPSET

I will modify the code of t.connect so that instead of the shell variables $GISDBASE and $LOCATION_NAME the real path variables are set in the module help to reduce confusion.

t.connect accepts as database argument a string that defines a database connection. In case of sqlite this must be a path. t.connect will not substitute shell variables itself if they are not set.

comment:2 in reply to:  1 ; Changed 7 years ago by huhabla

Resolution: fixed
Status: newclosed
Type: defectenhancement

Replying to huhabla:

You can use:

eval `g.gisenv`

To set $GISDBASE, $LOCATION_NAME and $MAPSET

I will modify the code of t.connect so that instead of the shell variables $GISDBASE and $LOCATION_NAME the real path variables are set in the module help to reduce confusion.

Done in r58015

t.connect accepts as database argument a string that defines a database connection. In case of sqlite this must be a path. t.connect will not substitute shell variables itself if they are not set.

comment:3 in reply to:  2 Changed 7 years ago by lucadelu

Resolution: fixed
Status: closedreopened

Replying to huhabla:

Replying to huhabla:

You can use:

eval `g.gisenv`

To set $GISDBASE, $LOCATION_NAME and $MAPSET

I will modify the code of t.connect so that instead of the shell variables $GISDBASE and $LOCATION_NAME the real path variables are set in the module help to reduce confusion.

Done in r58015

Sorry I don't understand what was done, I have the same behavior of yesterday, If I use

t.connect database='$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/tgis.db'

the database is created in

/grassdata/eu_laea/$MAPSET/sqlite/tgis.db

The revision I'm using is 58021.

comment:4 Changed 7 years ago by huhabla

This issue is hopefully fixed in r58024.

Now the temporal framework supports '$GISBASE/$LOCATION_NAME/$MAPSET' settings and will substitute them correctly. t.connect should show now the same behavior as db.connect.

comment:5 in reply to:  4 Changed 7 years ago by lucadelu

Resolution: fixed
Status: reopenedclosed

Replying to huhabla:

This issue is hopefully fixed in r58024.

Fixed, thanks a lot

Note: See TracTickets for help on using tickets.