<p>Hi Rich,</p>
<p>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 anew, but of course that's about as far from elegant as you can get. Sorry that I don't know more about the way GRASS interacts with Postgres and where the connection is stored.</p>
<p>Best,<br>
Daniel </p>
<p>--</p>
<p>B.Sc. Daniel Lee<br>
Geschäftsführung für Forschung und Entwicklung<br>
ISIS - International Solar Information Solutions GbR<br>
Vertreten durch: Daniel Lee, Nepomuk Reinhard und Nils Räder</p>
<p>Deutschhausstr. 10<br>
35037 Marburg<br>
Festnetz: +49 6421 379 6256<br>
Mobil: +49 176 6127 7269<br>
E-Mail: <a href="mailto:Lee@isi-solutions.org">Lee@isi-solutions.org</a><br>
Web: <a href="http://www.isi-solutions.org">http://www.isi-solutions.org</a></p>
<p>ISIS wird gefördert durch die Bundesrepublik Deutschland, Zuwendungsgeber: Bundesministerium für Wirtschaft und Technologie aufgrund eines Beschlusses des Deutschen Bundestages, sowie durch die Europäische Union, Zuwendungsgeber: Europäischer Sozialfonds. Zusätzliche Unterstützung erhält ISIS von dem Entrepreneurship Cluster Mittelhessen, der Universität Marburg, dem Laboratory for Climatology and Remote Sensing und dem GIS-Lab Marburg.</p>
<div class="gmail_quote">On Mar 21, 2012 9:41 PM, "Rich Shepard" <<a href="mailto:rshepard@appl-ecosys.com">rshepard@appl-ecosys.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I changed the database names so they represent the project rather than the<br>
state in which they're located. The postgres ALTER DATABASE command does the<br>
job quite well. Unfortunately, grass seems to be confused by the name change<br>
and any attempt to access map attributes or overlay (intersect) the table<br>
causes the wxPython GUI to crash and a message appears on the console that<br>
grass was unable to open the old database name (error #16007.1) and unable<br>
to describe the table _LAB (error #16010.1).<br>
<br>
After changing the postgres database name I ran db.connect to associate<br>
the new name with the location and mapset. It appears that this does not<br>
change where grass has the old name tucked away. The VAR file has the new<br>
database name.<br>
<br>
I want to better understand how grass interacts with postgres and where<br>
it needs to be modified to reflect the new database names. If this is in<br>
one of the db.* modules I missed seeing it.<br>
<br>
TIA,<br>
<br>
Rich<br>
<br>
______________________________<u></u>_________________<br>
grass-user mailing list<br>
<a href="mailto:grass-user@lists.osgeo.org" target="_blank">grass-user@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/grass-user</a><br>
</blockquote></div>