<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<link href="chrome://translator/skin/floatingPanel.css"
type="text/css" rel="stylesheet">
</head>
<body bgcolor="#FFFFFF" text="#000099">
You can define the SQLite database yourself with db.connect. The
database does only contain the attribute data, no geometric
information, so you could define the same SQLite database for
different mapsets and even locations. I tried this actually out some
time ago, and it worked for me at the time. You can easily try out
yourself, but see my next point. <br>
<br>
Whether that is a smart thing to do is another point. Depending on
how you set up your GRASS database, you might end up having layers
with the same name in different mapsets or locations. In that case,
you will run into trouble; you can't have more then one table with
the same name in your SQLite database. I would therefore recommend
having one SQLite database per mapset. There are also plans for a
SQLite database per layer. I am not sure what would be the advantage
of that though. <br>
<br>
I am not sure about your second question, but GRASS 7 uses the
SQLite database by default.<br>
<br>
Paulo<br>
<br>
<br>
<br>
On 04/09/2012 09:04 AM, Micha Silver wrote:
<blockquote cite="mid:4F828A04.4090602@arava.co.il" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<style>body p { margin-bottom: 0cm; margin-top: 0pt; } </style> On
09/04/2012 09:47, RichardC wrote:
<blockquote cite="mid:1333954039623-4715248.post@n6.nabble.com"
type="cite">
<pre wrap="">Hi,
I'm also planning to move from the DBF to SQLite database, and was wondering
if you might be able to help with the following.
Is it is possible to set a single SQLite database for the entire GRASS GIS
database or each mapset requires its own sqlite db file?
</pre>
</blockquote>
<br>
I'm pretty sure it's per mapset.<br>
Have a look at this nice summary blog post about db connections
(from 2009, but still accurate)<br>
<a moz-do-not-send="true"
href="http://casoilresource.lawr.ucdavis.edu/drupal/node/733">http://casoilresource.lawr.ucdavis.edu/drupal/node/733</a><br>
<blockquote cite="mid:1333954039623-4715248.post@n6.nabble.com"
type="cite">
<pre wrap="">Currently, I'm using v6.4.2 which uses DBF by default. Is there a command
that can switch the installation to using SQLite as the default, so that
mapsets in subsequently created locations will use Sqlite? Or I need to
reconfigure the installation (i.e., the ./configure options prior to
make/make install)?
Thanks,
Richard
--
View this message in context: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://osgeo-org.1560.n6.nabble.com/getting-from-DBF-to-SQLite-tp4657601p4715248.html">http://osgeo-org.1560.n6.nabble.com/getting-from-DBF-to-SQLite-tp4657601p4715248.html</a>
Sent from the Grass - Users mailing list archive at Nabble.com.
_______________________________________________
grass-user mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a>
This mail was received via Mail-SeCure System.
</pre>
</blockquote>
<p><br>
</p>
<br>
<pre class="moz-signature" cols="72">--
Micha Silver
052-3665918
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
grass-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a>
</pre>
</blockquote>
<br>
<div style="bottom: auto; left: 1605px; right: auto; top: 133px;
display: none;" class="translator-theme-default"
id="translator-floating-panel">
<div title="Click to translate"
id="translator-floating-panel-button"></div>
</div>
</body>
</html>