Let's say one is impatient about cases where (sql.html says) "the
GRASS SQL parser needs to be extended", so one thinks: "I'll try
postgresql". However one is on a modem, so all one can download is
sqlite. However, db.drivers does not list sqlite yet. What might one
do in this case? Assume we are on Debian and not prepared to mess with
GRASS source code.
Let's say one is impatient about cases where (sql.html says) "the
GRASS SQL parser needs to be extended", so one thinks: "I'll try
postgresql". However one is on a modem, so all one can download is
sqlite. However, db.drivers does not list sqlite yet. What might one
do in this case? Assume we are on Debian and not prepared to mess with
GRASS source code.
output db with v.out.ascii.db (from Wiki add-ons page), use awk, octave,
whatever to make & populate a new column, reimport the new vector with
v.in.db or v.in.ascii.
?
The Debian postgresql package + immediate deps are only ~ 5mb download?
Hamish
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dan Jacobson wrote:
Let's say one is impatient about cases where (sql.html says) "the
GRASS SQL parser needs to be extended", so one thinks: "I'll try
postgresql". However one is on a modem, so all one can download is
sqlite. However, db.drivers does not list sqlite yet. What might one
do in this case? Assume we are on Debian and not prepared to mess with
GRASS source code.
wild guess: use odbc to connect to sqlite ?
http://www.ch-werner.de/sqliteodbc/
but not packaged for debian yet:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298866
connect with:
db.connect driver=odbc database=DBNAME
Moritz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCtn6DrIrMbm76jD8RAsZkAJ9pyo14IqpTq1CBtiniI8oaaJUR7wCePv77
oMEbefl7hk+/55vH/RvqK9U=
=vRul
-----END PGP SIGNATURE-----