Hi,
I noticed that Grass 6.3 cvs doesn't 'remember' the database changes that were applied during the last session:
db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:
group:
db.connect driver=sqlite database=/home/epatton/Projects/FundyBathy/2007006/databases/BOF_2007.db
db.connect -p
driver:sqlite
database:/home/epatton/Projects/FundyBathy/2007006/databases/BOF_2007.db
schema:
group:
(exit Grass63, then start it again)
db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:
group:
I've tried setting my database changes via the gui as well, with no difference. I've double-checked that sqlite database I'm trying to connect to is where I pointed to. Shouldn't Grass preserve the database settings from session-to-session?
Thanks,
~ Eric.
On Thu, Oct 04, 2007 at 09:37:25PM +0200, Patton, Eric wrote:
Hi,
I noticed that Grass 6.3 cvs doesn't 'remember' the database changes that were applied during the last session:
>db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:
group:
>db.connect driver=sqlite database=/home/epatton/Projects/FundyBathy/2007006/databases/BOF_2007.db
>db.connect -p
driver:sqlite
database:/home/epatton/Projects/FundyBathy/2007006/databases/BOF_2007.db
schema:
group:
(exit Grass63, then start it again)
>db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:
group:
I've tried setting my database changes via the gui as well, with no difference. I've double-checked that sqlite database I'm trying to connect to is where I pointed to. Shouldn't Grass preserve the database settings from session-to-session?
Absolutely. I was also suprised yesterday and added a workaround
in lib/init/init.sh (to restore DBF if the VAR file is missing).
But I wonder what is deleting this file. This is a pretty new bug.
Markus
------------------
ITC -> dall'1 marzo 2007 Fondazione Bruno Kessler
ITC -> since 1 March 2007 Fondazione Bruno Kessler
------------------
Ok, thanks for the confirmation. I'll file an official bug report, then.
~ Eric.
-----Original Message-----
From: Markus Neteler [mailto:neteler@itc.it]
Sent: Thu 10/4/2007 4:49 PM
To: Patton, Eric
Cc: grassuser@grass.itc.it; grass-dev@grass.itc.it
Subject: Re: [GRASS-dev] Grass 6.3-cvs fails to preserve databaseconnection changes
On Thu, Oct 04, 2007 at 09:37:25PM +0200, Patton, Eric wrote:
Hi,
I noticed that Grass 6.3 cvs doesn't 'remember' the database changes that were applied during the last session:
>db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:
group:
>db.connect driver=sqlite database=/home/epatton/Projects/FundyBathy/2007006/databases/BOF_2007.db
>db.connect -p
driver:sqlite
database:/home/epatton/Projects/FundyBathy/2007006/databases/BOF_2007.db
schema:
group:
(exit Grass63, then start it again)
>db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:
group:
I've tried setting my database changes via the gui as well, with no difference. I've double-checked that sqlite database I'm trying to connect to is where I pointed to. Shouldn't Grass preserve the database settings from session-to-session?
Absolutely. I was also suprised yesterday and added a workaround
in lib/init/init.sh (to restore DBF if the VAR file is missing).
But I wonder what is deleting this file. This is a pretty new bug.
Markus
------------------
ITC -> dall'1 marzo 2007 Fondazione Bruno Kessler
ITC -> since 1 March 2007 Fondazione Bruno Kessler
------------------