Hello,
it seems that You are looking for v.db.connect, as You need to
reconnect existing vector data sets to a different database. (Or, if
You are careful, just edit MAPSET/vector/MYMAP/dbln file.)
As goes for a GUI crash, please, report it in the issue tracker, as
WXGUI shouldn't crash if DB
On Thu, 22 Mar 2012, Maris Nartiss wrote:
it seems that You are looking for v.db.connect, as You need to reconnect
existing vector data sets to a different database. (Or, if You are
careful, just edit MAPSET/vector/MYMAP/dbln file.)
Maris,
You may very well be correct. I have been looking
On Thu, 22 Mar 2012, Maris Nartiss wrote:
As goes for a GUI crash, please, report it in the issue tracker, as WXGUI
shouldn't crash if DB connection information isn't correct.
Osgeo didn't like something about my attempts to create an account so I
could post the problem. As it did not tell
I changed the database names so they represent the project rather than the
state in which they're located. The postgres ALTER DATABASE command does the
job quite well. Unfortunately, grass seems to be confused by the name change
and any attempt to access map attributes or overlay (intersect)
Hi Rich,
I've also had trouble with using Postgres tables in GRASS and then changing
them. If I deleted the tables in the past, it was always very difficult to
be able to delete the corresponding vector maps. My only real positive
experience in that regard has been to delete the mapset and start
On Wed, 21 Mar 2012, Daniel Lee wrote:
I've also had trouble with using Postgres tables in GRASS and then
changing them. If I deleted the tables in the past, it was always very
difficult to be able to delete the corresponding vector maps. My only real
positive experience in that regard has been
